telegraph-mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| EVM_NETWORK | No | EVM CAIP-2 network | eip155:* |
| SVM_NETWORK | No | Solana CAIP-2 network | solana:* |
| TELEGRAPH_NODE_URL | Yes | Telegraph node URL | http://localhost:7044 |
| REFRESH_INTERVAL_MS | No | Miner-tool refresh interval (ms). 0 to disable. | 300000 |
| TELEGRAPH_DAEMON_URL | Yes | Daemon API URL | http://localhost:8081 |
| TELEGRAPH_ENGINE_URL | Yes | Engine server URL | http://localhost:8080 |
| TELEGRAPH_EVM_PRIVATE_KEY | No | EVM private key (0x-prefixed hex) | |
| TELEGRAPH_SOLANA_PRIVATE_KEY | No | Solana private key (base58) |
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
No tools | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/telegraphprotocol/telegraph-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server