English Français العربية

Plug and Ship

Official registry Developer tools

Search MCP servers, agent skills and coding-agent plugins: trending tools and best-of lists.

Source code Website Documentation

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

Remote (streamable-http)
Claude Code 
claude mcp add --transport http plug-and-ship 'https://plugandship.dev/mcp'
JSON configuration (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "plug-and-ship": {
            "type": "http",
            "url": "https://plugandship.dev/mcp"
        }
    }
}

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. plugandship-mcp
  2. Tools
  3. Use the hosted endpoint (no install)
  4. Run it locally (stdio)
  5. Self-host Streamable HTTP
  6. Configuration
  7. Test
  8. Registry
  9. License

plugandship-mcp

An MCP server for Plug and Ship. It lets your coding agent search the Plug and Ship index of MCP servers, agent skills and coding-agent plugins without leaving the chat.

It is read-only. It calls the public Plug and Ship API (/api/v1) and needs no API key.

Listed in the official MCP Registry as dev.plugandship/plugandship-mcp.

Tools

ToolArgumentsWhat it returns
search_toolsquery or task (keywords or a plain-language task, e.g. "query my Postgres from Cursor"), type? (mcp / skill / plugin), client? (claude-code / cursor / codex / grok-bot), remote? (only MCP servers with a public HTTPS endpoint), limit? (1 to 50, default 10)Tools ranked by relevance (full-text + semantic match; stars, recent commits, a valid one-click config and a license only break ties), each with a one-line reason it matches, install command and page link. Also returns structured output, including what was understood from the task. client: "grok-bot" keeps only MCP servers with a public remote (HTTP) endpoint.
get_toolslugFull details for one tool: description, repo, stars, tags, install command, remote endpoint if any.
trendingperiod (day / week / month), type?, limit?Fastest-growing tools: stars gained in the period, from Plug and Ship's own daily star snapshots.
list_besttopic?, limit?A curated "best of" list. Leave topic empty to list topics (for example grok-bot-connectors, voice-agents, postgres-mcp-servers).

Use the hosted endpoint (no install)

Remote MCP server, Streamable HTTP, stateless, no auth:

https://plugandship.dev/mcp

Claude Code

claude mcp add --transport http plugandship https://plugandship.dev/mcp

Cursor (~/.cursor/mcp.json or .cursor/mcp.json in a project)

{
  "mcpServers": {
    "plugandship": { "url": "https://plugandship.dev/mcp" }
  }
}

Codex (~/.codex/config.toml)

[mcp_servers.plugandship]
url = "https://plugandship.dev/mcp"

Run it locally (stdio)

Requires Node.js 18 or newer. Runs straight from GitHub, no npm package needed (the built dist/ is committed):

npx -y github:plugandship/plugandship-mcp

Claude Code

claude mcp add plugandship -- npx -y github:plugandship/plugandship-mcp

Cursor

{
  "mcpServers": {
    "plugandship": {
      "command": "npx",
      "args": ["-y", "github:plugandship/plugandship-mcp"]
    }
  }
}

Codex

[mcp_servers.plugandship]
command = "npx"
args = ["-y", "github:plugandship/plugandship-mcp"]
From a checkout
git clone https://github.com/plugandship/plugandship-mcp
cd plugandship-mcp
npm install
npm run build
node dist/index.js

Self-host Streamable HTTP

node dist/index.js --http --port 3333 --host 127.0.0.1
# endpoint: http://127.0.0.1:3333/mcp

Stateless, JSON responses, POST only. Requests with a browser Origin other than localhost are rejected. It binds to 127.0.0.1 by default. Put it behind HTTPS before exposing it anywhere.

Configuration

Env varDefaultPurpose
PLUGANDSHIP_API_URLhttps://plugandship.devAPI base URL (use http://localhost:3000 against a local site).

The public API is cached and rate-limited (about 60 requests per minute per IP). On a 429 the tool returns a short "try again in a minute" error.

Test

npm test                                            # stdio + local HTTP, against https://plugandship.dev
PLUGANDSHIP_API_URL=http://localhost:3000 npm test  # against a local site
MCP_REMOTE_URL=https://plugandship.dev/mcp npm run test:remote  # the hosted endpoint

npm test builds the server, starts it over stdio and over Streamable HTTP, connects with the official MCP SDK client, lists the tools and calls each one, including error cases (unknown slug, invalid input, foreign Origin). test:remote runs the same checks against a remote endpoint.

Registry

server.json is the MCP Registry entry: a remote-only listing (streamable-http, https://plugandship.dev/mcp) under the dev.plugandship namespace, verified by DNS.

License

MIT

Frequently asked questions

What is Plug and Ship?

Search MCP servers, agent skills and coding-agent plugins: trending tools and best-of lists.

How do I install Plug and Ship?

It runs as a remote server. In Claude Code: claude mcp add --transport http plug-and-ship 'https://plugandship.dev/mcp'. For other clients, paste the JSON configuration from this page into their MCP settings.

Does Plug and Ship need an API key?

Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.

Is Plug and Ship open source?

Yes. Its code is on GitHub under the MIT license.

Who maintains Plug and Ship?

It is published by plugandship. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.