Contexter

io.github.maaaksoPublished by GitHub account maaaksov1.0.0Updated Oct 28, 2026

Share one project context across ChatGPT, Claude, Telegram and any MCP client.

VerifiedStreamable HTTPWeb executableKnowledge & MemoryCommunication & Collaboration

Overview

AI-generated overview

Hosted remote MCP server that keeps one shared project context across ChatGPT, Claude, Telegram and other MCP clients.

What you can do
  • Read contexts, context cards, feeds, records, sources, artifacts, files and images
  • Save and update artifacts, files, contexts and records, and set context notifications
  • Share contexts, check share audiences, deliver content to chats and invite rooms to a context
  • Remove, restore, delete or leave records and contexts, and revoke shared access
When to use it
Useful when you work on a project across several AI assistants or with other people, and want one shared set of saved notes instead of re-explaining the project in each tool. Also fits Telegram groups that want decisions captured and continued in each member's own AI.
Requirements
A remote MCP endpoint over Streamable HTTP; no install or API key. OAuth 2.1 sign-in, approved once through Telegram, is required. Works in Claude, ChatGPT and any client that supports Streamable HTTP with OAuth 2.1.
Before you install
Contexts can be shared with other people and Telegram groups, so saved records may become visible to those audiences; check who can see a context before saving. Write tools create, update, share and delete data, and deletion is only reversible for 7 days. In Telegram groups, messages from people who opted in are collected as records.

Installation

In SourceWeft

  1. Open Contexter in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.maaakso%2Fcontexter/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "contexter": {
      "type": "http",
      "url": "https://contexterai.com/mcp"
    }
  }
}

README

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: @ai_contexter_bot
  • 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:

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) — list_contexts, get_context_card, get_context_feed, list_records, list_sources, get_artifact, get_file, read_image_content

Saving (7) — save_artifact, save_file, create_context, add_records_to_context, update_artifact, update_context, set_context_notifications

Sharing (5) — share_context, revoke_context_access, check_share_audience, deliver_to_chat, invite_room_to_context

Removing (6) — remove_record_from_context, delete_record, leave_context, restore_record, delete_context, restore_context

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.

A group chat that does not lose its decisions. Add the bot to a Telegram group. Messages from the people who opt in become records; the context built from the chat is shared with those same people, and each of them works on it in their own AI, outside the group.

Privacy

  • AI chat history is never imported. Saving is always explicit.
  • A record's visibility is the visibility of the context it is in. There are no hidden audiences: every shared context shows exactly who can see it.
  • In a Telegram group, only the messages of people who joined in are collected. Anyone who has not is not collected at all.
  • Deletion is reversible for 7 days.

Privacy policy · Security model in plain words · Terms · Subprocessors

Support

Open an issue here, or message @ai_contexter_bot in Telegram. Questions and answers for people already using it: contexterai.com/help.

Source: README.md at commit 4324aea

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

75% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.