Export as a Claude Code plugin

Package your hosted MCP server as an installable Claude Code plugin and download it as a .zip to import into Claude. A plugin bundles the connection to your server (and any skills and prompts you've authored) into a single artifact your users — or your team — can install in one step.

Beta. The generated layout may still evolve.

Plugin export is a paid feature — it's available on the Team plan and above. On the free Starter plan the Plugins page is hidden; upgrade to enable it.

Find it under Distribute → Plugins for any app (on an eligible plan).

What you get

The download is a self-contained, single-plugin marketplace folder:

<server-slug>/
├── .claude-plugin/
│   ├── plugin.json        name, description, version (+ a token prompt if needed)
│   └── marketplace.json   one-plugin marketplace so the folder installs as-is
├── .mcp.json              connection to your hosted MCP server (type: http)
├── skills/<slug>/SKILL.md  your enabled skills (+ their reference files)
├── commands/<slug>.md      slash commands generated from your enabled prompts
└── README.md               install instructions

Your tools, widgets, and resources are not copied into the plugin — they are served live over the MCP connection when Claude connects, so they always reflect the current server configuration.

Requirements

• A Team plan or higher. Plugin export is gated behind the plugin_export feature; Starter workspaces can't export.

• A published server. A development branch can't be exported as a plugin because it has no public endpoint — deploy it first.

How authentication is handled

The plugin connects to your live production endpoint, so it authenticates exactly the way your server does. No secrets are ever written into the plugin.

Server auth mode	In the plugin
User OAuth	Claude Code prompts each user to sign in on first use. Nothing is stored in the plugin.
Bearer token	Each user enters the token at install time (stored in their OS keychain) and it's sent as an Authorization header.
API key	Each user enters the key at install time; it's sent in the header or query parameter your server expects.
None	The plugin connects directly with no credential.

Export and install

1. Open Distribute → Plugins, confirm the auth note matches your server, and click Download plugin (.zip).

2. Unzip it. In Claude Code, add the folder as a marketplace and install the plugin:

   /plugin marketplace add /absolute/path/to/<server-slug>
   /plugin install <server-slug>@<server-slug>

   Alternatively, commit the folder to a git repository and run /plugin marketplace add <owner>/<repo> followed by the same install command — handy for sharing with a team.

3. Your server's tools appear in Claude. Skills and prompts you authored show up as plugin skills and slash commands.

Related

• Integrate with AI clients — connect Claude, Cursor, VS Code and others by URL or config.

• Export & self-host your MCP server — run the server itself on your own infrastructure.

• Publish to Claude — list your server in the Claude Connectors Directory.