ePaint

Basically title. We need pick order data available in the Riot API.

All winrate % are broken and inaccurate. We can find some truly ridiculous stuff like Rammus having a 55.43% wr, which is simply not true in the sense of "Pick Rammus and win 55% of your games!"

Counterpicks exist, draft composition exist, flex picks exist. Please, let's acklowedge that.

As it currently is, WR stats for any champion less popular and blindpickable than Ahri or Seraphine are just not accurate.

This data used to be available back in the v3 API from 2016, but it got cut off on the current v4/v5.

Am I the only one that's been getting terrible matchmaking?

I'm talking an ARAM-only player (always on my team ofc) vs a Grandmaster

Games are terribly one-sided and fast, but not because of balancing or Baron or whatever people are blaming. There's always one guy getting 8 0 out of lane, and that speeds things up a lot.

The game is a lot of fun and I'll happily wait until they add a ranked ladder here.

Heyo, I simply wanted to show you guys the directory-mcp I built. Here's the GitHub repo: [https://github.com/ePaint/directory-mcp\](https://github.com/ePaint/directory-mcp)

In my company, we've been suggested more and more to connect MCPs to our Claude instances to speed up communication, which has been great, but I've noticed a common pattern that got really tedious really quickly for me: I had to explain to Claude each time what each project was, who was working on it, and why it mattered.

directory-mcp is simply a graph of people and projects; each node can hold link information like (but not limited to) their Slack ID, Outlook email, or Jira account ID, making other MCP calls m

Heyo, I simply wanted to show you guys the directory-mcp I built. Here's the GitHub repo: https://github.com/ePaint/directory-mcp

In my company, we've been suggested more and more to connect MCPs to our Claude instances to speed up communication, which has been great, but I've noticed a common pattern that got really tedious really quickly for me: I had to explain to Claude each time what each project was, who was working on it, and why it mattered.

directory-mcp is simply a graph of people and projects; each node can hold link information like (but not limited to) their Slack ID, Outlook email, or Jira account ID, making other MCP calls muc

Heyo, I simply wanted to show you guys the directory-mcp I built. Here's the GitHub repo: https://github.com/ePaint/directory-mcp

In my company, we've been suggested more and more to connect MCPs to our Claude instances to speed up communication, which has been great, but I've noticed a common pattern that got really tedious really quickly for me: I had to explain to Claude each time what each project was, who was working on it, and why it mattered.

directory-mcp is simply a graph of people and projects; each node can hold link information like (but not limited to) their Slack ID, Outlook email, or Jira account ID, making other MCP calls muc

Heyo, I simply wanted to show you guys the directory-mcp I built. Here's the GitHub repo: https://github.com/ePaint/directory-mcp

In my company, we've been suggested more and more to connect MCPs to our Claude instances to speed up communication, which has been great, but I've noticed a common pattern that got really tedious really quickly for me: I had to explain to Claude each time what each project was, who was working on it, and why it mattered.

directory-mcp is simply a graph of people and projects; each node can hold link information like (but not limited to) their Slack ID, Outlook email, or Jira account ID, making other MCP calls muc