Connect once, then just talk
How to connect each of your assistants — and short answers to the questions people actually ask.
Steps
Four steps in
The steps below are the MCP path — every client that pastes the address, whatever that client calls the screen. In Telegram you are done at Start.
-
Add the MCP server
Take the path your own assistant asks for — the screens differ from client to client, and so do their names: ChatGPT keeps them under plugins, Claude under connectors. Telegram skips this step entirely.
-
Sign in
A standard OAuth 2.1 sign-in opens, and lists the permissions being asked for. We never ask for your assistant's password.
-
Press Start, then confirm
The button opens our bot; one tap on Start and the bot shows a card naming the app that is connecting and what it will be allowed to read. Confirm, and your Telegram is linked. Nothing to type, nothing to paste. If you did not start this sign-in yourself, refuse — somebody else is asking for your records.
-
Connected
The assistant reaches your contexts with the rights you granted.
Connecting
Connecting your AI
Contexter is a standard remote MCP server, so any assistant that speaks MCP can work with it. Only the way in differs from client to client.
MCP server address
The address is the whole configuration — there is nothing else to fill in. Telegram never asks for it: you just start the bot.
ChatGPT, Claude and Telegram
- ChatGPT
-
Lives under plugins, and only in developer mode — the setup opens in a browser, not in the mobile app. Turn the mode on first, or the page has nothing to add a server with.
Turn on developer modeThen open the plugins page and paste the address. Once the server is saved, the sign-in starts on its own.
Open ChatGPT plugins - Claude
-
Press + Add custom connector, paste the address and confirm — the setup opens in a browser, not in the mobile app. Claude registers itself with us automatically; you are never asked for a client id or a secret. Once the connector is there, Claude uses it on mobile too, saving included. On an organization account the connector is added by its owner in admin settings.
Open Claude connectors - Telegram
- No address to paste: open the bot and press Start. This is also the door that confirms every other one — the card you approve in the chat is what completes a sign-in started in another client.
Other MCP clients
- Cursor
-
Cursor's own install link — it opens the app and asks you to confirm.
Add to Cursor - Gemini CLI
-
One command adds the server to your Gemini CLI settings.
gemini mcp add --transport http contexter https://contexterai.com/mcp
FAQ
Questions people actually ask
Can I close the sign-in page after confirming in Telegram?
Keep it open for a few seconds — that page is the one that hands the finished connection back to your assistant. If it does get closed too early, the bot's message carries a Finish sign-in button for exactly that case.
The Telegram button opens nothing — what now?
On a desktop without Telegram installed there is a fallback right under the button:
a /link command with a short code, and a button to copy it. Send that
line to the bot yourself. The code is single-use and lives about five minutes; if it
expires, reload the sign-in page for a fresh one.
What happens the first time I connect?
Nothing to wait for. Your first message to the bot sets your account up right away, so you can connect from the start and everything goes straight through — nothing you write meanwhile is lost.
Should I grant write access right away?
Yes, if you plan to save things. Read and write are separate permissions, and the assistant reads the list of what it may do once, at connection time — granting writing later means reconnecting.
The assistant says it cannot save — is something broken?
Almost always it is the app mode, not the connection. In ChatGPT, saving works in the working mode; the app's plain chat can only read. Switch the mode, or save the same thing from Claude — it saves reliably, including on mobile.
A new ability was announced — why don't I see it?
Assistants read the list of available tools once, when they connect, then cache it. Reconnect in the assistant's settings and start a new chat — the same applies when you grant write access for the first time.
Something stopped working — what is the first thing to try?
Reconnect: disconnect, connect again, start a new chat. It re-runs sign-in, re-reads the tools and rebuilds the link. This also covers the case where the assistant reports the server as unavailable — after a reconnect it usually turns out it was not. Trying the same thing from another connected AI is the quickest cross-check.
Does deleting a Telegram message delete it from Contexter?
No — two different actions in two different places. Deletion in Contexter is deliberate and reversible for 7 days. Removing a record from one context is different again: the record stays with you and only leaves that context.
How do I invite someone into a context?
Ask your assistant to share the context, and the bot sends you a card with a Choose who to send it to button — Telegram opens its own chat picker and you send the invitation yourself. The person who opens it sees what the context is before joining, and joins only when they press the button.