Add your open-source MCP server
We've just added an MCP Servers section to the README, and we'd like the community to fill it out.
Model Context Protocol servers let AI agents call APIs as tools. If you maintain one and it's open source, we want it listed.
What qualifies
Your server must meet all of these:
- Open source, with a public repo and an OSI-approved license
- Actually runs: a user can install it and make a successful tool call today
- Documented: a README with install steps and the list of tools it exposes
- Not a thin wrapper: it exposes real capability, not one
fetch()around a public endpoint that already has a row elsewhere in this README - Not abandoned: a commit or release in the last 6 months
Hosted/commercial servers are welcome if the server implementation itself is open source. A closed-source server behind a signup page is not a fit for this list.
How to add yours
- Fork the repo and create a branch:
add/<your-server-name>-mcp - Add one row to the
## MCP Serverstable inREADME.md - Open a PR titled
Add <Your Server> MCP server - Fill in the PR checklist
Row template — copy this:
| [Name](https://link-to-repo-or-docs) | What it does, under 100 characters | `apiKey` | `stdio`, `HTTP` | [Cursor](url) · [Glama](url) |Column reference:
| Column | Accepted values | Notes |
|---|---|---|
| Name | [Title](url) |
Link to the repo or the official docs page. Don't end the title with "API" |
| Description | Free text | Capitalized, no trailing period, max 100 characters |
| Auth | No, `apiKey`, `OAuth` |
Backticks required for everything except No |
| Transport | `stdio`, `HTTP`, `SSE` |
Comma-separate if you support several |
| Install | [Marketplace](url) separated by ·, or – |
Cursor, Anthropic and Glama are the ones we track. Link only to listings that actually exist |
⚠️ The Install column is not aspirational. Use
–if your server isn't published on any marketplace yet, that is a completely normal state and costs you nothing. A link to a listing that doesn't exist gets the PR closed.
Where to put your row
Add it alphabetically within the table, below the existing seed entries. Don't reorder or touch other people's rows, that's what causes merge conflicts.
PR checklist
Copy this into your PR description:
- [ ] Repo is open source with an OSI-approved license
- [ ] Server installs and makes a successful tool call
- [ ] README documents install steps and exposed tools
- [ ] Commit or release within the last 6 months
- [ ] Description is under 100 characters, capitalized, no trailing period
- [ ] Install cell links to real listings, or uses `–`
- [ ] Added exactly one row, alphabetically placed
- [ ] No other lines in README.md were modifiedSource: public-apis/public-apis