Chainstack MCP Server (`com.chainstack/chainstack`)

The Chainstack MCP server provides AI agents direct access to the Chainstack platform. It supports deploying and managing blockchain nodes across 70+ protocols, searching documentation, and checking platform status from a coding environment. It is designed for use via MCP tooling and does not require an API key.

🛠️ Key Features

Deploy and manage blockchain nodes across 70+ protocols
Search documentation
Check platform status
Live endpoint at mcp.chainstack.com
Tool count: 18
Topics include: blockchain, mcp, ai-agents, blockchain-nodes, mcp-server, model-context-protocol, rpc, web3

🚀 Use Cases

Deploying blockchain infrastructure for multiple protocols
Looking up Chainstack documentation from within an AI agent
Verifying platform status during development

⚡ Developer Benefits

Works with multiple AI coding environments (e.g., Claude Code, Cursor, Codex, Windsurf, Gemini CLI, GitHub Copilot, Antigravity, Claude.ai, ChatGPT)
No API key needed (per README excerpt)
Provides tools such as search_docs

⚠️ Limitations

The provided excerpt does not list all available tools or configuration details beyond search_docs and the onboarding flow.

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:

code

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):

bash

npx skills add chainstacklabs/mcp-server

This installs the bundled skills/chainstack skill.

Option 2: Register as an MCP server

VS Code — Chainstack is in the GitHub MCP Registry, so VS Code installs it for you. Two ways:

From inside VS Code — open the Extensions view (⇧⌘X / Ctrl+Shift+X), search @mcp chainstack, and click Install. Right-click and choose Install in Workspace to write .vscode/mcp.json instead of your user profile.
From the registry — open the Chainstack entry and click Install > Install in VS Code.

Neither needs an API key, which covers every tool that works unauthenticated.

Anywhere else:

bash

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

See full setup guide for all agents.

MCP registries

Listed in both public registries as com.chainstack/chainstack:

GitHub MCP Registry — the catalog VS Code surfaces in its Extensions view, with one-click install
MCP Registry — the official registry that MCP clients read from

bash

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.

Issues & feature requests

Use Issues to:

Report bugs or unexpected behavior
Request new tools or features
Suggest improvements to any Chainstack product

name	string	required
description	string	optional

project_id	string	required
name	any	optional
description	any	optional

node_id	string	required
name	string	required

message	string	required
email	string	required
name	string	required
category	string	optional

Chainstack