← Registry

Developer Tools

manycp.com

ManyCP is an MCP server that helps developers manage, add, and update their MCP server listings across multiple public directories.

1 endpoint8 known toolsFirst detected October 1, 2026Last detected October 1, 2026

ENDPOINT 1

https://manycp.com/mcp

No auth detected

MCP server metadata

Name
manycp
Version
1.0.0
Capabilities
tools
Server instructions

Connect ManyCP first: create an API key at https://manycp.com/app/settings and send it as 'Authorization: Bearer <key>'. Until then every tool call answers with this same sentence. ManyCP files a developer's MCP server in every MCP directory and keeps each listing current. It knows 26 directories: 1 direct publish (the official MCP Registry), 11 auto pull request, 1 auto-indexed, 13 assisted (ManyCP prepares every field, a person sends it). Usual path: 1. check_listings {repo_url} shows where a public GitHub repo is already listed. No plan needed. 2. add_server {repo_url} reads the repo and saves a draft listing. 3. get_server {server} shows the listing and the status in each directory. update_listing fixes wording. 4. submit_server {server} files it. Pull requests come from the user's own GitHub account and say they were sent with ManyCP. 5. sync_server {server} re-reads the repo after a release and marks stale listings. Rules: - Never say a listing is live until get_server shows the status live. ManyCP checks before it says so. - ManyCP only opens pull requests for repos the user owns, at most one per repo per directory. - No API key was sent. Read tools (list_directories, list_servers, get_server, check_listings) work on every plan once a key is connected. add_server, update_listing, submit_server, sync_server need a launch credit ($19, once), Starter or Pro. - A tool that cannot finish returns isError true with the next step in plain words. Show that step to the user. - Ask the user before you set consent_star to true.

Known tools 8

list_directories

List every MCP directory ManyCP can file a server in (26 today).

Inferred read-only
list_servers

List the MCP servers on this ManyCP account.

Inferred read-only
add_server

Add an MCP server to ManyCP from its public GitHub repo.

Inferred read-only
get_server

Get one server's full listing and its status in every directory that fits it.

Inferred read-only
update_listing

Edit the listing ManyCP sends to every directory.

Potential side effects
check_listings

Check which MCP directories already list a public GitHub repo.

Inferred read-only
submit_server

File a saved server in MCP directories.

Inferred read-only
sync_server

Re-read a server's GitHub repo right now: latest release or tag, package version, README, description, topics.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.manycp]
url = "https://manycp.com/mcp"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "manycp": {
      "type": "http",
      "url": "https://manycp.com/mcp"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: manycp
Remote MCP URL: https://manycp.com/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "manycp": {
      "url": "https://manycp.com/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "manycp": {
      "type": "http",
      "url": "https://manycp.com/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "manycp",
  "transport": "streamable-http",
  "url": "https://manycp.com/mcp"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Trust Data Available

BuiltWith Trust API v2 evidence for manycp.com was fetched 2026-10-03T07:38:42.543Z.

Trust status Neutral

manycp.com is assessed as Neutral: No suspicious signals found, but no strong positive signal either

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.