ManyCP MCP server

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.

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

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.

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

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).

{
  "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 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.

{
  "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"
}

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.

{
  "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 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.

{
  "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"
}

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.

{
  "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"
}

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.

{
  "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"
}