Plugin

Install Vruum as a harness plugin where plugin rails exist, and know the fallback path for harnesses that use direct MCP plus skills.

Plugin is the packaging layer. A Vruum plugin can bundle:

the remote MCP server entry for https://api.vruum.ai/mcp;
Vruum workflow skills;
harness metadata such as display name, description, and category;
setup instructions for the harness that understands that plugin format.

The plugin is not the runtime. MCP is still the live tool connection. Skills are still the workflow instructions the agent loads. The plugin just makes installation one step when a harness has plugin rails.

Non-technical clients should use a plugin when their harness offers one, or direct MCP when it does not. They should not need Node or the local CLI for normal Vruum operation.

Harness support

Harness	Plugin status	Use now
Claude Code	Vruum ships Claude plugin metadata in the public skills package.	Install through the Claude plugin/marketplace flow when available. Otherwise use direct MCP and skills setup.
Claude Desktop / Claude.ai	Vruum distributes a plugin zip from the skills release channel.	Download the Vruum plugin zip and add it from the Claude plugin UI.
Codex CLI	Vruum ships Codex plugin metadata with `skills` and `mcpServers` entries.	Use the Codex plugin commands below when the marketplace is available, or use `vruum init`.
Cursor	No Vruum plugin bundle today.	Connect the Vruum MCP server; install shipped skill files manually where supported.
Cline	No Vruum plugin bundle today.	Connect the Vruum MCP server; install shipped skill files manually where supported.
OpenCode	No Vruum plugin bundle today.	Connect MCP; OpenCode can read `.agents/skills` when configured.
Windsurf	No Vruum plugin bundle today.	Connect MCP; install skill files manually only if the harness exposes a skill directory.
Gemini CLI	No Vruum plugin bundle today.	Connect MCP; install shipped skill files manually where supported.
ChatGPT or hosted MCP clients	Use remote MCP, not a local plugin bundle.	Connect `https://api.vruum.ai/mcp` and authenticate in the client.

Codex plugin

The public skills package includes a Codex plugin manifest:

{
  "name": "vruum",
  "skills": "./skills/",
  "mcpServers": "./.mcp.json"
}

When the Codex plugin marketplace is available in your environment:

codex plugin marketplace add vruum-gtm/skills
codex plugin add vruum@vruum-gtm
codex mcp login vruum

If plugin installation is unavailable, use the technical fallback:

vruum login
vruum init
export VRUUM_MCP_TOKEN=<your-vruum-token>
codex

vruum init registers MCP through codex mcp add and installs Vruum skills into ~/.agents/skills.

Claude plugin

The public skills package includes Claude plugin metadata. For Claude Desktop or Claude.ai plugin upload, use the release zip when it is published:

https://github.com/vruum-gtm/skills/releases/latest/download/vruum-plugin.zip

For Claude Code without plugin install, use direct setup:

vruum login
vruum init

vruum init registers MCP through claude mcp add and installs Vruum skills into ~/.claude/skills.

Plugin vs MCP vs skills

Need	Use
One install path for a harness that supports plugins	Plugin
The live Vruum tool connection	MCP
Workflow instructions like outreach triage or pipeline fill	Skills
Local config writing, CI, local files, or debugging	CLI Reference

Give this to an agent

Check whether my harness has a Vruum plugin. If it does, use that.
If not, connect the Vruum MCP server at https://api.vruum.ai/mcp. Then load
Vruum-shipped skills through plugin support, vruum init, or a local skill
directory if this harness supports one. Use the MCP skill tool only for team
skills saved in Vruum.

Quick Start — copyable install prompt to give a harness.
MCP — connect hosted MCP in each harness.
Skills — install, discover, invoke, and publish skills.
CLI Reference — granular command tree and exit codes.

Harness support

Codex plugin

Claude plugin

Plugin vs MCP vs skills

Give this to an agent

Related docs