Connect Telegram to Cursor.
Connect selected chats through your personal ChatMate bot and add its MCP server to Cursor. Find a tester’s bug report, open the attached log, fix the code and ask the agent to reply to the group when the work is done.
Cursor on a Mac: the owner asks the agent to fix the cart crash Sofia reported in the QA · Mobile Telegram group. The agent finds her message, reads the attached log, fixes CartViewController.swift and replies to Sofia in the group after the owner presses Run tool.
- Add it
- One click or ~/.cursor/mcp.json
- Works in
- Cursor editor, CLI and Cloud Agents
- Telegram access
- Selected private chats and groups
- Sign-in
- With Telegram, no API keys
Connect Cursor.
The editor and the CLI share mcp.json. Cloud Agents sign in separately.
First, your personal bot
Cursor reads Telegram through your own ChatMate bot. Create it in @chatmate_agent and connect the chats you want. It takes a couple of minutes in Telegram and is done once for every AI.
How to create the bot and connect chatsAdd ChatMate to Cursor
Add to CursorPress the button on the computer with Cursor. Cursor shows the server and asks before it installs it.
Or put it in mcp.json
Use ~/.cursor/mcp.json for every project, or .cursor/mcp.json in one project.
~/.cursor/mcp.json { "mcpServers": { "chatmate": { "url": "https://www.getchatmate.com/api/connector/mcp" } } }Sign in with Telegram
Open Customize, find ChatMate and log in. Sign in with Telegram in the browser and allow access. In the terminal, the CLI uses the same file and needs one login:
Terminal agent mcp login chatmateCloud Agents
cursor.com/agentsMCP
Add the address from the MCP menu at cursor.com/agents. Cloud Agents sign in separately, once per person.
What works in Cursor.
Cursor reads the chats you connected, from the moment you connected them and up to 30 days back.
Bug reports from chats
A tester’s message in a QA group, with the steps and the device, becomes the agent’s starting point.
Logs and screenshots
Files people attached in connected chats, opened next to your code.
A reply after Run tool
Cursor asks before MCP tools by default, so the message to the group waits for your click.
Editor and terminal
The CLI reads the same mcp.json, so the agent in your terminal sees the same chats.
Questions about Cursor.
- Do I need a paid Cursor plan?
Cursor’s MCP docs name no plan requirement for adding custom servers.
- How do I connect Grok Bot?
Grok Bot has its own setup. Ask it to add ChatMate and sign in with Telegram. Follow the Grok Bot guide.
- And grok.com?
grok.com is separate from Grok Bot. Open grok.com/connectors, press New Connector, choose Custom, paste the address and sign in. xAI says connectors are open to every Grok user. The steps are on the Grok page.
- Is this one of the Telegram MCP servers on GitHub?
No. Those run on your machine and log in to Telegram with an api_id. ChatMate is hosted and reads only what your personal bot receives: the private chats you pick in Chat Automation and the groups you add it to.
- The button didn’t open Cursor
It opens Cursor on the computer where you press it. On a phone, or if Cursor isn’t installed there, add the server to mcp.json instead.
Next to Cursor other ways in.
The same ChatMate in the other coding agents.
- Claude CodeOne claude mcp add, or nothing at all if you added ChatMate on claude.ai.
CodexAlready there in the ChatGPT desktop app once ChatMate is in ChatGPT; one codex mcp add for the CLI and the IDE extension.- Grok BotGrok Bot adds ChatMate when you ask it in a message, with its own Telegram sign-in.
