# Chainstack MCP server > Deploy and manage blockchain nodes across 70+ protocols, search Chainstack docs, check status and pricing, and request testnet funds. - Listing: https://mcp.tc/i/chainstack - Connect: use the server's own URL `https://mcp.chainstack.com/mcp` (with your API key); clients connect to it directly. The listing link is a page, not an MCP endpoint. - Type: remote (Streamable HTTP) - Auth: API key - Category: [Developer Tools](https://mcp.tc/c/developer-tools) - Vendor: Chainstack - Homepage: - Repository: ## About Connects an assistant to the Chainstack platform. You can list projects and nodes, create and delete them, look up valid blockchain and cloud deployment options, search the protocol and RPC documentation, check platform status, read live pricing, request testnet faucet funds, and send a message to the Chainstack team. It runs as a hosted streamable HTTP endpoint at https://mcp.chainstack.com/mcp. Docs search, page fetch, platform status, pricing and contact tools work without a key. Node, project and faucet tools need a Chainstack API key sent as an Authorization Bearer header. ## What it can do - Deploy, rename and delete blockchain nodes - Create, update and delete projects that hold nodes - List valid blockchain, cloud and region options before deploying - Search Chainstack docs and fetch full pages - Check platform status, incidents and maintenances - Fetch live pricing for plans, add-ons and dedicated nodes - Top up testnet addresses from the Chainstack faucet - Send a message to Chainstack sales and support ## Tools (18) - `get_organization`: Get organization name and ID. (read-only) - `get_deployment_options`: List blockchain, cloud and network combinations valid for node deployment. (read-only) - `list_projects`: List all projects, which are containers for nodes. (read-only) - `create_project`: Create a new project with a name and optional description. - `list_nodes`: List nodes with status and endpoints, optionally filtered by project. (read-only) - `get_node`: Get a node's full details including endpoints and cloud info. (read-only) - `create_node`: Deploy a new blockchain node in a project on a chosen blockchain and cloud. - `get_project`: Get details of a project. (read-only) - `update_project`: Update a project's name or description. (can modify or delete data) - `delete_project`: Delete a project (irreversible). (can modify or delete data) - `update_node`: Rename a node. (can modify or delete data) - `delete_node`: Delete a node (irreversible). (can modify or delete data) - `search_docs`: Search Chainstack docs for RPC methods, node setup and code examples. (read-only) - `get_doc_page`: Fetch the full content of a Chainstack documentation page. (read-only) - `get_platform_status`: Check platform status, active incidents and maintenances. (read-only) - `contact_chainstack`: Submit a message to Chainstack's sales and support team after user confirmation. (can modify or delete data) - `request_testnet_funds`: Top up a testnet address from the Chainstack faucet to the per-network cap. (can modify or delete data) - `get_chainstack_pricing`: Return a live snapshot of plan tiers, add-ons and dedicated-node pricing. (read-only) ## Example prompts - "Deploy an Ethereum node in my default project" - "Search the Chainstack docs for supported eth\_call parameters" - "Is there any active incident on the Chainstack platform?" - "Top up my Sepolia address with testnet ETH" ## Install ### Claude Code 1. Run this in a terminal, in your project folder: ```bash claude mcp add --transport http chainstack https://mcp.chainstack.com/mcp --header "Authorization: Bearer " ``` 2. Replace the placeholder with your key before you run it, then check it with `/mcp` inside Claude Code. Add `--scope user` to make it available in every project, not just this one. ### Claude Desktop 1. Custom connectors can’t send this server’s key header, so use the `mcp-remote` bridge. Open **Settings → Developer → Edit Config** and add: `claude_desktop_config.json`: ```json { "mcpServers": { "chainstack": { "command": "npx", "args": [ "-y", "mcp-remote", "https://mcp.chainstack.com/mcp", "--header", "Authorization: Bearer " ] } } } ``` 2. Replace the placeholder with your key and restart Claude Desktop. The bridge needs Node.js on your computer. ### Cursor [Add to Cursor]() (opens Cursor) Or add it by hand to `~/.cursor/mcp.json` (all projects) or `.cursor/mcp.json` (this project): `mcp.json`: ```json { "mcpServers": { "chainstack": { "url": "https://mcp.chainstack.com/mcp", "headers": { "Authorization": "Bearer " } } } } ``` ### VS Code Add it to `.vscode/mcp.json`. VS Code asks for the key the first time and stores it securely: `.vscode/mcp.json`: ```json { "servers": { "chainstack": { "type": "http", "url": "https://mcp.chainstack.com/mcp", "headers": { "Authorization": "Bearer ${input:api-key}" } } }, "inputs": [ { "type": "promptString", "id": "api-key", "description": "API key", "password": true } ] } ``` ### Devin Desktop 1. Add it to `~/.config/devin/mcp_config.json` (macOS and Linux) or `%APPDATA%\devin\mcp_config.json` (Windows): `mcp_config.json`: ```json { "mcpServers": { "chainstack": { "serverUrl": "https://mcp.chainstack.com/mcp", "headers": { "Authorization": "Bearer " } } } } ``` 2. Refresh the MCP server list in Cascade. Devin Desktop is the new name for Windsurf. It reads `serverUrl` (or `url`) for remote servers. ### Codex ```bash codex mcp add chainstack --url https://mcp.chainstack.com/mcp --bearer-token-env-var CHAINSTACK_API_KEY ``` Or edit `~/.codex/config.toml` directly: `config.toml`: ```toml [mcp_servers.chainstack] url = "https://mcp.chainstack.com/mcp" bearer_token_env_var = "CHAINSTACK_API_KEY" ``` Set `CHAINSTACK_API_KEY` to your key in the shell that runs Codex. ### Gemini CLI ```bash gemini mcp add --transport http --header "Authorization: Bearer " chainstack https://mcp.chainstack.com/mcp ``` This adds it to the current project. Add `-s user` to use it everywhere. ### Any client Most clients accept this shape. Some name the URL field differently: `serverUrl` in Devin Desktop, `httpUrl` in Gemini CLI’s settings file. ```json { "mcpServers": { "chainstack": { "type": "http", "url": "https://mcp.chainstack.com/mcp", "headers": { "Authorization": "Bearer " } } } } ``` Zed puts servers under `context_servers` in its settings. Cline needs `"type": "streamableHttp"`, or it assumes SSE. Client only starts local servers? Bridge it with `npx -y mcp-remote https://mcp.chainstack.com/mcp`. ## Details - Server version: 1.10.10 - MCP protocol version: 2025-11-25 - Last checked: 2026-10-03 (reachable) - Listed: 2026-10-03 - Updated: 2026-10-03 --- Source: https://mcp.tc/i/chainstack (mcp.tc is an independent directory, not affiliated with this server's publisher). Corrections: https://mcp.tc/report