Chainstack

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 you 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_organizationRead-only

  Get organization name and ID.

• get_deployment_optionsRead-only

  List blockchain, cloud and network combinations valid for node deployment.

• list_projectsRead-only

  List all projects, which are containers for nodes.

• create_projectWrites

  Create a new project with a name and optional description.

• list_nodesRead-only

  List nodes with status and endpoints, optionally filtered by project.

• get_nodeRead-only

  Get a node's full details including endpoints and cloud info.

• create_nodeWrites

  Deploy a new blockchain node in a project on a chosen blockchain and cloud.

• get_projectRead-only

  Get details of a project.

• update_projectCan delete

  Update a project's name or description.

• delete_projectCan delete

  Delete a project (irreversible).

• update_nodeCan delete

  Rename a node.

• delete_nodeCan delete

  Delete a node (irreversible).

Read from the live server on 3 Oct 2026. Read-only, Writes and Can delete are hints the server declares; your client decides whether to ask before running a tool.

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

Set up

Every client connects to mcp.chainstack.com. Pick yours; the page remembers your choice.

claude mcp add --transport http chainstack https://mcp.chainstack.com/mcp --header "Authorization: Bearer <YOUR_API_KEY>"

{
  "mcpServers": {
    "chainstack": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp.chainstack.com/mcp",
        "--header",
        "Authorization: Bearer <YOUR_API_KEY>"
      ]
    }
  }
}

{
  "mcpServers": {
    "chainstack": {
      "url": "https://mcp.chainstack.com/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_API_KEY>"
      }
    }
  }
}

{
  "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
    }
  ]
}

{
  "mcpServers": {
    "chainstack": {
      "serverUrl": "https://mcp.chainstack.com/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_API_KEY>"
      }
    }
  }
}

codex mcp add chainstack --url https://mcp.chainstack.com/mcp --bearer-token-env-var CHAINSTACK_API_KEY

[mcp_servers.chainstack]
url = "https://mcp.chainstack.com/mcp"
bearer_token_env_var = "CHAINSTACK_API_KEY"

gemini mcp add --transport http --header "Authorization: Bearer <YOUR_API_KEY>" chainstack https://mcp.chainstack.com/mcp

{
  "mcpServers": {
    "chainstack": {
      "type": "http",
      "url": "https://mcp.chainstack.com/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_API_KEY>"
      }
    }
  }
}

FAQ

Embed

Show Chainstack in a README or on your site. Each embed links to this page, uses the server’s own URL, and sets no cookies. How embeds work

README badge Website card iframe JSON

README badge

Markdown

[![Chainstack on mcp.tc](https://mcp.tc/i/chainstack/badge.svg)](https://mcp.tc/i/chainstack)

HTML

<a href="https://mcp.tc/i/chainstack"><img src="https://mcp.tc/i/chainstack/badge.svg" alt="Chainstack on mcp.tc" height="20"></a>

It follows the reader’s light or dark mode. Add ?theme=light or ?theme=dark to fix it, or ?style=compact to show the mark without the word.

Website card

HTML

<script src="https://mcp.tc/w/chainstack.js" async></script>

The card appears where the tag is. Add data-theme="dark" or data-size="compact" to the tag to change it. The file holds everything it needs, so it makes no other requests and sets no cookies.

iframe

HTML

<iframe src="https://mcp.tc/embed/chainstack" title="Chainstack on mcp.tc" width="420" height="200" loading="lazy" allow="clipboard-write" style="border:0;border-radius:8px;max-width:100%"></iframe>

Use it on pages that don’t allow scripts. Add ?theme=light or ?theme=dark to the address to fix the colors.

JSON

The listing as data for your own pages and tools: name, tagline, the server’s own URL, tools and the “Add to” links. Any site can read it (CORS is open).

https://mcp.tc/i/chainstack.json

What each field means