Connect your agent to Claude & Cursor as an MCP tool.
Deploy an agent on a2a cloud and you get a hosted MCP endpoint URL. Paste it into Claude, Cursor, or any MCP client and every tool on the agent shows up for the model to call. Scoped grants control which tools each client gets, and every call returns a signed receipt. No local MCP server to run.
hosted endpoint · any MCP client · scoped per tool
Running your own MCP server to reach Claude and Cursor is a chore.
The usual path to using your agent inside Claude or Cursor is to write an MCP server, run it locally, and keep that process alive on your machine. It only works where it runs, your API keys sit in a plaintext config the client reads, and there's no way to give one client fewer tools than another. Sharing it with a teammate means they set the whole thing up again.
Deploy once, get an MCP URL, paste it into any client.
a2a cloud hosts the MCP endpoint for you. The agent's tools are published over MCP automatically, access is scoped with grants, your keys stay server-side, and every call is signed. Connecting Claude or Cursor is a copy-paste.
Deploy, get an MCP URL
When you deploy an agent to a2a cloud, it exposes a hosted MCP endpoint. Every tool on the agent becomes an MCP tool automatically — you don't build or run a separate MCP server.
Paste into Claude or Cursor
Add the MCP endpoint URL to Claude Desktop, Claude Code, Cursor, or any MCP-compatible client. The agent's tools appear in the client, ready for the model to call directly inside your workflow.
Works with any MCP client
Because a2a serves standard MCP, the same endpoint works across MCP clients — not just Claude and Cursor. One deployed agent, many clients, no per-client rebuild.
Scoped grants per tool
Issue a grant that exposes only the tools a given client should have, with an audience and TTL. A read-only assistant and a build agent can point at the same deployment with different, least-privilege access.
Your keys stay server-side
The agent's upstream credentials and database live on a2a cloud, behind the MCP endpoint. Clients authenticate to the endpoint — they never hold your API keys or database passwords.
Every tool call, signed
Each MCP tool call your client makes returns an Ed25519-signed receipt recording the caller, the grant, the inputs, the outputs, and the cost. What Claude or Cursor did through your agent is provable, not just logged.
Local MCP server vs. a hosted a2a endpoint.
Frequently asked.
How do I connect my agent to Claude as an MCP tool?
Deploy the agent to a2a cloud, which exposes a hosted MCP endpoint where every tool becomes an MCP tool. Copy that endpoint URL into Claude Desktop or Claude Code as an MCP server. The agent's tools then appear in Claude and the model can call them directly — no separate MCP server for you to run.
How do I add my agent as an MCP server in Cursor?
Take the MCP endpoint URL from your deployed a2a cloud agent and add it as an MCP server in Cursor's settings. Cursor connects to the hosted endpoint and surfaces the agent's tools. Because it's a standard MCP endpoint, the same URL works in Cursor, Claude, and other MCP clients.
Does it work with MCP clients other than Claude and Cursor?
Yes. a2a cloud serves a standard MCP endpoint, so any MCP-compatible client can connect to it. You deploy the agent once and reuse the same endpoint across whichever MCP clients you or your team use, without rebuilding anything per client.
Can I limit which tools a client can access?
Yes. Scoped grants let you expose only the tools a given client should have, with an audience and a TTL. Two clients can point at the same deployment with different, least-privilege access — for example a read-only assistant versus an agent allowed to run write operations.
Do I have to put my API keys in the client config?
No. Your agent's upstream credentials and database stay server-side on a2a cloud, behind the MCP endpoint. Clients authenticate to the endpoint rather than holding your secrets, and every tool call returns a signed receipt recording who called what under which grant.
Related guides.
All guides live in the guides index.
Put your agent inside Claude and Cursor.
Deploy any agent — LangGraph, OpenAI Agents SDK, CrewAI, or custom — to a2a cloud and get a hosted MCP endpoint URL. Paste it into Claude, Cursor, or any MCP client and every tool is callable. Scoped grants control access per client, your keys and database stay server-side, and every tool call returns a signed receipt. One deploy, reachable from every client you use.