---
title: Marketplace and MCP servers
description: Submit, review and pin plugins, skills and MCP server packages in your org's marketplace, and approve the MCP servers each key group's venom users get.
section: cloud
order: 64
audience: [user, operator]
sources: [services/nodejs-cloud/app/(console)/(shell)/marketplace, services/nodejs-cloud/app/(console)/(shell)/mcp, services/nodejs-cloud/components/marketplace, services/nodejs-cloud/components/mcp, services/nodejs-cloud/lib/marketplace, services/nodejs-cloud/lib/mcp]
features: [cloud.console-marketplace, cloud.console-mcp]
---

Two console pages control what extensions your members' venom may load:

| Page | What it is for | Read | Change |
|---|---|---|---|
| `/marketplace` | the org's catalog: its own listings, its library skills, its key groups' MCP servers and venom's featured plugins and skills | `routing:read` (owner, admin, developer, viewer) | any reader may submit; approving, pinning, deprecating and removing need `org:manage` |
| `/marketplace/submit` | submit a new package or a new version | `routing:read` | |
| `/marketplace/{id}` | one listing: install command, what it asks for, versions, reviews | `routing:read` | `org:manage` |
| `/marketplace/featured/{name}` | one of venom's own plugins or built-in skills | `routing:read` | |
| `/mcp` | the MCP servers a key group's venom users get, carried in the key group's signed policy | `routing:read` | `routing:write` (owner, admin, developer) |

## Publish a plugin to your org {#quick-start}

1. In the plugin's directory, build a bundle with runtime dependencies included:

   ```bash
   npm pack
   ```

2. Open `/marketplace/submit`, choose **Bundle (.tgz)** and pick the file. The name, version and description are
   read from the bundle's manifest.
3. Tick what it asks for (runs code in venom, tools it adds, hosts it contacts, environment variables it reads,
   commands it starts), add a note for the reviewer and submit. It is pending until an admin approves it.
4. An admin opens the listing at `/marketplace/{id}`, checks what the bundle asks for, and approves the version.
5. Members install it:

   ```bash
   venom plugin install org:acme-lint
   venom plugin install org:acme-lint@1.2.0 --yes
   ```

Without a version, venom installs the pinned version, else the newest approved one. The CLI side is described in
[Installing plugins](/docs/plugins/installing.md#org-marketplace).

## Submitting {#submit}

A package can come from three sources:

| Source | Fields |
|---|---|
| Bundle | a `.tgz` of at most 2 MiB (16 MiB unpacked, 1000 files, paths up to 255 characters and 16 levels). Links, unsafe paths and duplicates refuse the bundle |
| npm | package, version and `Integrity` (`npm view <package>@<version> dist.integrity`) |
| git | repository URL and the full commit id (`git rev-parse HEAD`), never a branch or tag |

Other fields: name (what members install as `org:<name>`; lowercase letters, digits, `.`, `_` and `-`, up to 64
characters), a semantic version, title, kind (plugin, skill or MCP server; guessed from the contents when empty),
description, homepage and a note for the reviewer. Submitting the same name again adds a version to the listing. An
org holds at most 200 listings and 50 versions per listing.

`/marketplace/submit?name=<name>` opens the form with the name filled in, for a new version.

## Reviewing a listing {#listing}

`/marketplace/{id}` shows the install command, what the served version asks for, every version with its state
(`pending`, `approved`, `rejected`), who submitted and decided it, and reviews. Admins can:

| Control | Effect |
|---|---|
| Approve / Reject (with a reason) | approving makes the version installable; rejecting an approved version revokes it |
| Download | the version's bundle, to inspect it locally |
| Version members get | **Pinned**: everyone installs exactly that version and others are refused. **Newest**: the newest approved version. A pinned version must be unpinned before it can be rejected |
| Deprecation | a deprecated listing is hidden from the list by default and venom asks before installing it, showing your reason |
| Remove | deletes the listing. Installed copies keep working; `venom plugin update` reports it gone |

Install manifests are signed with the org's policy-signing key (or the cloud's), valid for 15 minutes. Without a
signing key the API answers `503 policy_signing_not_configured`: set one up from `/mcp` (below).

**Rate it**: members leave one review per item (1 to 5 stars and up to 1000 characters) on listings, featured items,
library skills and MCP servers. They can remove their own; admins can remove anyone's.

The `/marketplace` list has search, tabs by kind, **Show deprecated**, the admins' pending queue
(`/marketplace?tab=pending`), your own submissions (`?tab=mine`) and the featured items (`?tab=featured`).

## MCP servers {#mcp}

`/mcp` configures one key group at a time (a legacy key group session sees its own; an admin picks one with
`?team=<key group id>`). A key group holds API keys, daemons, policies and GPU grants, not people. Approvals
travel in the key group's signed policy; members sign in to OAuth servers on their own machine, and no token or
tool call passes through the cloud.

The page has:

- **Set up signing**, shown while the org has no policy-signing key (owners and admins). It creates the key and shows
  its fingerprint.
- **Connect your machine**: the commands a member runs (`venom cloud login`, then `venom mcp connect`).
- **Approved servers**, each with one control and an optional tools pin (`tools_sha256`, the 64 hex characters
  `venom mcp pin <name>` prints).
- **Catalog**: a curated, searchable table (search, sign-in type, **Approved only**, category), with the same control
  and a link to each vendor's docs.
- **Add custom server**.

| Control | Meaning |
|---|---|
| Off | not approved; members can't enable it |
| Available | approved, off by default; members opt in with `venom mcp enable <name>` |
| Everyone | approved and on for everyone using the key group's keys |

Every change signs a new policy envelope ("Policy #N signed."); members get it the next time venom starts.

### Custom server fields {#custom-server}

| Field | Notes |
|---|---|
| Name | what members type in `venom mcp enable <name>`; letters, digits, `-` and `_` |
| Title, Description | optional |
| Transport | `http`, `sse` or `stdio` |
| URL (http, sse) | `https:`, or `http:` to `localhost`, `127.0.0.1` or `[::1]`; no user name or password in it |
| Sign-in (http, sse) | none or OAuth, with optional scopes (space-separated), client ID (for servers without dynamic client registration) and authorization server metadata URL |
| Command, Arguments (stdio) | runs on each member's machine inside their sandbox; at most 32 arguments, one per line. Pin packages to an exact version |

A key group's policy holds at most 50 servers. Headers and environment variables are refused, so servers that need a
static token are not supported. Changes are audited as `policy.mcp_set`.

## Troubleshooting {#troubleshooting}

| Message | Cause and fix |
|---|---|
| "Only admins (org:manage) can do this." | approving, pinning, deprecating and removing need an owner or admin |
| "Your role cannot change the key group's MCP servers." | needs `routing:write` (owner, admin, developer) |
| "Only an owner or admin can set up signing." | ask an owner or admin to open `/mcp` |
| "No key group to configure yet. Create one under Settings → Tenants & key groups." | create a key group first |
| `503 policy_signing_not_configured` on install | set up signing on `/mcp` |
| The bundle is refused | it is over 2 MiB, has links or unsafe paths, or its runtime dependencies are missing |

## Related {#related}

- [Installing plugins](/docs/plugins/installing.md): `venom plugin install` and the org marketplace from the CLI.
- [MCP servers](/docs/plugins/mcp.md#org): `venom mcp` and your organisation's servers.
- [Team library and starter packs](/docs/cloud/console-library.md): library skills listed in the marketplace.
