MCP and its methods

Contexter is a Model Context Protocol server over Streamable HTTP. Clients authorise with OAuth 2.1 and get tools scoped to one person's contexts.

The server

One address, standard protocols

Any assistant that speaks MCP can work with it — ChatGPT, Claude, Cursor and Gemini CLI all take the same address. Step-by-step guides for each client are on the help page.

MCP server address

https://contexterai.com/mcp

Streamable HTTP. Discovery, dynamic client registration and OAuth 2.1 are advertised from the same origin.

contexts:read messages:read artifacts:write

Tools

Twenty-six tools, four purposes

Reading, saving, sharing, removing. Every write goes through the permissions the person granted at sign-in.

Reading · 8 tools

Finding out what is already there. Nothing changes.

list_contexts
Every context you can open — your own and the ones shared with you — each with the people who see it.
get_context_card
One context at a glance: what it is about, how much is in it, who is in it, what arrived last. Built by the server, not retold by the model.
get_context_feed
The records of one context, page by page, with markers where something was deleted.
list_records
Everything you have — Telegram messages and saved AI results — searchable.
list_sources
Which chats your records came from, under their human names.
get_artifact
The full text of one saved result, not just its opening lines.
get_file
A download link for a file attached to a record. Single use, fifteen minutes.
read_image_content
The picture itself, handed to the model that asked for it — not a link to it.

Saving · 7 tools

Putting something in, and correcting it afterwards.

save_artifact
Save a result of the conversation into a context. A context of the same name is reused, never duplicated.
save_file
Save something the assistant composed as a file — a table, a document, an image.
create_context
Start an empty context. Empty is a valid state.
add_records_to_context
File records you already have into a context. Messages and results mix freely.
update_artifact
Edit a saved result of your own. Telegram messages are never editable.
update_context
Rename your context or change its description.
set_context_notifications
Turn the alerts about a shared context on or off. Yours alone: it changes nothing for anybody else in it.

Sharing · 5 tools

Letting a person in, and taking them out again.

share_context
Two steps. First you see how many records, and whose, a new member would immediately read; only after you agree is an invitation issued. It arrives as a card in your own Telegram, where you pick the recipient with Telegram's chat picker — no link is ever printed into the chat.
revoke_context_access
Take a person out of a context. Owner only, always by hand.
check_share_audience
Who would see a context if you shared it, asked before anything is shared. The confirmation that follows names those people.
deliver_to_chat
Publish a result into a Telegram group you take part in — your assistant’s words, and existing records alongside them. It never sends by itself: a confirmation card appears in your private chat with the bot, showing the chat, the text and how many people will read it, and the message leaves only when you press it. What arrives joins that chat’s records under your name, with buttons to file it into one of the chat’s contexts.
invite_room_to_context
Invite the people of a Telegram group into a context made from that group. Only those who have opened the bot to the room can accept.

Removing · 6 tools

Taking things out — and putting them back, which is half of this group.

remove_record_from_context
Unfile a record from one context. It stays with its owner.
delete_record
Delete your own record everywhere. Soft for 7 days.
leave_context
Step out of a context shared with you. It needs nobody's permission, because it takes access away rather than granting it. What you added stays.
restore_record
Undo that, inside the seven days.
delete_context
Delete the context, not its contents. Records stay with their owners.
restore_context
Bring the context back, with its records and its members.

Write tools need a human decision. The client acts for a person and is never a subject of rights: the token carries the scopes of whoever completed the Telegram link step, and anything that widens an audience waits for a yes. Text arriving inside records, chat titles or names is data, not instructions.