Contexter MCP server
online · 100% uptimeio.github.maaakso/contexter·v1.0.0·1 starsShare one project context across ChatGPT, Claude, Telegram and any MCP client.
1 stars
Reviews
Write oneNobody has reviewed Contexter yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Contexter tools
Tool list not cached yet. `describe` through the gateway fetches it live.
Public scan report
scanner v0.1.10 · 2026-10-30 · same rubric, same numbers if you re-run it
- –Code scanremote-only server, no package to scann/a
- Live reliabilityremote reachable in 483ms (auth required)20/20
- –Tool poisoningtools not inspected (endpoint requires auth); not countedn/a
- Auth qualityOAuth resource metadata advertised on 40115/15
- Maintenancelast push 62 days ago12/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
How Contexter compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 92/100
- higher than 93% of 48,243 servers
- Uptime
- 100%
- of our recent checks; the typical remote server answers 100%
- Response time
- 614 ms
- faster than 26% of 30,027 servers
- GitHub stars
- 1
- more than 65% of 28,706 servers
Install Contexter in Claude Code, Cursor or VS Code
claude mcp add --transport http contexter https://contexterai.com/mcp
What the publisher says
From the Contexter repository's README, as published. We do not edit it. Read it on GitHub
Contexter
Share one AI context across ChatGPT, Claude and Telegram.
Save what you worked out with one AI, continue it in another — and share the context with people in Telegram, who keep working on it in their own AI.
Contexter is a hosted remote MCP server. This repository is its public documentation: the connection details, the tool catalogue and what does and does not move between tools. The server itself is hosted and closed-source — there is nothing to install and no key to manage.
- Homepage: https://contexterai.com
- MCP endpoint: https://contexterai.com/mcp
- Transport: Streamable HTTP
- Authentication: OAuth 2.1 (with protected-resource metadata discovery)
- Telegram bot: @aicontexterbot
- Status: early access, free, open to everyone
The problem it solves
You plan something in ChatGPT. You continue it in Claude. You discuss it in a Telegram group. Every hop, you re-explain the project — and the person you are working with cannot pick it up at all, because your history lives inside your account.
Contexter gives the project one context instead of one copy per tool. Both assistants read and write the same records. You can share that context with a person, and they continue it in whichever AI they use.
Nothing is imported automatically. Connecting an assistant does not hand Contexter your chat history. Only the records you explicitly save — or ask your assistant to save — end up in a context.
Connecting
Claude
Add a custom connector pointing at https://contexterai.com/mcp. Claude discovers the OAuth endpoints on its own; you sign in through Telegram and approve access once.
ChatGPT
Add Contexter as a connector with the same URL. Same OAuth flow.
Any other MCP client
Anything that speaks Streamable HTTP with OAuth 2.1 works the same way — point it at https://contexterai.com/mcp.
Full walkthroughs, including what travels between each pair of tools:
- ChatGPT and Claude
- ChatGPT and Telegram
- Claude and Telegram
What you can ask an assistant to do
Once connected, you talk to your assistant normally. For example:
Create a context called "Kitchen renovation" in Contexter and put my measurement notes in it.
What is in my Dolomites hike context?
Save this comparison to the AI-bot context and share it with Anna.
Tool catalogue
Twenty-six tools in four groups. Write tools require a human decision — the client acts for a person, and irreversible steps (sharing, publishing to a room, deletion) are confirmed rather than assumed.
Reading (8) — listcontexts, getcontextcard, getcontextfeed, listrecords, listsources, getartifact, getfile, readimage_content
Saving (7) — saveartifact, savefile, createcontext, addrecordstocontext, updateartifact, updatecontext, setcontextnotifications
Sharing (5) — sharecontext, revokecontextaccess, checkshareaudience, delivertochat, inviteroomtocontext
Removing (6) — removerecordfromcontext, deleterecord, leavecontext, restorerecord, deletecontext, restorecontext
Scopes, response shapes and the reasoning behind each one: contexterai.com/developers.
Use cases
Two assistants, one project. Research in ChatGPT, drafting in Claude. The plan lives in a context both reach, so neither one starts from an empty page.
Two people, two different AIs. You share the context, not a document export. The other person opens it from whatever assistant they already pay for.
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Contexter: common questions
- Is Contexter MCP server safe?
- Yes, by our scan: it is graded A (92/100). Read the Contexter safety report
- How do I install Contexter?
- It runs remotely at contexterai.com. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
- Does Contexter need an API key?
- No key to paste: it signs you in with OAuth when your client connects.
- Is Contexter maintained?
- The last commit was 68 days ago (2026-08-29). The latest release is v1.0.0.
- Is Contexter up?
- 100% of our last 28 checks got an answer. We check remote servers about four times a day.
- How does Contexter compare with other MCP servers?
- safety score 92/100 (higher than 93% of 48,243 servers); uptime 100% (of our recent checks; the typical remote server answers 100%); response time 614 ms (faster than 26% of 30,027 servers). Full comparison.