Use Stellar Intel through AI agents via the Model Context Protocol (MCP) server.
The MCP server exposes Stellar Intel's off-ramp routing to MCP-capable agents over stdio. It reuses the same routing and canonical-hashing logic as the web app.
The server is published on npm as @stellarintel/mcp.
npm install @stellarintel/mcp# Build and run
npm run build # tsc -> dist/
npm start # node dist/index.js, stdio transport
# Or use tsx for development (no build step)
npx tsx scripts/mcp/server.tsPoint any MCP-capable client (Claude Desktop, an agent framework, etc.) at the built entry point as a stdio command.
Returns the best net-received quote for a corridor + amount. The rate is sourced from the routed anchor's current price (SEP-38 firm quote, falling back to SEP-24/SEP-6 fee-adjusted live FX) — it can return RATE_UNAVAILABLE if the anchor cannot currently be quoted.
{
"from": "USDC",
"to": "NGN",
"amount": "100"
}{
"anchor": "cowrie",
"quoteId": "<64-hex sha256>",
"netReceived": "156800",
"expiresAt": "2026-…Z"
}Returns an unsigned intent envelope plus an unsigned Stellar transaction for an agent to sign. The intentHash is the canonical SHA-256 hash the agent signs.
An off-ramp intent without a signature:
{
"type": "offramp",
"sourceAsset": "USDC",
"destinationAsset": "NGN",
"amount": "100",
"sender": "GABC…",
"recipient": "GBDEST…"
}{
"unsignedEnvelope": {
"intent": { … },
"intentHash": "<sha256-hex>"
},
"unsignedTx": "<base64-xdr>"
}Non-custodial by design. The MCP server can only prepare intents and unsigned transactions — it never holds signing keys. An AI agent can price and compare routes autonomously, but the user must sign the final transaction in their wallet (Freighter) before execution. The agent cannot spend without a user signature.
Tests are located in the main app repository:
# Unit tests
npm run test -- tests/mcp-offramp.spec.ts
# E2E tests (spawns server + real MCP client)
npm run test -- tests/mcp-e2e.spec.ts