> For the complete documentation index, see [llms.txt](https://shinkalabs.gitbook.io/hub/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://shinkalabs.gitbook.io/hub/andromeda/concepts/mcp.md).

# MCP

The Model Context Protocol (MCP) is a standard way for AI agents and IDEs to call external tools. Andromeda ships an MCP server at `https://api.andromedainfra.pro/mcp`. Every REST route is mirrored as an MCP tool, generated from the same route catalogue that drives the HTTP API, so the two surfaces never drift apart. There are around 65 tools, covering wallet creation and signing, recovery, policy operations, future-sign, webhooks, audit-log queries and the Encrypt FHE surface. (`GET /capabilities` reports the exact count for the deployment you call.)

## Why it exists

Agents increasingly perform real actions: creating a wallet, signing a message, rotating a key, arming a future signature, querying an audit log, deploying a policy. With MCP, an agent in Claude Desktop, Cursor, or any MCP client can do all of that with no SDK and no glue code. You add one server entry; the agent discovers the tools.

The headline example: **`create_dwallet`**. The agent asks the user for a passphrase, calls the tool, and a new cross-chain dWallet exists — no SDK, no seed phrase, no node, no client install. Andromeda runs the 2PC-MPC DKG server-side and stores the wallet's key wrapped under the passphrase (never the passphrase itself, never the plaintext key). See [Create a dWallet](/hub/andromeda/getting-started/create-dwallet.md) for the custody model. Paired tools: `presign` and `sign_message`.

## How it authenticates

The MCP endpoint uses the same `X-Api-Key` header as REST, passed in the client's server configuration. The key's [scopes](/hub/andromeda/getting-started/auth.md) apply: a key without `write` cannot call tools that mutate state, and admin-only tools (webhooks, audit, policies, future-sign) require the `admin` scope. Quotas are charged per tool call, matching the cost of the equivalent REST call.

## Transport

The server speaks streamable HTTP. Point an MCP client at the `/mcp` URL with the header set and it negotiates the rest. See [Connect](/hub/andromeda/mcp-reference/connect.md) for client configuration and [Tool catalogue](/hub/andromeda/mcp-reference/tools.md) for what is exposed.

## Idempotency over MCP

Tool calls honour the same idempotency rules as REST: the same request body with the same `Idempotency-Key` replays the previous response rather than re-executing. See [Idempotency keys](/hub/andromeda/guides/idempotency.md).

## What MCP is not

MCP is a different surface over the same operations, not a different product. Anything you can do over MCP you can do over REST, and vice versa. If you are building a normal backend integration, use REST. If you are building (or plugging into) an agent, use MCP.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://shinkalabs.gitbook.io/hub/andromeda/concepts/mcp.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.