§ Build · ICP MCP

Ask questions and perform actions across your apps by chatting with AI.

ICP MCP is the official connector between your AI assistant and the Internet Computer, hosted by DFINITY. Sign in your assistant with Internet Identity with only desired permissions and session time. Prompt AI to get things done on your behalf.

Connector URL · Production Internet Identity

POSThttps://mcp.internetcomputer.org/mcp

Hosted by DFINITY on the Internet Computer.

What it is

One connector between your AI chat and the Internet Computer

For example, add this server as a Claude connector or a ChatGPT plugin. Then work with your apps in plain language: look things up, call methods, manage your app accounts. No coding required.

№ 01

Chat with your apps

Ask questions and perform actions across your apps, in plain language.

№ 02

It acts as you

You sign in with an Internet Identity and allow AI to access it on your terms.

№ 03

You stay in control

Grants are limited and expire by design. Revoke access anytime.

How to enable it

Connect it in three steps

  1. № 01

    Add mcp.internetcomputer.org/mcp to your chatbot

    as a custom connector or MCP server in Claude, ChatGPT, or any MCP-capable app

  2. № 02

    Click connect to authorize a session for your Internet Identity

    Choose session duration (revocation anytime). Choose Actions and questions to let AI act, or Questions-only mode to only look things up.

  3. № 03

    Your agent is set to go

    Prompt your agent to check facts, analyze and present the data or take actions across your apps. Use your agent on the go from the convenience of your smartphone. No more switching between multiple mobile apps to stay productive.

Trust and control

You decide what AI can reach, and for how long

№ 01

Only add trusted connectors

Make sure the URL is from a source you trust before you add it.

№ 02

Revoke access anytime

Remove the connector to revoke AI access. It stops working right away.

№ 03

Grants expire by design

You pick the identity and how long a grant lasts. Re-approving later is normal, not a fresh setup.

Build with Caffeine

Build with Caffeine, then let your users act through AI.

Apps created through caffeine.ai natively support ICP MCP. Simply by chatting with an AI assistant, your users and admins can request on-demand analytics and get more done on the go.

  • Summarize this week's activity across my Caffeine apps
  • Find the bookings that still need a reply and draft the responses
  • Create three test-users in my new Caffeine app: your-app.caffeine.ai
Try asking

Once it is on, just talk to your AI

  • Book a 1:1 with Alex in August on a day neither of us have too many meetings.
  • Create a daily plan for my trip to Maggia Valley (7-12 Sep).
  • Summarize my progress this week from the data in my workout app.
What AI can do

A few things AI access lets your chat do

№ 011 tool

Open an app

Name an app or paste its link, and one call turns it into something AI can read: the canisters behind it, what each one can answer, and which of them holds the data.

open_app
№ 022 tools

Act as your identity

AI acts as your Internet Identity at an app. Delegations are minted on demand, and results echo the origin they were derived for.

list_app_accountsget_app_principal
№ 035 tools

Read on-network data

Fetch a canister interface, read its API doc, and ask questions of canisters that expose a query surface - with no code to write. Like writes, reads work only on the canisters an app declares as its own.

get_canister_candidget_canister_api_docget_canister_oql_schemacanister_queryicp_oql_guide
№ 042 tools

Act on canisters

Make state-changing calls as your identity, with textual Candid in and out. Writes go to the apps that opted in, on the canisters they declare as their own.

canister_update_callcandid_syntax_guide
For developers

Make your own app discoverable

ICP MCP can only reach an app that describes itself: which canisters it is made of, what their interfaces are, and how they are meant to be used. Publish that description once, and every assistant connected to ICP MCP can find your app and work in it on your users' behalf.

№ 01Any app

Publish the discoverability files

Serve a manifest of your canisters at your app’s origin, keep the Candid interface metadata your toolchain already emits, and add a query method that documents the parts of your API an assistant cannot guess. The service discoverability guide in the developer docs has the exact paths, fields and checks.

/.well-known/ic-architecturecandid:serviceget_api_doc/.well-known/ii-derivation-origin
№ 02Built with Caffeine

Or generate them with caffeine.ai

Apps generated through caffeine.ai publish all of it at deploy time: the canister manifest, the interfaces, the API notes and a queryable data surface. The ICP MCP connection works out of the box, with nothing to write by hand and nothing to keep in sync as the app changes.

Already live on caffeine.ai? Your app is discoverable now.

These files activate participation under the ICP MCP App operator terms, which the app’s operator accepts and which include responsibility for any personal data that reaches the app through the connector.