Skip to content

MCP server for Substrate-based chains #2535

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

jakehemmerle
Copy link
Contributor

@jakehemmerle jakehemmerle commented Apr 1, 2025

Project Abstract

mcp-polkadot aims to expose any Substrate-based chain's on-chain state to AI agents via the Model-Context Protocol (MCP). More examples of MCP can be found here

Grant level

  • Level 1: Up to $10,000, 2 approvals
  • Level 2: Up to $30,000, 3 approvals
  • Level 3: Unlimited, 5 approvals (for >$100k: Web3 Foundation Council approval)

Application Checklist

  • The application template has been copied and aptly renamed (project_name.md).
  • I have read the application guidelines.
  • Payment details have been provided (Polkadot AssetHub (USDC & DOT) address in the application and bank details via email, if applicable).
  • I understand that an agreed upon percentage of each milestone will be paid in vested DOT, to the Polkadot address listed in the application.
  • I am aware that, in order to receive a grant, I (and the entity I represent) have to successfully complete a KYC/KYB check.
  • The software delivered for this grant will be released under an open-source license specified in the application.
  • The initial PR contains only one commit (squash and force-push if needed).
  • The grant will only be announced once the first milestone has been accepted (see the announcement guidelines).
  • I prefer the discussion of this application to take place in a private Element/Matrix channel. My username is: @_______:matrix.org (change the homeserver if you use a different one)

@github-actions github-actions bot added the admin-review This application requires a review from an admin. label Apr 1, 2025
Copy link
Contributor

github-actions bot commented Apr 1, 2025

CLA Assistant Lite bot All contributors have signed the CLA ✍️ ✅

@jakehemmerle
Copy link
Contributor Author

I have read and hereby sign the Contributor License Agreement.

Copy link
Contributor

@keeganquigley keeganquigley left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @jakehemmerle nice to talk to you again. I see you marked 0% for DOT payment, however at least 50% DOT (vested linearly over two years) is mandatory now for the grants program. Would you be willing to accept half the payment in DOT and if so could you update this?

@keeganquigley keeganquigley added the changes requested The team needs to clarify a few things first. label Apr 2, 2025
@jakehemmerle
Copy link
Contributor Author

Hi @jakehemmerle nice to talk to you again. I see you marked 0% for DOT payment, however at least 50% DOT (vested linearly over two years) is mandatory now for the grants program. Would you be willing to accept half the payment in DOT and if so could you update this?

Hey Kegan! I hope all is well in your world. Just updated it.

Another thing, I now realize that grants for individual contributors might aim for a max $10k grant instead of max $30k. Would it be better to decompose this into a smaller set of milestones and aim for the $10k instead?

@keeganquigley
Copy link
Contributor

Thanks @jakehemmerle much appreciated. I have marked the application as ready for review and will ping the rest of the committee for comment.

To answer your question, I would leave as is for now and you can always change it down the line if it isn't accepted. Thanks!

@keeganquigley keeganquigley added ready for review The project is ready to be reviewed by the committee members. and removed changes requested The team needs to clarify a few things first. labels Apr 4, 2025
@PieWol PieWol self-assigned this Apr 7, 2025
@KarimJedda
Copy link

A small suggestion from me would be to not call it mcp-substrate but rather mcp-polkadot. Would that work?

@jakehemmerle
Copy link
Contributor Author

A small suggestion from me would be to not call it mcp-substrate but rather mcp-polkadot. Would that work?

Is there a reason, semantically, that mcp-polkadot is more descriptive? This would work for any Substrate-based runtime (eg. Polkadot, Astar, Entropy, etc).

@KarimJedda
Copy link

Developer tooling & resources will benefit from consolidation around the Polkadot brand, given the branding overhaul initiated across the ecosystem in the past months/year.

These two non-exhaustive links might provide a bit more context:

Ideally you want to reduce possible confusion and reduce cognitive load on people that don't have the full history in mind.

In short, it's all Polkadot.

@jakehemmerle
Copy link
Contributor Author

@KarimJedda Right on, thanks for the context. Happy to change to mcp-polkadot.

@jakehemmerle
Copy link
Contributor Author

@keeganquigley can you let me know what is missing from the review? If payment details are the bottleneck, can you let me know what email to send them to?

@keeganquigley
Copy link
Contributor

Thanks @jakehemmerle yes can you please send them to [email protected]

Much of the team is ooo this week, sorry for the delay.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
admin-review This application requires a review from an admin. ready for review The project is ready to be reviewed by the committee members.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants