Schema | telegram-mcp-bridge

telegram-mcp-bridge

Describes the environment variables required to run the server.

Name	Required	Description	Default
`MCP_HOST`	No	Host address for the MCP HTTP server to bind to.	127.0.0.1
`MCP_AUTH_TOKEN`	No	Bearer token required for HTTP MCP. Must be at least 32 characters.
`PUBLIC_BASE_URL`	No	Public base URL of the bridge, e.g. https://bridge.example.com
`BRIDGE_TRANSPORT`	No	Transport mode for the MCP server. Use 'http' for the server profile. Defaults to 'stdio' for local mode.	stdio
`MCP_ALLOWED_HOSTS`	No	Comma-separated list of allowed Host headers, e.g. bridge.example.com
`TELEGRAM_ALLOW_ALL`	No	Set to 'true' to allow all inbound users/chats when the ingress allowlist is empty. Outbound sending remains blocked unless TELEGRAM_ALLOWED_CHAT_IDS is set.	false
`TELEGRAM_BOT_TOKEN`	Yes	Telegram bot token obtained from @BotFather.
`TELEGRAM_INGRESS_MODE`	No	Telegram ingress mode: 'webhook' for the server profile, 'polling' (long polling) for local mode.	polling
`TELEGRAM_WEBHOOK_SECRET`	No	Secret token used to validate X-Telegram-Bot-Api-Secret-Token for webhook requests.
`TELEGRAM_ALLOWED_CHAT_IDS`	Yes	Numeric allowlist of authorized chat IDs, authorizing both inbound chats and outbound destinations.
`TELEGRAM_ALLOWED_USER_IDS`	Yes	Numeric allowlist of authorized inbound user IDs. If both this and TELEGRAM_ALLOWED_CHAT_IDS are populated, an event must satisfy both.

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Server capabilities have not been inspected yet.

Functions exposed to the LLM to take actions

Name	Description
No tools

Interactive templates invoked by user choice

Name	Description
No prompts

Contextual data attached and managed by the client

Name	Description
No resources

This server cannot be deployed

ActivityMaintained

ResponsivenessNo issues