TeamShared

MCP文档知识

提供方 未标注

文档知识 未标注 未标注 社区 / 第三方 Claude DesktopClaudeCursorVS Code

编码代理的共享内存。无需在每次会话中重新解释你的代码库。托管MCP位于https://teamshared.com/mcp,支持邮箱/OTP连接。

一句话选型结论

按资料字段整理

TeamShared 属于文档知识类 MCP 服务器,传输方式未标注,鉴权方式未标注,可直接接入 Claude Desktop、Claude、Cursor 等,没有现成安装命令,需按官方文档接入。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类文档知识 传输方式未标注 鉴权未标注 部署方式未标注
GitHub 星标 未标注 仓库热度,无公开仓库时显示未标注
工具数 未标注 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

文档知识
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量未标注暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

支持客户端

适用场景

记忆

安装与配置

未标注 未标注
上游未给出传输方式
  1. 1
    准备运行环境

    按官方文档确认运行环境(常见为 Node.js 或 Python),装好后再执行安装命令。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后随便调一个只读工具,确认能返回结果,再接入正式流程。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
文档检索问答

在你的文档库里按问题找答案。

知识库读写

把新资料写进知识库,随用随取。

内容整理

把零散资料归纳成结构化笔记。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 已适配 Claude Desktop、Claude、Cursor,换客户端不用重新研究配置。

先想清楚的地方

  • 没有现成安装命令,需要按官方文档自己填启动命令和参数。
  • 资料没标注工具数量,实际能力要装好后确认。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在文档知识场景里让模型直接调用外部能力的人。
  • 已经在用 Claude Desktop、Claude 的用户,接入路径最短。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
TeamShared当前 未标注 未标注 未标注 无 未标注
dify 未标注 stdio · 本地进程 本地部署 有 2026-04-11
open-webui 未标注 stdio · 本地进程 本地部署 有 2026-04-11
JeecgBoot 未标注 stdio · 本地进程 本地部署 有 2026-04-11
Cherry Studio 未标注 未标注 未标注 无 2026-05-17
mempalace 未标注 stdio · 本地进程 本地部署 有 2026-04-11

服务器档案

文档知识
字段来自项目仓库与公开索引,中文说明由本站标注
提供方未标注上游标注的维护方 未标注
分类文档知识本站按上游分类展示
连接方式未标注上游未给出传输方式
鉴权方式未标注远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时未标注 · 未标注本地安装时用到的包标识与运行时
部署类型未标注上游给出的部署形态
最近核验未标注上游最后核验时间

详细介绍

13.3 KB
来自项目仓库与上游目录的原文,未做删改

teamshared (Cursor, Claude Code, and Codex plugins)

Registers the teamshared MCP server. The Cursor plugin also ships the
recall-first memory rule and Cursor hooks that capture Agent Chat into
TeamShared (sessionStart, beforeSubmitPrompt, afterAgentResponse,
stop, sessionEnd) plus postToolUse (failed test/lint/shell),
postToolUseFailure (read-only recall), and preCompact. The Cursor
plugin still has no skills, slash commands, or extra agents.

This repo also ships a Claude Code marketplace plugin under claude/
(remote MCP via Claude Code's native /mcp OAuth, TEAMSHARED_TOKEN for the
optional capture hooks, protocol 1.31.0, SessionStart injection, and official
Claude Code capture hooks).

The native Codex package under plugins/teamshared/ uses the server's MCP
OAuth discovery flow and treats Codex as a first-class client: protocol 1.31.0,
SessionStart injection, and official Codex capture hooks. A manual Codex TOML
setup remains available under install/codex/ (TEAMSHARED_TOKEN; do not mix).

Hosted install is teamshared.com/#connect.
The public plugin / marketplace source is this repo
(teamshared-ai/teamshared-plugin).
The remote MCP endpoint is https://teamshared.com/mcp.

One Connect, one org per repo. Install the plugin once and connect once.
From chat, call org_list / org_bind(slug=...). CLI
teamshared org bind is an optional fallback that writes
.teamshared/org. Do not add a second TeamShared server. Unbound /mcp
keeps working — it stays on the org chosen at Connect time. Agent-facing
copy: AGENTS.md.

Component Purpose
mcp.json Registers https://teamshared.com/mcp (URL only; Cursor OAuth Connect)
rules/teamshared.mdc Lean always-on fetch/store loop (alwaysApply); tool encyclopedia lives in memory_tools_catalog
hooks/ Cursor hooks: Agent Chat capture plus postToolUse (failed test/lint/shell), postToolUseFailure (read-only recall), and preCompact
claude/ Claude Code plugin (remote MCP via native /mcp OAuth + protocol 1.31.0 + capture hooks needing TEAMSHARED_TOKEN)
.claude-plugin/marketplace.json Claude Code marketplace catalog (/plugin marketplace add teamshared-ai/teamshared-plugin)
.agents/plugins/marketplace.json Codex marketplace catalog (codex plugin marketplace add teamshared-ai/teamshared-plugin)
plugins/teamshared/ Native Codex plugin (OAuth MCP + protocol 1.31.0 + official capture hooks)
clients/ Copy-paste protocol + MCP examples for non-Cursor harnesses (not loaded by Cursor)

Install

From git marketplace (recommended)

  1. Settings → Plugins → Add marketplace → paste https://github.com/teamshared-ai/teamshared-plugin
  2. Run /add-plugin teamshared or enable teamshared under Settings → Plugins
  3. Settings → Tools & MCP → teamshared → Connect (email + one-time code, same as the console)

Cloud and Grok Bot agents inherit that account-level Connect. Installing the
plugin registers https://teamshared.com/mcp — you only click Connect.
Do not paste a URL or token into the plugin mcp.json. Then bind the repo
(teamshared org bind); do not add a second TeamShared server.

See MARKETPLACE.md for the official Marketplace publish checklist.

Claude Code (marketplace)```

/plugin marketplace add teamshared-ai/teamshared-plugin
/plugin install teamshared@teamshared
/reload-plugins
/mcp


In `/mcp`, select **teamshared** and choose **Authenticate** — Claude Code's
own native OAuth flow, same email/OTP login as the web console, token stored
in your system keychain. Confirm tools appear under `/mcp` as
`plugin:teamshared:teamshared` connected.

The chat-capture hooks are a separate subprocess with no access to that
keychain, so if you also want them capturing chat automatically, mint a
`tsk_` org key and export it — never commit it:```bash
export TEAMSHARED_TOKEN=tsk_...   # mint under https://teamshared.com/app/keys

Without it the hooks just no-op; the MCP connection and every-turn workflow
work fine either way. From chat, call org_bind(slug=...) (CLI
teamshared org bind is optional) so capture follows the org; do
not add a project .mcp.json TeamShared server.
Unbound /mcp keeps working. SessionStart injects protocol 1.31.0;
/teamshared:status checks health + version. Details:
claude/README.md.

Codex (native plugin marketplace)

The native Codex package uses TeamShared's MCP OAuth discovery flow, so it does
not require TEAMSHARED_TOKEN or store an authorization header. The first
browser open is the Codex host (system default browser). TeamShared only
serves /oauth/authorize and the redirect; the post-OTP finish page uses a
single handoff. ChatGPT’s in-app @Browser is Computer Use, not MCP
Authenticate — there is no API to force Connect there. To skip the browser,
use install/codex/ + TEAMSHARED_TOKEN instead
of this plugin. Details:

46 and

plugins/teamshared/README.md.```bash
codex plugin marketplace add teamshared-ai/teamshared-plugin
codex plugin add teamshared@teamshared


Restart the Codex app, start a new task, and connect TeamShared when prompted.
Then review and trust plugin hooks with `/hooks` so capture writes run.
From chat, call `org_bind(slug=...)` (CLI `teamshared org bind ` is
optional); do not add a second `[mcp_servers.teamshared]` next to the
plugin. Unbound `/mcp` keeps working.
`SessionStart` injects protocol 1.31.0; `$status` checks health + version.
The package lives under `plugins/teamshared/` and is
cataloged by `.agents/plugins/marketplace.json`.
Details: `plugins/teamshared/README.md`.

### cursor.directory listing

Submit **this** repo at cursor.directory/plugins/new:```
https://github.com/teamshared-ai/teamshared-plugin

Do not submit the old xhad/teamshared-cursor redirect. Root plugin.json and
.mcp.json are the Open Plugins / directory discovery files; Cursor install
still uses .cursor-plugin/ and mcp.json.

Ready-to-paste listing description:```
TeamShared is hosted MCP plus the recall-first memory rule and Cursor
hooks that capture Agent Chat (plus failed test/lint/shell + preCompact).
No skills, slash commands, or extra agents.

Install in Cursor:
1. Settings → Plugins → Add marketplace
2. Paste https://github.com/teamshared-ai/teamshared-plugin
3. /add-plugin teamshared
4. Settings → Tools & MCP → teamshared → Connect (email + one-time code)

Cloud and Grok Bot agents inherit that Connect.
Bind each repo with teamshared org bind; do not add a second server.


### From this repo (folder or symlink)

**Add plugins from folder** needs a marketplace catalog in the selected
directory. Select **this repo root** (it ships `.cursor-plugin/marketplace.json`
with `"source": "./"`).

Then enable the plugin, reload the window, and **Connect**.

For local iteration without the folder picker:```bash
ln -sf "$(pwd)" ~/.cursor/plugins/local/teamshared

Setup

  1. Connect with email/OTP — Settings → Tools & MCP → teamshared → Connect.
    Cursor opens a browser; sign in with the same email + one-time code as the
    web console (/app). The plugin already shipped the server URL; do not add
    headers or a tsk_* token to the plugin mcp.json.
  2. Bind the repo — teamshared org bind writes .teamshared/org
    ({"v":1,"slug"}). Commit that file. Capture follows it. Do not add a
    second TeamShared server in .cursor/mcp.json, project .mcp.json, or
    Codex config.toml.
  3. Cursor Cloud / Grok Bot — they inherit that account-level Cursor
    Connect. After the one-time Connect, every cloud agent for that user gets
    TeamShared. Bind still lives in the checkout (.teamshared/org); Cloud
    does not take a second MCP URL from repo config. Unbound /mcp keeps
    working (Connect-time org).
  4. Developer: Reload Window — confirm Settings → MCP shows teamshared enabled.

If you previously added https://teamshared.com/mcp by hand, remove that
manual entry so you do not get two teamshared servers.

Bots that must stay in one org use a seat key — teamshared token mint
scoped to that org, or mint under /app/keys — on the MCP headers
(Authorization: Bearer tsk_…). Not in the plugin mcp.json. Unbound
/mcp keeps working for interactive Connect.

What you get

  • MCP tools: memory_recall, memory_remember, memory_session_*, etc.
    (registered by mcp.json when the plugin is installed).
  • Rule: injects the recall-first protocol on every agent turn, and points
    teammates to the web console (/app) for human actions.
  • Cursor hooks: Agent Chat turns are appended to TeamShared in
    near-real-time without waiting for the agent to call
    memory_session_ensure / context_commit. sessionStart maps
    conversation_id onto a working session and, after a successful
    ensure with auto_recall=true, injects a capped Cursor
    additional_context block (linked soul, a short playbook header when
    present, and compact auto_recall bullets — not full memory bodies
    or transcripts). Explicit memory_recall remains preferred for
    keyword work. Fail-open on MCP/auth errors. beforeSubmitPrompt and
    afterAgentResponse append redacted user/assistant text; sessionEnd
    closes and distills. stop only notes aborted/error loops (it fires
    after every turn, so it does not distill). postToolUse still appends a
    short episodic fact when a Shell test/lint/command fails (command +
    error tail, secrets stripped). On Cursor postToolUseFailure and on
    that failed postToolUse, hooks also call remote memory_recall with
    a tight query (tool name + truncated error, k=3, verbose=false) and
    inject compact hits as additional_context — same pattern as
    SessionStart auto_recall. Skip when recall is empty or MCP has no token.
    That recall path never writes (context_commit). Fail-open if MCP is
    unreachable. preCompact writes a short session summary. All reuse the
    existing Connect session — no tsk_ in mcp.json. Cloud agents may skip
    sessionStart / sessionEnd; prompt/response hooks still capture turns.
    Agents still recall first and may commit curated facts; hooks store the
    transcript.

Bind a repo to an org

One TeamShared server stays on https://teamshared.com/mcp. The repo file
chooses the org; capture follows it. Do not add a second TeamShared server.```bash
teamshared org bind sapien --token "$TEAMSHARED_TOKEN"
teamshared org status
teamshared org unbind


`bind` checks membership, then writes only `.teamshared/org`:```json
{"v":1,"slug":"sapien"}

The derived URL https://teamshared.com/o/{slug}/mcp is never stored. Commit
the file so every harness in the checkout sees the same org. status and
unbind work offline. Missing or invalid file → unbound /mcp (Connect-time
org). That is supported; binding is not required.

Harness Connect once Bind Do not
Cursor Settings → Tools & MCP → teamshared → Connect .teamshared/org; hooks POST to the org URL with the same Connect token .cursor/mcp.json / project MCP twin
Cursor Cloud Inherited account Connect Same checkout file; hooks follow it Repo MCP URL as a Cloud bind path
Claude Code /mcp → Authenticate Same file; hooks use an org-scoped TEAMSHARED_TOKEN Project .mcp.json TeamShared server
Codex Plugin OAuth (or manual tsk_ — not both) Same file [mcp_servers.teamshared] next to the plugin

Bots that must stay in one org: teamshared token mint (org-scoped
seat key) or /app/keys. Still one server.

The Cursor plugin still has no skills, slash commands, or extra agents.
The Claude Code package ships protocol 1.31.0 (teamshared-memory),
/teamshared:status, and official Claude Code capture hooks. The Codex
package ships the same 1.31.0 loop plus official Codex hooks (SessionStart,
UserPromptSubmit, Stop, Interrupt, SessionEnd, PostToolUse on failed
Bash, PreCompact). SessionEnd closes through one bounded commit;
Interrupt covers Cursor abort parity. Codex has no StopFailure or
PostToolUseFailure.

Other clients

See clients/ for Hermes, Claude Desktop, and protocol markdown.
Claude Code and Codex should use their marketplace plugins above unless you are
debugging a manual client configuration.

Codex (manual TOML alternative)

For manual MCP registration without the native plugin, Codex uses TOML rather
than Cursor's JSON mcp.json. Mint a tsk_ key at
teamshared.com/app/keys, export it, then
register the hosted MCP (Codex sends Authorization: Bearer tsk_…):bash export TEAMSHARED_TOKEN=tsk_... # from /app/keys — never commit this codex mcp add teamshared \ --url https://teamshared.com/mcp \ --bearer-token-env-var TEAMSHARED_TOKEN

Or merge install/codex/mcp.toml into project-local
.codex/config.toml and run Codex from that trusted repo root. Full steps:
install/codex/README.md.

Use either the native marketplace plugin or the manual TOML entry, not both.
The manual path is the seat-key path for bots that must stay in one org
(teamshared token mint scoped to that org) and the reliable way to skip
the OAuth browser
. Do not add a second TeamShared server next to the
plugin. Bind the checkout with teamshared org bind either way;
unbound /mcp keeps working.

Cursor desktop, Cursor Cloud, and Grok Bot still use Connect — do not add
this tsk_ block to the plugin mcp.json.

License

MIT — see LICENSE.

常见问题

6 问
答案由本站依据条目字段整理,不引用上游原文
TeamShared 怎么安装?

资料没有给出安装命令,请到官方仓库或文档按说明接入;这类条目多数是生态应用,或尚未发布可安装包。

TeamShared 怎么在 Claude Desktop、Claude、Cursor 里配置?

它的传输方式未标注,在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,配置才会生效。

TeamShared 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

TeamShared 需要 API Key 吗?

资料没有标注鉴权方式,是否需要密钥取决于服务本身,接入前按官方文档确认。

TeamShared 支持哪些客户端?

资料标注支持 Claude Desktop、Claude、Cursor、VS Code、Codex、Zed;其他客户端只要能配置 MCP Server,也能用同样的命令或地址接入。

TeamShared 能提供哪些能力?

资料显示能力标签包括 记忆。具体工具清单以官方文档为准。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 未标注。