ManyCP MCP server

Official8 tools

by dayyad

Submit an MCP server to many MCP directories and track each listing from an AI assistant

io.github.dayyad/manycp-mcp (MCP Server)

The io.github.dayyad/manycp-mcp server is described as an MCP server that helps users submit an MCP server to many MCP directories and track each listing from an AI assistant.

🛠️ Key Features

Submit an MCP server to multiple MCP directories
Track each directory listing from an AI assistant

🚀 Use Cases

Publishing an MCP server across several MCP directory services
Monitoring the status or presence of listings after submission

⚡ Developer Benefits

Centralized workflow for directory submissions
Visibility into listing outcomes via an AI assistant

⚠️ Limitations

Only high-level behavior is provided: submission to “many MCP directories” and listing tracking; no additional capabilities, tools, or protocol details are included in the provided data.

Topics

mcpmcp-servermodel-context-protocolremote-mcpgemini-cli-extension

Captured live from the server via tools/list.

list_directories

List every MCP directory ManyCP can file a server in (26 today). For each one you get: its id (pass ids to submit_server), name and URL, how ManyCP files it (Direct publish, Auto PR, Auto-indexed or Assisted), whether it fits local servers, remote servers or both, whether it must wait for another directory, and what ManyCP does step by step. Read-only, takes no input, works on every plan. Use it to answer 'where can I list my MCP server?' or to pick directory ids for submit_server.

Parameters

No parameters.

Raw schema

{
  "type": "object",
  "properties": {},
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}

list_servers

List the MCP servers on this ManyCP account. Each comes with its id and slug (every other tool takes either one as `server`), its repo and version, and a one-line status across the directories that fit it, for example '3 live, 1 PR open, 16 not started'. Read-only, works on every plan. Call this first when the user says 'my server' and you do not know which one they mean. Use get_server for the detail of one.

Parameters

No parameters.

Raw schema

{
  "type": "object",
  "properties": {},
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}

add_server

Add an MCP server to ManyCP from its public GitHub repo. ManyCP reads the repo (README, package.json or pyproject.toml, server.json, Dockerfile), finds npm, PyPI, Docker and remote endpoints, writes a draft listing (title, short description, categories, tags, tools, install config), saves it, and returns the listing, any warnings, and the plan for every directory that fits. It does not submit anywhere: review the listing, fix it with update_listing, then call submit_server. Adding a repo that is already added is an error that names the existing server. Needs a launch credit ($19 per server, once), Starter (3 servers) or Pro (unlimited).

Parameters1

repo_url

string

required

The public GitHub repo: https://github.com/owner/name, or just owner/name.

Raw schema

{
  "type": "object",
  "properties": {
    "repo_url": {
      "type": "string",
      "minLength": 3,
      "maxLength": 300,
      "description": "The public GitHub repo: https://github.com/owner/name, or just owner/name."
    }
  },
  "required": [
    "repo_url"
  ],
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}

get_server

Get one server's full listing and its status in every directory that fits it. Status is one of: live (ManyCP confirmed the listing exists), pr_open (a pull request is waiting on maintainers), submitted (sent, waiting), in_progress, queued, needs_update (the listing is behind the latest version), action_required (the user must do something, the reason is included), rejected, skipped, or not_started. Also returns links: pull requests, live listing pages, the dashboard page. Read-only, works on every plan. `server` accepts an id, a slug, a GitHub repo, or the exact name.

Parameters1

server

string

required

Which server: its id (srv_...), its slug, its GitHub repo (https://github.com/owner/name or owner/name), or its exact name. list_servers shows them all.

Raw schema

{
  "type": "object",
  "properties": {
    "server": {
      "type": "string",
      "minLength": 1,
      "maxLength": 300,
      "description": "Which server: its id (srv_...), its slug, its GitHub repo (https://github.com/owner/name or owner/name), or its exact name. list_servers shows them all."
    }
  },
  "required": [
    "server"
  ],
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}

update_listing

Edit the listing ManyCP sends to every directory. Send only the fields you want to change; the rest stay as they are. Fields: title (max 100 characters), short_description (max 100 characters, because the official MCP Registry rejects longer), description (long text, Markdown is fine), categories (up to 5 ids), tags (up to 15, lowercase words), tools (the FULL list of {name, description}, it replaces the old list), homepage_url (an empty string clears it). Saves at once. Directories that already list the server keep their current text until the next sync or submit. Version, packages and repo come from GitHub and cannot be edited here. Needs a launch credit, Starter or Pro.

Parameters8

server	string	required	Which server: its id (srv_...), its slug, its GitHub repo (https://github.com/owner/name or owner/name), or its exact name. list_servers shows them all.
title	string	optional	Display name, max 100 characters. Empty string clears it.
short_description	string	optional	One plain sentence, max 100 characters. Say what it does and for whom. Empty string clears it.
description	string	optional	The long description, max 5000 characters. Markdown is fine.
categories	array	optional	Up to 5 category ids. Replaces the current categories.
tags	array	optional	Up to 15 short lowercase tags, like 'weather' or 'postgres'. Replaces the current tags.
tools	array	optional	The complete list of tools. It replaces the current list, so include the ones that stay.
homepage_url	string	optional	A full http(s) URL. Empty string clears it.

Raw schema

{
  "type": "object",
  "properties": {
    "server": {
      "type": "string",
      "minLength": 1,
      "maxLength": 300,
      "description": "Which server: its id (srv_...), its slug, its GitHub repo (https://github.com/owner/name or owner/name), or its exact name. list_servers shows them all."
    },
    "title": {
      "description": "Display name, max 100 characters. Empty string clears it.",
      "type": "string",
      "maxLength": 100
    },
    "short_description": {
      "description": "One plain sentence, max 100 characters. Say what it does and for whom. Empty string clears it.",
      "type": "string",
      "maxLength": 100
    },
    "description": {
      "description": "The long description, max 5000 characters. Markdown is fine.",
      "type": "string",
      "maxLength": 5000
    },
    "categories": {
      "description": "Up to 5 category ids. Replaces the current categories.",
      "maxItems": 5,
      "type": "array",
      "items": {
        "type": "string",
        "enum": [
          "aggregators",
          "browser-automation",
          "cloud-platforms",
          "code-execution",
          "communication",
          "databases",
          "data-science",
          "developer-tools",
          "file-systems",
          "finance",
          "knowledge-memory",
          "location",
          "marketing",
          "monitoring",
          "productivity",
          "research",
          "search",
          "security",
          "social-media",
          "version-control",
          "other"
        ]
      }
    },
    "tags": {
      "description": "Up to 15 short lowercase tags, like 'weather' or 'postgres'. Replaces the current tags.",
      "maxItems": 15,
      "type": "array",
      "items": {
        "type": "string",
        "minLength": 1,
        "maxLength": 40
      }
    },
    "tools": {
      "description": "The complete list of tools. It replaces the current list, so include the ones that stay.",
      "maxItems": 100,
      "type": "array",
      "items": {
        "type": "object",
        "properties": {
          "name": {
            "type": "string",
            "minLength": 1,
            "maxLength": 100,
            "description": "The tool's name exactly as the server exposes it."
          },
          "description": {
            "type": "string",
            "maxLength": 500,
            "description": "What the tool does, one or two sentences."
          }
        },
        "required": [
          "name",
          "description"
        ]
      }
    },
    "homepage_url": {
      "description": "A full http(s) URL. Empty string clears it.",
      "type": "string",
      "maxLength": 300
    }
  },
  "required": [
    "server"
  ],
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}

check_listings

Check which MCP directories already list a public GitHub repo. 10 of the 26 directories have a public lookup, so those come back listed or missing (with the listing URL when listed) and the rest come back unknown. No login and no ManyCP server needed, works on every plan and on repos you do not own. Results are cached for about 10 minutes. Use it before add_server to show the gap, or after submit_server to see what went live.

Parameters1

repo_url

string

required

The public GitHub repo: https://github.com/owner/name, or just owner/name.

Raw schema

{
  "type": "object",
  "properties": {
    "repo_url": {
      "type": "string",
      "minLength": 3,
      "maxLength": 300,
      "description": "The public GitHub repo: https://github.com/owner/name, or just owner/name."
    }
  },
  "required": [
    "repo_url"
  ],
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}

submit_server

File a saved server in MCP directories. Per directory the result says what happened. Direct publish (the official MCP Registry) publishes for real. Auto PR forks the target repo and opens a pull request from the user's GitHub account. Auto-indexed just waits for its source. Assisted directories get every field prepared plus a link, and a person finishes them (on Pro, ManyCP staff can). Leave `directories` out to send to every directory that fits and is ready, or pass ids from list_directories to pick some. ManyCP opens at most one pull request per repo per directory, so repeating the call is safe. A directory is only called live after ManyCP confirms it. The first submit of a server takes one launch credit ($19, bought once) unless a subscription covers it. Before the directories, ManyCP also opens ONE pull request on the user's own repo (never a fork) with the files directories look for: .mcp.json, glama.json, gemini-extension.json, server.json and the mcpName marker. cursor.directory, Glama and the Gemini CLI gallery wait until the user merges it, and the result says so. If the user has not allowed pull requests yet, the result is an error with a link they open once to grant GitHub access, then you call this again. Set consent_star to true only after the user agrees to let ManyCP star punkpeye/awesome-remote-mcp-servers on their GitHub account, because that list rejects pull requests from accounts that have not starred it.

Parameters3

server	string	required	Which server: its id (srv_...), its slug, its GitHub repo (https://github.com/owner/name or owner/name), or its exact name. list_servers shows them all.
directories	array	optional	Directory ids from list_directories, like 'official-mcp-registry'. Omit to send to every directory that fits and is ready.
consent_star	boolean	optional	True only if the user said yes to ManyCP starring punkpeye/awesome-remote-mcp-servers for them. Default false.

Raw schema

{
  "type": "object",
  "properties": {
    "server": {
      "type": "string",
      "minLength": 1,
      "maxLength": 300,
      "description": "Which server: its id (srv_...), its slug, its GitHub repo (https://github.com/owner/name or owner/name), or its exact name. list_servers shows them all."
    },
    "directories": {
      "description": "Directory ids from list_directories, like 'official-mcp-registry'. Omit to send to every directory that fits and is ready.",
      "maxItems": 60,
      "type": "array",
      "items": {
        "type": "string",
        "minLength": 1,
        "maxLength": 80
      }
    },
    "consent_star": {
      "description": "True only if the user said yes to ManyCP starring punkpeye/awesome-remote-mcp-servers for them. Default false.",
      "type": "boolean"
    }
  },
  "required": [
    "server"
  ],
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}

sync_server

Re-read a server's GitHub repo right now: latest release or tag, package version, README, description, topics. If the version or listing changed, ManyCP updates the saved listing, marks directories that list an older version as needs_update, and starts update runs where a directory supports it (the official registry gets the new version; pull-request directories get an update PR only when the entry text changed). If nothing changed it says so. Paid plans also sync on their own (Pro every hour, Starter every day), so use this to sync now, for example right after a release. Needs a launched server or a paid plan.

Parameters1

server

string

required

Which server: its id (srv_...), its slug, its GitHub repo (https://github.com/owner/name or owner/name), or its exact name. list_servers shows them all.

Raw schema

{
  "type": "object",
  "properties": {
    "server": {
      "type": "string",
      "minLength": 1,
      "maxLength": 300,
      "description": "Which server: its id (srv_...), its slug, its GitHub repo (https://github.com/owner/name or owner/name), or its exact name. list_servers shows them all."
    }
  },
  "required": [
    "server"
  ],
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}

README.md3 KBView on GitHub

ManyCP MCP server

Submit your MCP server to every MCP directory, from your agent.

ManyCP reads your GitHub repo, drafts one listing, publishes it to the official MCP Registry, opens the pull requests on the awesome lists, prepares the web forms for the rest, and keeps every listing in sync when you ship a new version. This is its remote MCP server, so you can do all of that from Claude Code, Cursor, VS Code or any MCP client:

"Submit my weather-mcp to every directory."

Website: https://manycp.com
Endpoint: https://manycp.com/mcp (Streamable HTTP)
Auth: Authorization: Bearer <key> — create a key at https://manycp.com/app/settings

Tools

Tool	What it does
`check_listings`	Shows which directories already list a public GitHub repo. No plan needed.
`list_directories`	Every directory ManyCP knows, and how each one is handled (direct publish, auto PR, auto-indexed, assisted).
`add_server`	Reads a GitHub repo and saves a draft listing: name, description, tools, install command, `server.json`.
`list_servers`	Your servers, with a status summary per directory.
`get_server`	One server's listing and its status in every directory, with links to PRs and listings.
`update_listing`	Fix the wording, tags, categories or tools of a listing.
`submit_server`	Files the listing everywhere it can: registry publish, pull requests from your own GitHub account, prepared forms.
`sync_server`	Re-reads the repo after a release and updates or flags stale listings.

Install

Claude Code

bash

claude mcp add --transport http manycp https://manycp.com/mcp --header "Authorization: Bearer YOUR_KEY"

Cursor (~/.cursor/mcp.json)

json

{
  "mcpServers": {
    "manycp": {
      "url": "https://manycp.com/mcp",
      "headers": { "Authorization": "Bearer YOUR_KEY" }
    }
  }
}

VS Code (.vscode/mcp.json)

json

{
  "inputs": [{ "type": "promptString", "id": "manycp-key", "description": "ManyCP API key", "password": true }],
  "servers": {
    "manycp": {
      "type": "http",
      "url": "https://manycp.com/mcp",
      "headers": { "Authorization": "Bearer ${input:manycp-key}" }
    }
  }
}

Claude Desktop (via mcp-remote)

json

{
  "mcpServers": {
    "manycp": {
      "command": "npx",
      "args": ["mcp-remote", "https://manycp.com/mcp", "--header", "Authorization:${MANYCP_AUTH}"],
      "env": { "MANYCP_AUTH": "Bearer YOUR_KEY" }
    }
  }
}

How submissions work

Official MCP Registry: published directly with your GitHub identity (io.github.<you>/*).
Awesome lists and GitHub-based catalogs: one pull request per list, opened from your own GitHub account, in each list's exact format, disclosed as sent with ManyCP.
Directories that crawl GitHub: ManyCP opens one PR on your repo with the files they look for.
Web-form directories: the ManyCP browser extension fills each form; you review and press Submit.

License

MIT

Install

Tools (8)

list_directorieslist_serversadd_serverget_serverupdate_listingcheck_listingssubmit_serversync_server

Remote endpoint

Streamable HTTP

Hosted server - connect over the network, no local install.

url

https://manycp.com/mcp

Add to VS Code Add to Cursor

claude_desktop_config.json

json

{
  "mcpServers": {
    "manycp-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://manycp.com/mcp"
      ]
    }
  }
}

Desktop config is stdio-only; this bridges via mcp-remote. Native remote: Settings > Connectors.

io.github.dayyad/manycp-mcp (MCP Server)

🛠️ Key Features

🚀 Use Cases

⚡ Developer Benefits

⚠️ Limitations

Topics

list_directories

list_servers

add_server

get_server

update_listing

check_listings

submit_server

sync_server

ManyCP MCP server

Tools

Install

How submissions work

License

Install

Remote endpoint

Related servers