registry
by mcparmory·★ 25·Score 46
Production-ready MCP servers for 70+ APIs generated from OpenAPI specs with comprehensive tool coverage.
Overview
MCP Armory Registry provides a curated collection of production-ready MCP servers for popular APIs including GitHub, Google, Notion, Jira, and many more. Each server is automatically generated from upstream OpenAPI specifications using the MCP Blacksmith tool, then thoroughly tested against live APIs before release. The servers offer comprehensive API coverage with various authentication methods including API keys, Bearer tokens, OAuth2, JWT, and more.
Try asking AI
After installing, here are 5 things you can ask your AI assistant:
When to choose this
Choose MCP Armory when you need quickly deployable, production-ready MCP servers for popular APIs without custom development, especially when you want standardized implementations with built-in authentication and validation.
When NOT to choose this
Don't choose this if you need custom API endpoints beyond what's available in the registry, or if you require specialized authentication methods not covered by the generated servers.
Comparable tools
Installation
# With uvx (no install needed)
uvx mcparmory-github
# With pip
pip install mcparmory-github
mcparmory-github**MCP client configuration** (Claude Desktop, Cursor, Codex, Claude Code):
{
"mcpServers": {
"github": {
"command": "uvx",
"args": ["mcparmory-github"],
"env": {
"BEARER_TOKEN": "ghp_your_token_here"
}
}
}
}FAQ
- How are these MCP servers different from others?
- These servers are automatically generated from official OpenAPI specifications, ensuring comprehensive API coverage with consistent quality and authentication support.
- What authentication methods are supported?
- Servers support various authentication including API keys, Bearer tokens, Basic auth, OAuth2, JWT, OpenID Connect, and mutual TLS depending on the API.
Compare registry with
Last updated · Auto-generated from public README + GitHub signals.