{
  "markdown": "# Contexter\n\n**Share one AI context across ChatGPT, Claude and Telegram.**\n\nSave what you worked out with one AI, continue it in another — and share the context\nwith people in Telegram, who keep working on it in their own AI.\n\nContexter is a hosted **remote MCP server**. This repository is its public documentation:\nthe connection details, the tool catalogue and what does and does not move between tools.\nThe server itself is hosted and closed-source — there is nothing to install and no key to\nmanage.\n\n- **Homepage:** https://contexterai.com\n- **MCP endpoint:** `https://contexterai.com/mcp`\n- **Transport:** Streamable HTTP\n- **Authentication:** OAuth 2.1 (with protected-resource metadata discovery)\n- **Telegram bot:** [@ai_contexter_bot](https://t.me/ai_contexter_bot)\n- **Status:** early access, free, open to everyone\n\n---\n\n## The problem it solves\n\nYou plan something in ChatGPT. You continue it in Claude. You discuss it in a Telegram\ngroup. Every hop, you re-explain the project — and the person you are working with cannot\npick it up at all, because your history lives inside your account.\n\nContexter gives the project **one context** instead of one copy per tool. Both assistants\nread and write the same records. You can share that context with a person, and they\ncontinue it in whichever AI *they* use.\n\n**Nothing is imported automatically.** Connecting an assistant does not hand Contexter your\nchat history. Only the records you explicitly save — or ask your assistant to save — end up\nin a context.\n\n---\n\n## Connecting\n\n### Claude\n\nAdd a custom connector pointing at `https://contexterai.com/mcp`. Claude discovers the\nOAuth endpoints on its own; you sign in through Telegram and approve access once.\n\n### ChatGPT\n\nAdd Contexter as a connector with the same URL. Same OAuth flow.\n\n### Any other MCP client\n\nAnything that speaks Streamable HTTP with OAuth 2.1 works the same way — point it at\n`https://contexterai.com/mcp`.\n\nFull walkthroughs, including what travels between each pair of tools:\n\n- [ChatGPT and Claude](https://contexterai.com/chatgpt-claude)\n- [ChatGPT and Telegram](https://contexterai.com/chatgpt-telegram)\n- [Claude and Telegram](https://contexterai.com/claude-telegram)\n\n---\n\n## What you can ask an assistant to do\n\nOnce connected, you talk to your assistant normally. For example:\n\n> Create a context called \"Kitchen renovation\" in Contexter and put my measurement notes in it.\n\n> What is in my Dolomites hike context?\n\n> Save this comparison to the AI-bot context and share it with Anna.\n\n---\n\n## Tool catalogue\n\nTwenty-six tools in four groups. Write tools require a human decision — the client acts for\na person, and irreversible steps (sharing, publishing to a room, deletion) are confirmed\nrather than assumed.\n\n**Reading (8)** — `list_contexts`, `get_context_card`, `get_context_feed`, `list_records`,\n`list_sources`, `get_artifact`, `get_file`, `read_image_content`\n\n**Saving (7)** — `save_artifact`, `save_file`, `create_context`, `add_records_to_context`,\n`update_artifact`, `update_context`, `set_context_notifications`\n\n**Sharing (5)** — `share_context`, `revoke_context_access`, `check_share_audience`,\n`deliver_to_chat`, `invite_room_to_context`\n\n**Removing (6)** — `remove_record_from_context`, `delete_record`, `leave_context`,\n`restore_record`, `delete_context`, `restore_context`\n\nScopes, response shapes and the reasoning behind each one:\n[contexterai.com/developers](https://contexterai.com/developers).\n\n---\n\n## Use cases\n\n**Two assistants, one project.** Research in ChatGPT, drafting in Claude. The plan lives in\na context both reach, so neither one starts from an empty page.\n\n**Two people, two different AIs.** You share the context, not a document export. The other\nperson opens it from whatever assistant they already pay for.\n\n**A group chat that does not lose its decisions.** Add the bot to a Telegram group. Messages\nfrom the people who opt in become records; the context built from the chat is shared with\nthose same people, and each of them works on it in their own AI, outside the group.\n\n---\n\n## Privacy\n\n- AI chat history is **never** imported. Saving is always explicit.\n- A record's visibility is the visibility of the context it is in. There are no hidden\n  audiences: every shared context shows exactly who can see it.\n- In a Telegram group, only the messages of people who joined in are collected. Anyone who\n  has not is not collected at all.\n- Deletion is reversible for 7 days.\n\n[Privacy policy](https://contexterai.com/privacy) ·\n[Security model in plain words](https://contexterai.com/security) ·\n[Terms](https://contexterai.com/terms) ·\n[Subprocessors](https://contexterai.com/subprocessors)\n\n---\n\n## Support\n\nOpen an issue here, or message [@ai_contexter_bot](https://t.me/ai_contexter_bot) in\nTelegram. Questions and answers for people already using it:\n[contexterai.com/help](https://contexterai.com/help).\n",
  "bytes": 4896,
  "sha": "85a32a1ca1c995c2cddfc3756ac8dd6d6fbd590af54596e0cbb8e715398c1ad0",
  "repo_slug": "maaakso/contexter-mcp",
  "fonte": "repo",
  "truncated": false,
  "api": "https://agentalog.com/api/listings/mcp_io_github_maaakso_contexter_d0307c4e/readme"
}