TMCP Hub · Remote MCP gateway

Your AI client. One gateway. Only your access.

Connect a compatible AI client to TMCP with your own verified account. Discover tools you are authorized to use, without handing another user or integration your permissions.

Already have an account? Sign in. Client support for custom remote MCP depends on the client and plan.

Authenticated ChatGPT MCP calls proven Telegram login repair in progress

Two integration offers

Connect your own account or a reviewed service.

Telegram API applications and standard remote MCP servers are different products. Each keeps its own credentials and authorization boundary.

Personal app registration availableHosted login in repair

Personal Telegram

Register multiple Telegram-issued API applications under your verified identity, with no organization or TMCP approval required. Each Telegram account session belongs to its own authorized user.

  • Personal application self-service exists
  • Full hosted Telegram account sign-in is not yet live-proven
  • Telegram chooses phone, email and 2FA steps
Explore Telegram setup
Provider routing planned

Private MCP providers

Bring a compatible private HTTPS MCP service through reviewed admission, separate upstream authorization and precise user or organization grants.

  • Provider admission contract is defined
  • Public submission and generic routing are not implemented
  • Organization self-service is also pending
Understand private MCP

Your first connection

Three steps. No shared login.

Create your verified account

Use email registration, then verify that email. Existing users can sign in. Your TMCP identity is separate from a Telegram account.

Authorize a compatible client

In a client that supports remote MCP and OAuth, add https://tmcphub.com/mcp and authorize your own TMCP identity. ChatGPT connectivity and tool calls have been proven; availability depends on client support.

Use only granted services

See tools allowed for your identity. Register your own Telegram API application when needed; partner MCP services require separate admission and grants and are not live yet.

Current availability

What works now, and what is being built.

Verified live MCP connection

Remote client authorization

TMCP has completed authenticated ChatGPT MCP negotiation and tool calls. OAuth protection and the single remote gateway exist now.

Supported clients must provide remote MCP and OAuth capabilities. Not every client or subscription tier includes them.

Not yet launched

Other product capabilities

Hosted Telegram login still needs end-to-end confirmation after its repair. Generic private provider routing, new organization creation, embedded AI and payments remain unfinished. The independent synthetic Demo is live, but it is not connected through the TMCP provider catalog yet.

Availability is not inferred from an accepted specification or a completed source change.

Common questions

Know what you are connecting.

Is my TMCP login also a Telegram login?

No. TMCP verifies your email and authorizes your AI client. Telegram separately controls account sign-in, verification codes and optional two-step authentication.

Can I create my own Telegram API applications?

Yes. A verified Guest can register multiple personally owned Telegram-issued applications without platform approval, payment or an organization. An API application is not an authorized Telegram session.

Can I connect a private MCP server today?

Not yet. The standard provider contract exists, but organization self-service, provider submission, admission and runtime routing have not launched. See the planned partner process.

See all questions, setup guidance and recovery options

Get started

Start with one verified TMCP identity.

Explore permitted services and connect a compatible MCP client. No private provider is automatically enabled at registration.

Get started