knows a lot like Kapa AI (the Internetcomputer.org AI). Allowing a chat experience to be as good as doing it on the website.
knows all the good examples from Dfinity in Rust, Typescript, Motoko, etc. Also from the frontend to integrate well, with Identity Kit, Token Transactions, maybe Governance Calls, etc. And therefore can suggest/review code, in that light. (But also community can add references, like on game dev, if someone is in Unity, the AI knows about .NET cdk to connect to the IC)
Maybe the SNSs can also give their docs and example repos as ways for others to connect / use them. Like ICP Swap, Neutrinite, Boom DAO, KongSwap, etc.
Lastly, also good references of Pocket IC usage across all these use cases, making it safer to use vibe coding.
Now, on the side of Agents, Dfinity and the community can add and expand on many actions / service uses of the IC, like:
all ICRC ledger actions;
calling services like:
price or Defi Vectors from Neutrinite;
swap or add/remove liquidity on ICP Swap;
bot reading and sending messages on OC;
etc.
Then novel integrations and use cases for the startups can appear, where an AI Agent studio (maybe Elna) could reuse these actions as UI blocks with configs and anyone can setup their personal canister Agent.
I have seen ElizaOS, and maybe there are other “function calling” framework/registries, but already this MCP one, seems to be gaining significant traction to be worth the investment of the IC community (and Dfinity).
CC to a few people that could be interested in this topic: @ielashi@marc0olo (can you let Justin Kennedy know? Couldn’t find his handle) @fxgst@patnorris
Hi @tiago89 , very interesting topic with many opportunities indeed
in the DeAI group, we’ve had some discussions on MCP before but if you like we could put this on the agenda and talk about initiatives in more detail in an upcoming session then. What do you think?
Thanks for bringing this topic up @tiago89. I’ve also been thinking about MCP support and how that could look like.
I wonder if there can be some generic way of wrapping the canister interfaces to be MCP tools. After all, each canister has an interface with all the methods it supports, and if developers document these methods well in the candid file, then in principle it should be quite easy for these to be be wrapped as MCP tools.
We could even explore integrating MCP with the LLM canister, so that you can also use these tools on-chain.
Hi @baolongt , would love to have you join
For this Thursday, we’ve got a couple of other topics planned but I’d like to have a dedicated session on MCP soon, maybe April 17.
Would you also be open to demo your work on the SNS Agent to the group during the MCP-focused call?
I’m not sure whether or not this will help, but check out this example which shows how an OISY wallet can give a delegation to another principal. Perhaps similar logic can be implemented in MCP?
Currently the LLM canister serves Llama 3.1 8B. More models will be supported soon, but not closed-source models unfortunately as those cannot be hosted in a trustless way.