Developer · Remote MCP server
GramClaw
Manage Telegram outreach, campaigns, follow-ups, conversations, and pipelines from an MCP client.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.mar820/gramclaw- Version
- 0.1.0
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP
- Published
- 2026-09-09
- Updated
- 2026-09-09
- Publisher
- mar820 (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/mar820) · how
- Listed under
- Telegram MCP servers
- Website
- gramclaw.com/en/telegram-mcp
- Repository
- github.com/liquiden/grmcw
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://gramclaw.com/api/mcp?key={api_key} | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Checked
- Not requested: URL template placeholder
- Checked on
- 2026-10-05
How to connect GramClaw
GramClaw is a remote MCP server: there is nothing to install. Its endpoint is https://gramclaw.com/api/mcp?key={api_key}, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
The URL contains placeholders to fill in before connecting: {api_key}.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| GPUQuant AI InfrastructureSearch AI infrastructure, inspect facility evidence and explore sourced company relationships. | Remote · HTTPLive check: ✓ handshake |
| GRAFOMEM CGR CaptureRecord agent judgments and their real outcomes on GRAFOMEM Cloud. Capture now, score later. | Local · stdio |
| GrafyxReal-time codebase graph for AI assistants: call graphs, dependencies, symbol lookup. | Local · stdio |
| GrainRun SQL queries and inspect database schemas through safe, visible MCP tools. | Local · stdio |
| GranethPre-flight check for AI coding agents: hallucinated packages + secrets, 6 ecosystems, no account. | Remote & Local · HTTP, stdioLive check: ✗ no handshake |
| GraphifySearch indexed code, trace dependencies, assess change impact, and recall repository memory. | Remote · HTTPLive check: sign-in required |
| GraphkeeperMines git history for file co-change patterns into a queryable knowledge graph via MCP. | Local · stdio |
| GraphPilotStructural memory for coding agents: callers, callees, blast radius and symbols over MCP. | Local · stdio |