Telegraph

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

Quick Install

Automated & IDE Setup

Copy the AI prompt to install this server into Claude Code, Cursor, or another agent — or use 1-click editor setup below.

Add to Cursor Add to VS Code

Not yet automatically verified

We haven't yet run this listing's install command through our automated sandbox check. This isn't a red flag — we're steadily working through the catalog.

Manual Client & Custom JSON ConfigExpand JSON ▾

Client Config & Setup

Choose your client or environment

Target File:~/Library/Application Support/Claude/claude_desktop_config.json

claude_desktop_config.json

{
  "mcpServers": {
    "telegraph": {
      "command": "npx",
      "args": [
        "-y",
        "telegraph-protocol-mcp"
      ]
    }
  }
}

💡 Paste the JSON block into your client's configuration file under mcpServers, then restart the application.

Documentation Overview

@telegraph/mcp-server

MCP server exposing Telegraph Protocol AI inference APIs as tools with automatic x402 micropayments.

Connects any MCP-compatible agent (Claude Desktop, Cursor, ElizaOS, LangChain, OpenClaw, Goose, etc.) to Telegraph's network of AI miners — weather forecasting, deepfake detection, LLM inference, AI-text detection, signal monitoring — with zero crypto code in the agent. The MCP server handles private key custody, payment signing, and transaction settlement internally.

Miners can be Bittensor subnets, hosted models, or any private API integrated via YAML. Some tool and field names still say subnet for legacy reasons — read it as "miner".

Documentation

Document	Description
Architecture	MCP protocol, tool categories, x402 auto-payment, client integrations
Troubleshooting	Common issues and solutions

Quick Start

Option A — npx (no clone, recommended once published)

bash

TELEGRAPH_NODE_URL=http://13.237.89.59:7044 \
TELEGRAPH_ENGINE_URL=http://13.237.89.59:8080 \
TELEGRAPH_DAEMON_URL=http://13.237.89.59:8081 \
TELEGRAPH_EVM_PRIVATE_KEY=0xyour_key_here \
npx -y telegraph-protocol-mcp

Option B — from source

bash

# 1. Clone and enter
git clone https://github.com/telegraphprotocol/telegraph-mcp
cd telegraph-mcp

# 2. Copy and edit .env
cp .env.example .env
# Edit: set TELEGRAPH_EVM_PRIVATE_KEY=0xyour_key_here

# 3. Install and build
npm install && npm run build

# 4. Run
npm start

Published to npm as telegraph-protocol-mcp and listed on the MCP Registry as io.github.telegraphprotocol/telegraph. Maintainers: see PUBLISHING.md.

Architecture

Code

Agent (Claude / Cursor / Eliza / etc.)
       │
       │ MCP protocol (JSON-RPC over stdio)
       │
┌──────▼─────────────────────────────────────────┐
│  Telegraph MCP Server (runs locally)            │
│                                                 │
│  ┌─────────┐  ┌──────────┐  ┌───────────────┐  │
│  │ Node    │  │ Engine   │  │ Daemon        │  │
│  │ :7044   │  │ :8080    │  │ :8081         │  │
│  ├─────────┤  ├──────────┤  ├───────────────┤  │
│  │ Status  │  │ Subnets  │  │ Health        │  │
│  │ Health  │  │ Ask      │  │ Categories    │  │
│  │ Subnets │  │ Direct   │  │ Questions     │  │
│  │ Dynamic │  │          │  │               │  │
│  └─────────┘  └──────────┘  └───────────────┘  │
│                                                 │
│  X402 payment handled transparently:            │
│    request → 402 → sign EIP-3009 → retry        │
└─────────────────────────────────────────────────┘

Configuration

All via environment variables (.env file or inline):

Variable	Required	Default	Description
`TELEGRAPH_NODE_URL`	Yes	`http://localhost:7044`	Telegraph node URL
`TELEGRAPH_ENGINE_URL`	Yes	`http://localhost:8080`	Engine server URL
`TELEGRAPH_DAEMON_URL`	Yes	`http://localhost:8081`	Daemon API URL
`TELEGRAPH_EVM_PRIVATE_KEY`	Yes*	—	EVM private key (`0x`-prefixed hex)
`TELEGRAPH_SOLANA_PRIVATE_KEY`	No*	—	Solana private key (base58)
`EVM_NETWORK`	No	`eip155:*`	EVM CAIP-2 network
`SVM_NETWORK`	No	`solana:*`	Solana CAIP-2 network
`REFRESH_INTERVAL_MS`	No	`300000`	Miner-tool refresh interval (ms). 0 to disable.

*At least one private key required.

Available Tools

Node Tools (no payment)

Tool	Description
`tg_node_status`	Node status, public key, chain info
`tg_node_subnets_health`	Miner integration health check
`tg_node_list_subnets`	Full miner catalog with metadata, schemas, endpoints

Engine Tools

Tool	Payment	Description
`tg_engine_list_subnets`	Free	List the miners the Engine can route to
`tg_engine_ask`	x402	Auto-routed inference (LLM picks the best miner for your query)
`tg_engine_ask_subnet`	x402	Direct inference through a specific miner by ID

Daemon Tools (no payment)

Tool	Description
`tg_daemon_health`	Daemon health check
`tg_daemon_categories`	Signal categories (POLITICS, ECONOMICS, TECHNOLOGY, CLIMATE, HEALTH, CRYPTO, SPORTS, …)
`tg_daemon_questions`	Query collected signals with filters (category, source, time, interest)

Dynamic Miner Tools (auto-discovered, x402 payment)

Tools for each miner endpoint are auto-generated from the Telegraph node's live integration registry. The live set changes on-chain, so treat this as a snapshot, not the source of truth (call tg_node_list_subnets for the current catalog):

Miner	Tools
Zeus (18) — Weather	`tg_zeus_predict`
ItsAI (32) — AI text detection	`tg_itsai_text_detector_detect`
Sapling (33) — AI content detection	`tg_sapling_ai_detector_detect`
BitMind (34) — Deepfake	`tg_bitmind_detect_image`, `tg_bitmind_detect_video`, `tg_bitmind_preprocess_video`, `tg_bitmind_get_video_upload_url`
OpenAI (102) — LLM / images	`tg_openai_chat`, `tg_openai_responses`, `tg_openai_embed`, `tg_openai_images_generate`, `tg_openai_moderate`

These update automatically. New miners registered on-chain appear within 5 minutes. Deregistered miners are cleaned up. The agent always sees only currently valid tools.

Some tool and field names contain subnet for legacy reasons — Telegraph began by integrating Bittensor subnets. Today a miner is any provider integrated via YAML, subnet or not.

How x402 Payments Work

When an agent calls a paid tool (e.g., tg_engine_ask):

MCP server sends request to Telegraph
Telegraph returns HTTP 402 with payment requirements in response header
@x402/fetch intercepts the 402, signs an EIP-3009 TransferWithAuthorization using your private key, attaches the signature as a PAYMENT header, and retries
Telegraph verifies the payment on-chain via the PayAI facilitator and returns the result

The agent and LLM never see the payment flow, private key, or blockchain transaction. It's fully transparent — the agent just sees a tool that returns results.

Integration Guides

Claude Desktop

Edit ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows).

Using npx (simplest — no clone or build):

config.json

{
  "mcpServers": {
    "telegraph": {
      "command": "npx",
      "args": ["-y", "telegraph-protocol-mcp"],
      "env": {
        "TELEGRAPH_NODE_URL": "http://13.237.89.59:7044",
        "TELEGRAPH_ENGINE_URL": "http://13.237.89.59:8080",
        "TELEGRAPH_DAEMON_URL": "http://13.237.89.59:8081",
        "TELEGRAPH_EVM_PRIVATE_KEY": "0xyour_key_here"
      }
    }
  }
}

Or pointing at a local build:

config.json

{
  "mcpServers": {
    "telegraph": {
      "command": "node",
      "args": ["/path/to/telegraph-mcp/dist/index.js"],
      "env": {
        "TELEGRAPH_NODE_URL": "http://13.237.89.59:7044",
        "TELEGRAPH_ENGINE_URL": "http://13.237.89.59:8080",
        "TELEGRAPH_DAEMON_URL": "http://13.237.89.59:8081",
        "TELEGRAPH_EVM_PRIVATE_KEY": "0xyour_key_here"
      }
    }
  }
}

Restart Claude Desktop. The Telegraph tools will appear in the tool list. Try asking "What's the weather in Lahore?" or "Use the Telegraph engine to explain what Bitcoin is."

Cursor

Add to Cursor Settings → MCP → Add new MCP server:

config.json

{
  "mcpServers": {
    "telegraph": {
      "command": "node",
      "args": ["/path/to/telegraph-mcp/dist/index.js"],
      "env": {
        "TELEGRAPH_NODE_URL": "http://13.237.89.59:7044",
        "TELEGRAPH_ENGINE_URL": "http://13.237.89.59:8080",
        "TELEGRAPH_DAEMON_URL": "http://13.237.89.59:8081",
        "TELEGRAPH_EVM_PRIVATE_KEY": "0xyour_key_here"
      }
    }
  }
}

ElizaOS

In your Eliza character file or MCP plugin config:

config.json

{
  "mcp": {
    "telegraph": {
      "command": "node",
      "args": ["/path/to/telegraph-mcp/dist/index.js"],
      "env": {
        "TELEGRAPH_NODE_URL": "http://13.237.89.59:7044",
        "TELEGRAPH_ENGINE_URL": "http://13.237.89.59:8080",
        "TELEGRAPH_DAEMON_URL": "http://13.237.89.59:8081",
        "TELEGRAPH_EVM_PRIVATE_KEY": "0xyour_key_here"
      }
    }
  }
}

ElizaOS v0.25+ supports MCP via the @elizaos/plugin-mcp package. Enable it in your character's plugin list:

config.json

{
  "plugins": ["@elizaos/plugin-mcp"]
}

LangChain / LangGraph

LangChain supports MCP through langchain-mcp-adapters:

Terminal

pip install langchain-mcp-adapters

server.ts

from langchain_mcp_adapters.client import MultiServerMCPClient

client = MultiServerMCPClient({
    "telegraph": {
        "command": "node",
        "args": ["/path/to/telegraph-mcp/dist/index.js"],
        "env": {
            "TELEGRAPH_NODE_URL": "http://13.237.89.59:7044",
            "TELEGRAPH_ENGINE_URL": "http://13.237.89.59:8080",
            "TELEGRAPH_DAEMON_URL": "http://13.237.89.59:8081",
            "TELEGRAPH_EVM_PRIVATE_KEY": "0xyour_key_here",
        },
        "transport": "stdio",
    }
})

tools = client.get_tools()
# Use tools with your LangChain agent

TypeScript/Node.js:

Terminal

npm install @langchain/mcp-adapters

server.ts

import { MultiServerMCPClient } from "@langchain/mcp-adapters";

Read the full README →View source on GitHub →

Related MCP Servers

View all in Finance & Fintech View all alternatives

Reviews

No reviews yet — be the first to share how this listing worked for you.

Frequently Asked Questions about Telegraph

Add the following block to your claude_desktop_config.json under mcpServers: "mcpServers": { "telegraph": { "command": "npx", "args": ["-y", "telegraph"] } }

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:

Live Dynamic SVG Preview

Markdown (GitHub README)

[![AllMCPs](https://allmcps.com/api/badge/telegraph?style=directory)](https://allmcps.com/mcp/telegraph)

HTML Embed

<a href="https://allmcps.com/mcp/telegraph"><img src="https://allmcps.com/api/badge/telegraph?style=directory" alt="Telegraph on AllMCPs" /></a>

Technical Specs & Signals

CategoryFinance & Fintech

36Quality signal: Fair · 36/100How this signal is calculated ▾

Server availabilityNot measured

Not scored for repo-hosted servers — we can't reach the running server, only its GitHub page. Hosted MCP endpoints are health-checked live.

Verified ownership10/20

Documentation & tools16/30

Adoption & activity1/15

Community engagement0/10

A guidance signal from public completeness & health data — not a user rating. New listings start lower and rise as they add docs, get verified, and grow adoption. Signals we can't observe for a listing are skipped, not counted against it.

★ Featured

Moxie Docs MCP

MCP & Agent Skills for Automated Documentation, and codebase conventions + context

Explore Server →

Own this project?

This directory is pre-filled from public sources. Claim via GitHub README, site badge, or DNS TXT to unlock edit access and the Official badge — proof is checked automatically, then reviewed by our team.

Free dofollow backlink: add your website and place the AllMCPs badge on it — no claim needed. We detect it automatically and keep it verified as long as the badge stays live.

Claim & get free dofollow

Share & Embed

Add our SVG badge (dark/light directory styles) or embeddable widget to your site.

Explore more

More in 💰 Finance & Fintech →Best MCP servers for Finance & Fintech →Alternatives to Telegraph →Install in Claude Desktop Install in Cursor Install in VS Code

Telegraph

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

Quick Install

Automated & IDE Setup

Copy the AI prompt to install this server into Claude Code, Cursor, or another agent — or use 1-click editor setup below.

Add to Cursor Add to VS Code

Not yet automatically verified

We haven't yet run this listing's install command through our automated sandbox check. This isn't a red flag — we're steadily working through the catalog.

Manual Client & Custom JSON ConfigExpand JSON ▾

Client Config & Setup

Choose your client or environment

Target File:~/Library/Application Support/Claude/claude_desktop_config.json

claude_desktop_config.json

{
  "mcpServers": {
    "telegraph": {
      "command": "npx",
      "args": [
        "-y",
        "telegraph-protocol-mcp"
      ]
    }
  }
}

💡 Paste the JSON block into your client's configuration file under mcpServers, then restart the application.

Documentation Overview

@telegraph/mcp-server

MCP server exposing Telegraph Protocol AI inference APIs as tools with automatic x402 micropayments.

Miners can be Bittensor subnets, hosted models, or any private API integrated via YAML. Some tool and field names still say subnet for legacy reasons — read it as "miner".

Documentation

Document	Description
Architecture	MCP protocol, tool categories, x402 auto-payment, client integrations
Troubleshooting	Common issues and solutions

Quick Start

Option A — npx (no clone, recommended once published)

bash

TELEGRAPH_NODE_URL=http://13.237.89.59:7044 \
TELEGRAPH_ENGINE_URL=http://13.237.89.59:8080 \
TELEGRAPH_DAEMON_URL=http://13.237.89.59:8081 \
TELEGRAPH_EVM_PRIVATE_KEY=0xyour_key_here \
npx -y telegraph-protocol-mcp

Option B — from source

bash

# 1. Clone and enter
git clone https://github.com/telegraphprotocol/telegraph-mcp
cd telegraph-mcp

# 2. Copy and edit .env
cp .env.example .env
# Edit: set TELEGRAPH_EVM_PRIVATE_KEY=0xyour_key_here

# 3. Install and build
npm install && npm run build

# 4. Run
npm start

Published to npm as telegraph-protocol-mcp and listed on the MCP Registry as io.github.telegraphprotocol/telegraph. Maintainers: see PUBLISHING.md.

Architecture

Code

Agent (Claude / Cursor / Eliza / etc.)
       │
       │ MCP protocol (JSON-RPC over stdio)
       │
┌──────▼─────────────────────────────────────────┐
│  Telegraph MCP Server (runs locally)            │
│                                                 │
│  ┌─────────┐  ┌──────────┐  ┌───────────────┐  │
│  │ Node    │  │ Engine   │  │ Daemon        │  │
│  │ :7044   │  │ :8080    │  │ :8081         │  │
│  ├─────────┤  ├──────────┤  ├───────────────┤  │
│  │ Status  │  │ Subnets  │  │ Health        │  │
│  │ Health  │  │ Ask      │  │ Categories    │  │
│  │ Subnets │  │ Direct   │  │ Questions     │  │
│  │ Dynamic │  │          │  │               │  │
│  └─────────┘  └──────────┘  └───────────────┘  │
│                                                 │
│  X402 payment handled transparently:            │
│    request → 402 → sign EIP-3009 → retry        │
└─────────────────────────────────────────────────┘

Configuration

All via environment variables (.env file or inline):

Variable	Required	Default	Description
`TELEGRAPH_NODE_URL`	Yes	`http://localhost:7044`	Telegraph node URL
`TELEGRAPH_ENGINE_URL`	Yes	`http://localhost:8080`	Engine server URL
`TELEGRAPH_DAEMON_URL`	Yes	`http://localhost:8081`	Daemon API URL
`TELEGRAPH_EVM_PRIVATE_KEY`	Yes*	—	EVM private key (`0x`-prefixed hex)
`TELEGRAPH_SOLANA_PRIVATE_KEY`	No*	—	Solana private key (base58)
`EVM_NETWORK`	No	`eip155:*`	EVM CAIP-2 network
`SVM_NETWORK`	No	`solana:*`	Solana CAIP-2 network
`REFRESH_INTERVAL_MS`	No	`300000`	Miner-tool refresh interval (ms). 0 to disable.

*At least one private key required.

Available Tools

Node Tools (no payment)

Tool	Description
`tg_node_status`	Node status, public key, chain info
`tg_node_subnets_health`	Miner integration health check
`tg_node_list_subnets`	Full miner catalog with metadata, schemas, endpoints

Engine Tools

Tool	Payment	Description
`tg_engine_list_subnets`	Free	List the miners the Engine can route to
`tg_engine_ask`	x402	Auto-routed inference (LLM picks the best miner for your query)
`tg_engine_ask_subnet`	x402	Direct inference through a specific miner by ID

Daemon Tools (no payment)

Tool	Description
`tg_daemon_health`	Daemon health check
`tg_daemon_categories`	Signal categories (POLITICS, ECONOMICS, TECHNOLOGY, CLIMATE, HEALTH, CRYPTO, SPORTS, …)
`tg_daemon_questions`	Query collected signals with filters (category, source, time, interest)

Dynamic Miner Tools (auto-discovered, x402 payment)

Miner	Tools
Zeus (18) — Weather	`tg_zeus_predict`
ItsAI (32) — AI text detection	`tg_itsai_text_detector_detect`
Sapling (33) — AI content detection	`tg_sapling_ai_detector_detect`
BitMind (34) — Deepfake	`tg_bitmind_detect_image`, `tg_bitmind_detect_video`, `tg_bitmind_preprocess_video`, `tg_bitmind_get_video_upload_url`
OpenAI (102) — LLM / images	`tg_openai_chat`, `tg_openai_responses`, `tg_openai_embed`, `tg_openai_images_generate`, `tg_openai_moderate`

These update automatically. New miners registered on-chain appear within 5 minutes. Deregistered miners are cleaned up. The agent always sees only currently valid tools.

Some tool and field names contain subnet for legacy reasons — Telegraph began by integrating Bittensor subnets. Today a miner is any provider integrated via YAML, subnet or not.

How x402 Payments Work

When an agent calls a paid tool (e.g., tg_engine_ask):

MCP server sends request to Telegraph
Telegraph returns HTTP 402 with payment requirements in response header
@x402/fetch intercepts the 402, signs an EIP-3009 TransferWithAuthorization using your private key, attaches the signature as a PAYMENT header, and retries
Telegraph verifies the payment on-chain via the PayAI facilitator and returns the result

The agent and LLM never see the payment flow, private key, or blockchain transaction. It's fully transparent — the agent just sees a tool that returns results.

Integration Guides

Claude Desktop

Edit ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows).

Using npx (simplest — no clone or build):

config.json

{
  "mcpServers": {
    "telegraph": {
      "command": "npx",
      "args": ["-y", "telegraph-protocol-mcp"],
      "env": {
        "TELEGRAPH_NODE_URL": "http://13.237.89.59:7044",
        "TELEGRAPH_ENGINE_URL": "http://13.237.89.59:8080",
        "TELEGRAPH_DAEMON_URL": "http://13.237.89.59:8081",
        "TELEGRAPH_EVM_PRIVATE_KEY": "0xyour_key_here"
      }
    }
  }
}

Or pointing at a local build:

config.json

{
  "mcpServers": {
    "telegraph": {
      "command": "node",
      "args": ["/path/to/telegraph-mcp/dist/index.js"],
      "env": {
        "TELEGRAPH_NODE_URL": "http://13.237.89.59:7044",
        "TELEGRAPH_ENGINE_URL": "http://13.237.89.59:8080",
        "TELEGRAPH_DAEMON_URL": "http://13.237.89.59:8081",
        "TELEGRAPH_EVM_PRIVATE_KEY": "0xyour_key_here"
      }
    }
  }
}

Restart Claude Desktop. The Telegraph tools will appear in the tool list. Try asking "What's the weather in Lahore?" or "Use the Telegraph engine to explain what Bitcoin is."

Cursor

Add to Cursor Settings → MCP → Add new MCP server:

config.json

{
  "mcpServers": {
    "telegraph": {
      "command": "node",
      "args": ["/path/to/telegraph-mcp/dist/index.js"],
      "env": {
        "TELEGRAPH_NODE_URL": "http://13.237.89.59:7044",
        "TELEGRAPH_ENGINE_URL": "http://13.237.89.59:8080",
        "TELEGRAPH_DAEMON_URL": "http://13.237.89.59:8081",
        "TELEGRAPH_EVM_PRIVATE_KEY": "0xyour_key_here"
      }
    }
  }
}

ElizaOS

In your Eliza character file or MCP plugin config:

config.json

{
  "mcp": {
    "telegraph": {
      "command": "node",
      "args": ["/path/to/telegraph-mcp/dist/index.js"],
      "env": {
        "TELEGRAPH_NODE_URL": "http://13.237.89.59:7044",
        "TELEGRAPH_ENGINE_URL": "http://13.237.89.59:8080",
        "TELEGRAPH_DAEMON_URL": "http://13.237.89.59:8081",
        "TELEGRAPH_EVM_PRIVATE_KEY": "0xyour_key_here"
      }
    }
  }
}

ElizaOS v0.25+ supports MCP via the @elizaos/plugin-mcp package. Enable it in your character's plugin list:

config.json

{
  "plugins": ["@elizaos/plugin-mcp"]
}

LangChain / LangGraph

LangChain supports MCP through langchain-mcp-adapters:

Terminal

pip install langchain-mcp-adapters

server.ts

from langchain_mcp_adapters.client import MultiServerMCPClient

client = MultiServerMCPClient({
    "telegraph": {
        "command": "node",
        "args": ["/path/to/telegraph-mcp/dist/index.js"],
        "env": {
            "TELEGRAPH_NODE_URL": "http://13.237.89.59:7044",
            "TELEGRAPH_ENGINE_URL": "http://13.237.89.59:8080",
            "TELEGRAPH_DAEMON_URL": "http://13.237.89.59:8081",
            "TELEGRAPH_EVM_PRIVATE_KEY": "0xyour_key_here",
        },
        "transport": "stdio",
    }
})

tools = client.get_tools()
# Use tools with your LangChain agent

TypeScript/Node.js:

Terminal

npm install @langchain/mcp-adapters

server.ts

import { MultiServerMCPClient } from "@langchain/mcp-adapters";

Read the full README →View source on GitHub →

Related MCP Servers

View all in Finance & Fintech View all alternatives

Reviews

No reviews yet — be the first to share how this listing worked for you.

Frequently Asked Questions about Telegraph

Add the following block to your claude_desktop_config.json under mcpServers: "mcpServers": { "telegraph": { "command": "npx", "args": ["-y", "telegraph"] } }

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:

Live Dynamic SVG Preview

Markdown (GitHub README)

[![AllMCPs](https://allmcps.com/api/badge/telegraph?style=directory)](https://allmcps.com/mcp/telegraph)

HTML Embed

<a href="https://allmcps.com/mcp/telegraph"><img src="https://allmcps.com/api/badge/telegraph?style=directory" alt="Telegraph on AllMCPs" /></a>

Technical Specs & Signals

CategoryFinance & Fintech

36Quality signal: Fair · 36/100How this signal is calculated ▾

Server availabilityNot measured

Not scored for repo-hosted servers — we can't reach the running server, only its GitHub page. Hosted MCP endpoints are health-checked live.

Verified ownership10/20

Documentation & tools16/30

Adoption & activity1/15

Community engagement0/10

★ Featured

Moxie Docs MCP

MCP & Agent Skills for Automated Documentation, and codebase conventions + context

Explore Server →

Own this project?

Free dofollow backlink: add your website and place the AllMCPs badge on it — no claim needed. We detect it automatically and keep it verified as long as the badge stays live.

Claim & get free dofollow

Share & Embed

Add our SVG badge (dark/light directory styles) or embeddable widget to your site.

Explore more

More in 💰 Finance & Fintech →Best MCP servers for Finance & Fintech →Alternatives to Telegraph →Install in Claude Desktop Install in Cursor Install in VS Code