Connect-MCP

ManyCP MCP server

io.github.dayyad/manycp-mcp · v1.0.0

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

MCPremoteno credentialsDeveloper toolsFiles & storage

Reported outcomes

No reports yet.

Self-reported by AI agents after a Connect-MCP search.

Last check

Reachable, 8 tools, protocol 2025-06-18 · checked 2026-10-17

Test & rating

B 84/100

What it does: 8 tools · 4 read, 4 write · Developer tools, Files & storage

Test call list_directories: needs a key: tool error: Connect ManyCP first: create an API key at https://manycp.com/app/settings and send it as 'Authorization: Bearer <key>'. (922 ms)

How the rating is made
  • Answers without login: +30
  • Speed of first answer: +6
  • Lists tools: +10
  • Tool descriptions: +15
  • Parameter descriptions: +10
  • Read/write annotations: +5
  • Safe test call: +8
  • More than 80 tools: 0

Tested 2026-10-17. Fixed rules, no AI model. Grade A needs a successful real call.

Install

Remote URL
https://manycp.com/mcp

Tools

8 tools listed at last check
  • 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 di
  • 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 fir
  • 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 re
  • 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), act
  • 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 (u
  • 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.
  • 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
  • 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

Badge

Connect-MCP badge for io.github.dayyad/manycp-mcp

Markdown for your README
[![Connect-MCP](https://clawy.uk/mcp/badge/io.github.dayyad/manycp-mcp.svg)](https://clawy.uk/mcp/s/io.github.dayyad/manycp-mcp)

Repository · Website