mcpbeat Sign in

Telegraph MCP Server

by telegraphprotocol Your server? Claim it
local only

Telegraph runs on your own machine — the client starts it, so there is no endpoint to ping. 31 installs a week from npm. Last commit 2 Nov 2026.

Decentralized AI inference (weather, deepfake detection, LLMs) with x402 USDC micropayments.

Installs per day peak 8 · avg 3 · -7% w/w
a month agotoday
31
Installs / week
npm · telegraph-protocol-mcp
0
Stars
0 open issues
2 Nov 2026
Last commit
no releases in 90 days
MIT
License
TypeScript

Nothing serious here today

Today is the operative word: we check Telegraph every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

run in your terminal
claude mcp add telegraph -e 'TELEGRAPH_NODE_URL=<TELEGRAPH_NODE_URL>' -e 'TELEGRAPH_ENGINE_URL=<TELEGRAPH_ENGINE_URL>' -e 'TELEGRAPH_DAEMON_URL=<TELEGRAPH_DAEMON_URL>' -- npx -y telegraph-protocol-mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "telegraph": {
      "command": "npx",
      "args": [
        "-y",
        "telegraph-protocol-mcp"
      ],
      "env": {
        "TELEGRAPH_DAEMON_URL": "<TELEGRAPH_DAEMON_URL>",
        "TELEGRAPH_ENGINE_URL": "<TELEGRAPH_ENGINE_URL>",
        "TELEGRAPH_NODE_URL": "<TELEGRAPH_NODE_URL>"
      }
    }
  }
}
~/.codex/config.toml
[mcp_servers.telegraph]
command = "npx"
args = ["-y", "telegraph-protocol-mcp"]
env = { TELEGRAPH_NODE_URL = "<TELEGRAPH_NODE_URL>", TELEGRAPH_ENGINE_URL = "<TELEGRAPH_ENGINE_URL>", TELEGRAPH_DAEMON_URL = "<TELEGRAPH_DAEMON_URL>" }
.cursor/mcp.json
{
  "mcpServers": {
    "telegraph": {
      "command": "npx",
      "args": [
        "-y",
        "telegraph-protocol-mcp"
      ],
      "env": {
        "TELEGRAPH_DAEMON_URL": "<TELEGRAPH_DAEMON_URL>",
        "TELEGRAPH_ENGINE_URL": "<TELEGRAPH_ENGINE_URL>",
        "TELEGRAPH_NODE_URL": "<TELEGRAPH_NODE_URL>"
      }
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "telegraph": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "telegraph-protocol-mcp"
      ],
      "env": {
        "TELEGRAPH_DAEMON_URL": "<TELEGRAPH_DAEMON_URL>",
        "TELEGRAPH_ENGINE_URL": "<TELEGRAPH_ENGINE_URL>",
        "TELEGRAPH_NODE_URL": "<TELEGRAPH_NODE_URL>"
      }
    }
  }
}

Put your own values in place of <TELEGRAPH_NODE_URL> (Telegraph node public API URL (e.g. http://13.237.89.59:7044)), <TELEGRAPH_ENGINE_URL> (Telegraph Engine inference server URL (e.g. http://13.237.89.59:8080)), <TELEGRAPH_DAEMON_URL> (Telegraph Daemon signal API URL (e.g. http://13.237.89.59:8081)). The author’s registry entry marks them as required.

Optional settings from the registry entry, left out of the block above: TELEGRAPH_EVM_PRIVATE_KEY (EVM private key (0x-prefixed hex) of a USDC-funded burner wallet used to sign x402 payments. At least one of TELEGRAPH_EVM_PRIVATE_KEY or TELEGRAPH_SOLANA_PRIVATE_KEY is required), TELEGRAPH_SOLANA_PRIVATE_KEY (Solana private key (base58) for SVM x402 payments. Optional alternative to TELEGRAPH_EVM_PRIVATE_KEY), EVM_NETWORK (CAIP-2 network identifier for EVM payments. Defaults to eip155:*), SVM_NETWORK (CAIP-2 network identifier for Solana payments. Defaults to solana:*), REFRESH_INTERVAL_MS (Dynamic miner-tool refresh interval in milliseconds. Defaults to 300000 (5 min). Set to 0 to disable).

Alternatives to Telegraph

same job, measured the same way
Drain MCP
by kimbo128

Pay for AI inference with USDC micropayments on Polygon. No API keys needed.

63 installs/wk local only
Nutriref
by younghef

Pay-per-call USDA nutrition for AI agents (x402 micropayments in USDC on Base).

local only
PathCourse Health (PCH)
by pathcourse-health

Cheaper LLM inference, USDC agent payments via x402, agent identity / reputation lookup.

84 installs/wk local only
X402 MCP
by carboncashmere

177 crypto market intel endpoints with auto x402 USDC micropayments from your AI agent

77 installs/wk local only
DeriveAI x402 APIs
by deriveit33z-ship-it

25 pay-per-request intelligence APIs for AI agents via x402 micropayments (USDC/Base)

25 tools answering
AgentPay — Pay-per-call AI Microservices
by ronaldanton

22 AI microservices with x402 micropayments: summarize, translate, code-review. USDC on Base.

34 tools answering
Journalize
by journalize

Agent-native double-entry accounting ledger with x402 micropayments

11 tools answering
Clawfetch
by clawfetch

Web intelligence for AI agents: fetch, render, extract, research. x402 micropayments, no API keys.

180 installs/wk 10 tools local only

Telegraph — questions

Answers built from our own checks of this server.

Why is there no uptime for Telegraph?
Telegraph runs on your own machine over stdio — there is no network address to reach, so uptime cannot be measured for it by anyone. What can be measured is adoption: the npm package telegraph-protocol-mcp was installed 31 times last week.
How do I connect Telegraph?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It runs locally, so the command pulls telegraph-protocol-mcp straight from npm; nothing to host, nothing to sign up for.
How many people use Telegraph?
The npm package telegraph-protocol-mcp was installed 31 times in the last week. Week over week that is -7%. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.
Is Telegraph open source?
Yes — it is published under the MIT licence, written in TypeScript and 0 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.