How to submit an MCP server to ToolSDK MCP Registry
Open a pull request that adds one entry to toolsdk-ai/toolsdk-mcp-registry. A maintainer merges it.
An npm-focused registry used by ToolSDK.
- How
- Auto PR
- Fits
- Local and remote servers
- By hand
- ~15 min
- Speed
- Merged in batches. Median about 12 days (Sept 2026).
The steps, by hand
- 1
Read docs/CONTRIBUTING.md in the repo.
- 2
Fork toolsdk-ai/toolsdk-mcp-registry.
- 3
Add packages/<category>/<name>.json with type "mcp-server", name, packageName, description, url, runtime, license and env.
- 4
Remote servers: the packageName starts with @toolsdk-remote/ and the file has a remotes list.
- 5
Open a pull request. One server per PR.
What you need
- One server per pull request
- Do not edit the README or the generated indexes
- Remote servers: HTTPS only and a @toolsdk-remote/ package name
// or skip all of that
Or let ManyCP do it in one click
ManyCP forks toolsdk-ai/toolsdk-mcp-registry, adds your entry in the exact format, and opens the pull request from your GitHub account. It tracks the PR until it is merged.