VenomDocs

Cursor

Add the Venom MCP server and rule to Cursor, authorize your organization, and check the connection.

Venom makes Cursor multiplayer. Your teammates’ agents and yours share tasks, decisions, skills, and tools, whichever agent each person uses.

What you get in Cursor.

Cursor connects to Venom’s remote MCP server and loads a short Venom rule in Agent conversations. The rule tells the agent to read the project and task before acting and to log what changed. Your organization’s own practices live in shared skills. This setup doesn’t configure inline completion or Bugbot.

Install.

Two files, both merged into what you already have.

  1. Merge this into .cursor/mcp.json in your project, or ~/.cursor/mcp.json. Keep your other servers.
{
  "mcpServers": {
    "venom": {
      "url": "https://mcp.venomlabs.dev/"
    }
  }
}
  1. Copy platforms/cursor/venom.md from the plugin repository into your project’s .cursor/rules/ and rename it venom.mdc. The file sets alwaysApply: true.

Sign in.

Start a new Agent conversation and authorize Venom when Cursor prompts. Select your organization. Cursor manages the sign-in and tool approvals.

Check the connection.

Ask your agent:

Use Venom to list the projects I work on. If there are none, tell me.

An empty list is valid in a new organization. Follow the Quickstart to create a project and save a first result.

What guides Cursor.

Venom Full’s hooks don’t cover Cursor. The agent gets the always-applied rule and a one-line reminder at the top of every Venom tool response. A turn that never calls Venom gets no tool-response reminder. The rule and reminders ask; the agent makes the tool calls.

Next.

Codex

Install Venom and Venom Full in Codex, authorize your organization, and check the connection.

Gemini CLI

Install the Venom extension in Gemini CLI, authorize your organization, and check the connection.

On this page

What you get in Cursor.Install.Sign in.Check the connection.What guides Cursor.Next.