MCP overview
The Advisors Crypto MCP server is a thin transport over the REST API. Six tools, two resources, two prompts — everything an MCP-aware client like Claude Desktop or Cursor needs to surface AC as a first-class capability.
Install
The package is @advisors-crypto/mcp. Most clients prefer npx so they always pull the latest version:
{
"mcpServers": {
"advisors-crypto": {
"command": "npx",
"args": ["-y", "@advisors-crypto/mcp"],
"env": { "AC_AGENT_KEY": "ac_live_…" }
}
}
}Tools
Six tools, mapping 1:1 to REST endpoints. Tool names match the API names so a developer who has read the REST docs is already fluent.
whoami— identify the user.get_mandate— read the IPS.get_holdings— read the portfolio.validate_trade— dry-run a trade.propose_trade— queue a trade for attestation.get_audit— recent guardrail decisions.
Resources
Resources let MCP hosts pull AC state into context passively — without spending a tool call. Useful for “what’s my mandate?”-style questions where the model would otherwise have to call get_mandate first.
ac://mandate/current— the active IPS as JSON.ac://holdings/current— the portfolio snapshot.
Prompts
Prompts are reusable workflows the host surfaces in its UI. They inject a starting message that nudges the model into a known-good sequence of tool calls.
- review-portfolio — pulls the mandate + holdings and describes drift, headroom, and target positioning. Doesn’t propose trades.
- propose-trade-with-rationale — takes a free-text idea, runs
get_mandate,validate_trade, and thenpropose_tradewith a one-sentence rationale.
Environment
AC_AGENT_KEY Required. Bearer token from /agent.
AC_API_BASE Optional. Defaults to https://api.advisorscrypto.com.Logs
MCP transport runs over stdio. Server logs go to stderr so they never collide with the protocol stream on stdout. If your client surfaces server logs (Claude Desktop does), look there for the startup banner and any errors.