Skip to Content
Telegram MCPArchitectureArchitecture Documentation

Architecture Documentation

Architecture-as-built: component boundaries, data flow, request lifecycles, and the MCP session/push model. Sits at a level higher than individual modules (which live in ../components/).

Pages

PhasePage
1phase-1-inbound.md — Telegram update → echo reply lifecycle

Later phases will add:

  • Phase 2 — HTTP/Fastify + MCP transport layout, /mcp request lifecycle, JSON-RPC error mapping.
  • Phase 5 — Async job flow: webhook → enqueue → Inngest → push notification back to agent.
  • Phase 6 — End-to-end picture once the external Claude agent is connected.

See also

  • ../plan/design-overview.md — design intent for the whole system. Where this folder is “as-built”, that doc is “as-planned”. The two are kept in sync.
  • ../plan/ — current phase + deliverables.