MCP 服务器

Chainstack MCP Server

Provides AI agents direct access to the Chainstack platform, enabling blockchain node deployment, documentation search, platform status checks, and more.

README

Chainstack MCP server

The Chainstack MCP server gives AI agents direct access to the Chainstack platform — deploy blockchain nodes, search documentation, and check platform status from any coding environment.

Live at mcp.chainstack.com

Quick start

Type this into any AI agent:

get mcp.chainstack.com

The agent will fetch the onboarding page and walk you through setup. Works with Claude Code, Cursor, Codex, Windsurf, Gemini CLI, GitHub Copilot, Antigravity, Claude.ai, and ChatGPT.

Tools

No API key needed:

search_docs — search Chainstack documentation
get_doc_page — fetch full doc page content
get_platform_status — check platform status and incidents
contact_chainstack — send a message to Chainstack (sales, support, or general questions)
get_chainstack_pricing — live pricing snapshot: plan tiers, feature matrix, add-ons, and the per-chain dedicated-node catalog

API key required (get one here):

get_organization, list_projects, create_project, get_project, update_project, delete_project
list_nodes, get_node, create_node, update_node, delete_node, get_deployment_options
request_testnet_funds — top up a testnet address from the Chainstack faucet (12 networks across EVM, Solana, and TON)

Two ways to use

Option 1: Install as a skill (lean context)

Cross-agent, via the skills CLI — it auto-detects your installed agent (50+ supported, including Claude Code, Cursor, Codex, Windsurf, Antigravity, GitHub Copilot, Pi, and OpenCode):

npx skills add chainstacklabs/mcp-server

This installs the bundled skills/chainstack skill.

Option 2: Register as an MCP server

claude mcp add --transport http chainstack https://mcp.chainstack.com/mcp -s user

See full setup guide for all agents.

MCP registry

Published to the official MCP Registry as com.chainstack/chainstack:

curl "https://registry.modelcontextprotocol.io/v0.1/servers?search=com.chainstack/chainstack&version=latest"

server.json is the manifest. Its version field is a placeholder — the publish workflow derives the real value from the live server card at mcp.chainstack.com, which renders it from the deployed chart, so the registry entry cannot drift from what is actually running. Query the registry, not this file, to see what is published.