Skip to Content
Telegram MCPAPIAPI Documentation

API Documentation

This folder holds the MCP tool API surface for the Telegram MCP Server: one document per tool (or per tool group), covering input schema, output shape, error codes, and example payloads. The audience is the agent author — anyone wiring Claude (or another MCP client) up to this server.

When this gets populated

Starts filling in Phase 2 as the first tools land (send_message, send_image, edit_message, send_buttons) and grows phase by phase:

  • Phase 2 — messaging tools
  • Phase 3 — admin tools (approve_user, set_role)
  • Phase 4 — memory tools (update_memory, store_memory, get_chat_history, get_user_context)
  • Phase 5 — job tools (create_job, get_job_status, cancel_job)
  • Phase 7 — multi-modal extensions (send_document, image source variants)

Until then, the authoritative contract specs live in ../plan/data-and-contracts.md.

See ../plan/ for what’s being built and when.

Architecture DocumentationConfig