Venom

io.github.venomlabs-dev由 GitHub 账号 venomlabs-dev 发布v1.0.0更新于 Nov 14, 2026

Multiplayer for the coding agents your team already uses: shared tasks, decisions, skills and tools.

已验证Streamable HTTP可网页运行效率与工作流知识与记忆开发者工具

概览

AI 生成的概览

远程 MCP 服务器，让团队的编码智能体在 Claude Code、Codex、Cursor 等客户端之间共享项目、任务、决策与技能。

可以做什么
  • 读取并更新团队的 Venom 工作区：项目、任务与决策
  • 共享技能与工具，让其他智能体或同事接着完成工作
  • 通过服务器返回的指引让当前任务保持最新
  • 在多个 MCP 宿主中以同一组织范围的登录连接同一工作区
适用场景
适合多人或多个智能体协作同一代码库、希望交接内容、决策和任务状态能跨会话、跨不同编码智能体保留，又不想更换现有工具链的场景。
运行要求
远程端点 mcp.venomlabs.dev，无需本地包或运行时。需要 Venom 账号，并在每个宿主中完成 OAuth 授权，连接限定在所属组织。各宿主配置不同：Claude 与 Codex 通过插件安装，Gemini CLI 使用扩展目录，Cursor、Kiro、OpenCode、Copilot、Cline、Windsurf、Devin 需合并 MCP 配置并添加说明文件。30 天未使用需重新登录。
安装前请注意
需要 OAuth 登录，数据会发送到 Venom 服务器，仅通过智能体调用的工具写入所属组织工作区。智能体可写入和修改共享任务与决策，请在宿主中留意工具审批。可选的 venom-full 变体会添加钩子，在提示、上下文压缩以及 git/gh 事件时调用服务器的 get_guidance 工具，需在宿主中信任。无人值守的云端智能体需要单独的支持认证方式。

安装

在 SourceWeft 中

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

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

交给智能体安装

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

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

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

其他 MCP 客户端

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

{
  "mcpServers": {
    "venom": {
      "type": "http",
      "url": "https://mcp.venomlabs.dev/"
    }
  }
}

README

Venom MCP plugin

Venom AI by Venom Labs makes the coding agents your team already uses multiplayer. One MCP server connects Claude Code, Codex, Cursor, Gemini CLI and other MCP clients, so your team's agents share tasks, decisions, skills and tools. There is no new harness to adopt.

Website · How it works · Quickstart · MCP setup · Pricing

Venom is where your team's AI agents share their work: projects, tasks, decisions and skills, so any agent or teammate can pick up where another left off. Agents reach it through the host-managed MCP connection at https://mcp.venomlabs.dev.

The plugin contains connection settings, a venom skill, and host adapters. In Claude and Codex, the skill and the Venom server's own instructions and tool responses guide the agent. Other hosts use the short VENOM.md guidance as a rules file. Connections remain authenticated and organization-scoped; the host manages OAuth and tool approval. Installing this plugin does not disable those controls.

What this plugin does

Venom connects Claude to your team's Venom workspace through one remote MCP server, https://mcp.venomlabs.dev, which you sign in to with your Venom account. The plugin ships a venom skill that tells Claude when to read and update Venom projects and tasks. It registers no hooks and runs no code on your machine. Claude sends data to Venom only through the Venom tools it calls, and only to your organization's workspace.

Claude (chat, Cowork and Claude Code)

Add Venom from the plugin directory on claude.ai, or in Claude Code:

text
/plugin marketplace add venomlabs-dev/plugin/plugin install venom@venom

Authorize Venom when prompted. In chat and Cowork, connect Venom on the plugin's Connectors tab. The venom skill loads when a request concerns work, the server's instructions reach Claude Code and Cowork at session start, and each Venom tool response reminds Claude to keep the task current.

Codex

bash
codex plugin marketplace add venomlabs-dev/plugincodex plugin add venom@venom

Start a new task and authorize Venom. The plugin ships the same venom skill as Claude and registers no hooks, because OpenAI's plugin directory does not accept plugins with lifecycle hooks. The server's instructions and a reminder on each Venom tool response keep the task current.

Venom Full (for developers)

venom-full adds hooks to venom. Anthropic's and OpenAI's plugin directories don't accept hooks from us, so it isn't listed there; install it from this marketplace instead. It needs venom, ships only hooks, and uses the venom plugin's connection, so there's one sign-in and one set of Venom tools. Its files live in venomlabs-dev/venom-full; the marketplace fetches them for you.

Claude Code installs venom with it:

text
/plugin marketplace add venomlabs-dev/plugin/plugin install venom-full@venom

Codex needs both plugins and lifecycle hooks turned on:

bash
codex plugin marketplace add venomlabs-dev/plugincodex plugin add venom@venomcodex plugin add venom-full@venom

Then trust the Venom hooks once in /hooks.

The hooks are mcp_tool hooks that call the Venom server's get_guidance tool after compaction, before compaction (Claude Code), when a subagent starts, on each prompt, and after git commit, git push, gh pr create and gh pr merge. No local program runs. While the hooks are active, the server stops adding reminder lines to Venom tool responses.

Gemini CLI

Install the extension folder from a clone of this repository:

bash
git clone https://github.com/venomlabs-dev/plugin venom-plugingemini extensions install ./venom-plugin/platforms/gemini

Restart Gemini and authorize Venom. The extension loads its VENOM.md as a context file in every session. To update, pull this repository and run gemini extensions update venom. Do not install the repository root as a Gemini extension.

Other hosts

Merge MCP entries into existing configuration; never overwrite other servers. Add the small instruction file alongside existing rules.

HostMCP configurationInstruction installation
CursorMerge mcp.json into .cursor/mcp.json or ~/.cursor/mcp.jsonCopy venom.md into the project's .cursor/rules/ and rename it venom.mdc
Kiro IDE / CLIMerge mcp.json into .kiro/settings/mcp.jsonCopy venom.md into .kiro/steering/; custom agents must include this resource
OpenCodeMerge opencode.json into project opencode.jsonCopy root VENOM.md into the project root; preserve it in instructions alongside existing entries
GitHub Copilot CLIMerge mcp-config.json into ~/.copilot/mcp-config.jsonAppend copilot-instructions.md to .github/copilot-instructions.md or ~/.copilot/copilot-instructions.md
VS Code Copilot AgentMerge mcp.json into .vscode/mcp.jsonAppend the same Copilot instructions to .github/copilot-instructions.md
ClineMerge mcp.json through Cline's MCP settings UICopy venom.md into .clinerules/ and enable the rule
Windsurf / Devin Desktop legacy CascadeMerge mcp_config.json into ~/.codeium/windsurf/mcp_config.jsonCopy venom.md into .windsurf/rules/
Devin CLI / Desktop LocalMerge mcp_config.json into .devin/mcp_config.jsonAppend root VENOM.md to the project's AGENTS.md

Authorize each connection in its host. Use current supported host releases. The coverage notes describe sources, lifecycle limits, and verification. These are local/IDE adapters; unattended cloud agents need a separately supported authentication path.

Troubleshooting

If your agent says Venom isn't connected, or never uses Venom, sign in again: run /mcp and authenticate venom in Claude Code, run codex mcp login venom for Codex, or reconnect Venom on the plugin's Connectors tab in Claude chat and Cowork. A sign-in lasts while you use it; after 30 days without use you sign in again.

Upgrading to 0.8.1

The Codex manifest now carries the review test cases and release notes for OpenAI's plugin directory. Nothing changes for users.

Upgrading to 0.8.0

The marketplace now also lists venom-full, hooks for developers: see Venom Full. The venom plugin is unchanged.

Upgrading to 0.7.1

The venom skill now tells the agent what to do when Venom isn't connected: say so in one line, with the sign-in step for your app, instead of working without Venom unnoticed.

Upgrading to 0.7.0

The Codex plugin no longer ships hooks, so it can be listed in OpenAI's plugin directory. Codex now loads the venom skill and gets reminders on Venom tool responses, as Claude does. You can remove the old Venom hooks from /hooks.

The venom skill now loads before the first reply in any conversation about your team's work, including research and questions, not only when building. Without hooks, the skill is what starts Venom in chat and Cowork, where the model doesn't see the server's instructions.

Upgrading to 0.6.0

The Claude plugin no longer ships hooks. Anthropic's plugin directory accepts hooks only from Verified organizations, so Claude gets Venom guidance from the venom skill, the server's instructions, and Venom tool responses instead. Codex keeps its hooks, now in .codex-plugin/hooks.json; trust them again via /hooks. Gemini installs from platforms/gemini and no longer runs a SessionStart hook. Refresh manually copied rules files from this release.

Development

The repository holds only Markdown and JSON, as the directory requires for organizations that aren't Verified. Edit VENOM.md, then update the copies under platforms/ to match. The checks for this repository live in the Venom monorepo.

来源：README.md，提交 8c7a3b0

工具

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

版本历史

1
  1. v1.0.0最新Nov 14, 2026

评分

已满足适用检查项的 85%

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

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

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

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