Contexter

io.github.maaakso由 GitHub 账号 maaakso 发布v1.0.0更新于 Oct 28, 2026

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

已验证Streamable HTTP可网页运行知识与记忆沟通与协作

概览

AI 生成的概览

托管式远程 MCP 服务器,让 ChatGPT、Claude、Telegram 等 MCP 客户端共用同一份项目上下文。

可以做什么
  • 读取上下文、上下文卡片、动态流、记录、来源、产物、文件与图片
  • 保存和更新产物、文件、上下文与记录,并设置上下文通知
  • 分享上下文、检查分享对象、把内容投递到聊天、邀请房间加入上下文
  • 移除、恢复、删除或退出记录与上下文,并撤销已分享的访问权限
适用场景
适合在多个 AI 助手之间或与他人协作推进同一项目,希望用一份共享的已保存资料代替在每个工具里重复说明背景。也适合希望把群聊中的决定沉淀下来、再由各成员在自己的 AI 中继续的 Telegram 群组。
运行要求
需要远程 MCP 端点(Streamable HTTP),无需安装或 API 密钥。必须通过 OAuth 2.1 登录,并经 Telegram 批准一次。可用于 Claude、ChatGPT 以及任何支持 Streamable HTTP 与 OAuth 2.1 的客户端。
安装前请注意
上下文可分享给他人和 Telegram 群组,保存的记录可能对这些对象可见,保存前应确认可见范围。写入类工具会创建、更新、分享和删除数据,删除仅在 7 天内可恢复。在 Telegram 群组中,已加入者的消息会被收集为记录。

安装

在 SourceWeft 中

  1. 打开 控制台中的 Contexter,将其添加到工作区。
  2. 连接 所需的 凭据。它们会被私密存储,绝不会在公开页面上展示。
  3. 为需要使用其工具的对话启用该服务。

Web executable,通过 Streamable HTTP。 远程服务在工作区中配置后即可从网页运行时运行。

交给智能体安装

把这段提示词粘贴到 Claude Code、Codex、Cursor 等智能体,或 SourceWeft 对话中。智能体会读取该服务器的安装指南,先向你展示发布者、端点和登录方式,经你同意后再把它添加到你的客户端。密钥不会写进任何命令。

阅读 https://sourceweft.com/mcp/io.github.maaakso%2Fcontexter/install.md,并按其中说明把这个 MCP 服务器接入我的客户端。修改任何配置之前,先告诉我它的发布者、端点和登录方式,等我确认。不要把 API 密钥写进命令或我会提交的文件;问我密钥应从哪里获取。

查看智能体所依据的安装指南

其他 MCP 客户端

把它添加到你客户端的 mcpServers 配置中。 客户端会在首次连接时完成 OAuth 登录。

{
  "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.

来源:README.md,提交 4324aea

工具

0
该服务器需要登录,因此 SourceWeft 无法在没有账号的情况下读取其工具,也未收录。已连接账号所能看到的内容可能因账号及其权限而异。

版本历史

1
  1. v1.0.0最新Sep 16, 2026

评分

已满足适用检查项的 75%

该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。

  • 近 30 天内可连通必需25 分
  • 已声明认证方式必需10 分
  • 已列出工具15 分

    请让服务器在无凭据时响应 tools/list,或发布可在沙箱中无凭据启动的软件包。

  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分

    请在仓库或注册中心条目中声明许可证。