What to prepare
- You maintain the server and it is officially yours; its public source repository is on GitHub.
- A one-line description of 10 to 240 characters and at least two descriptive GitHub topics on the repository (they become the tags).
- An existing mcpHQ category id, set as the mcpHQ category if it differs from your shared category.
- No existing entry, and no open pull request, for the name, repository or endpoint.
One data entry, four generated files
The service adds one entry to the data file and the matching rows and counts to the README, llms.txt and llms-full.txt. It stops if the contribution rules, generators or file layout change. mcpHQ decides inclusion and timing.
Submission workflow
- Run the free preflight: it checks ownership, pins the reviewed contribution rules and generators, and scans main and open pull requests for duplicates.
- Review the exact diff for each of the four files: the data entry and the regenerated README, llms.txt and llms-full.txt.
- Authorize it; the service account opens one pull request from its fork with maintainer edits enabled.
- Track maintainer review; the entry is confirmed only once it is on main.
Blockers to resolve before review
Use these as preparation checks. The destination makes its own acceptance decision.
- A duplicate entry or an open pull request for the same server.
- A server that is not officially yours, has no clear purpose or docs, or a category that does not exist.
Primary sources
Checked 2026-11-04. Follow the destination’s current instructions if its requirements change.