Venom

io.github.venomlabs-devPublished by GitHub account venomlabs-devv1.0.0Updated Nov 14, 2026

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

VerifiedStreamable HTTPWeb executableProductivity & WorkflowKnowledge & MemoryDeveloper Tools

Overview

AI-generated overview

Remote MCP server that makes a team's coding agents share projects, tasks, decisions and skills across Claude Code, Codex, Cursor and other clients.

What you can do
  • Read and update the team's Venom workspace: projects, tasks and decisions
  • Share skills and tools so another agent or teammate can continue the work
  • Keep the current task up to date through guidance the server returns to the agent
  • Connect the same workspace from several MCP hosts with one organization-scoped sign-in
When to use it
Useful when several people or agents work on the same codebase and you want handoffs, decisions and task state to persist between sessions and across different coding agents, without adopting a new harness.
Requirements
A remote endpoint at mcp.venomlabs.dev; no local package or runtime. A Venom account and OAuth authorization in each host, with connections scoped to your organization. Host-specific setup: a plugin install for Claude and Codex, an extension folder for Gemini CLI, or merged MCP config plus an instruction file for Cursor, Kiro, OpenCode, Copilot, Cline, Windsurf and Devin. Sign-in expires after 30 days without use.
Before you install
Requires OAuth sign-in and sends data to Venom's servers, limited to your organization's workspace through the tools the agent calls. Agents can write and change shared tasks and decisions, so review tool approvals in the host. The optional venom-full variant adds hooks that call the server's get_guidance tool on prompts, compaction and git/gh events; it must be trusted in the host. Unattended cloud agents need a separate authentication path.

Installation

In SourceWeft

  1. Open Venom 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.venomlabs-dev%2Fvenom/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": {
    "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.

Source: README.md at commit 8c7a3b0

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.0LatestNov 14, 2026

Score

85% 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