submit_server

io.github.dayyad/manycp-mcp · Verify this 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.