registry
Eliminates custom API integration work by providing pre-built, tested MCP servers for 70+ enterprise tools.
Production-ready MCP servers for 70+ APIs — GitHub, Google, Notion, Jira & more. Generated from OpenAPI specs, tested against live APIs. Works with Claude Desktop, Cursor, Codex & Claude Code.
- Auto-populate Notion databases from GitHub issue metadata
- Generate Jira tickets from Claude analysis of support emails
- Sync Google Calendar events into project management workflows
Eliminates custom API integration work by providing pre-built, tested MCP servers for 70+ enterprise tools. Reduces time-to-first-API-call from weeks to minutes.
Teams building Claude-powered workflows that need instant, reliable access to GitHub, Google, Notion, Jira, and other SaaS platforms without writing connector code.
https://github.com/mcparmory/registry
By mcparmory
How to Get It
claude plugins install mcparmory/registry
Tip: Paste this into a Claude Code conversation. Verify command matches your Claude Code version.
Auto-generated from the tool's public listing — not hands-on verified. Cross-check against the source repo's README before running.
After installing, paste this into Claude:
Help me auto-populate Notion databases from GitHub issue metadata
Trust Signals Auto-scanned
Community Pulse Active
Discussed on Hacker News, Reddit
- In 2018, “Alaskan Avenger” Jason Vukovich was photographed smiling at his brothe — Reddit · 17085 pts
- So, THATS why they buy things not on the registry — Reddit · 2126 pts
- Claude Code's source code has been leaked via a map file in their NPM registry — Hacker News · 2095 pts
3 mentions across 2 sources
Reviewer notes
Auto-scanned review. These are observations, not a security certification.
Scored from trust signals (evidence-eval-v1): 28 GitHub stars; 1 contributors; last commit 74d ago; license no license.
Things to check
- Scanned, not hands-on tested — this entry was auto-scanned from public metadata (GitHub metrics, license, security flags). No reviewer has run it, and no tool-specific limitations have been documented yet.
- Single maintainer. Consider the risk if this person stops maintaining the project.
How to evaluate tools before deploying →
Data shown here comes from public APIs and automated scanning. Reviewer notes reflect one person's experience. This is not a security certification or legal recommendation. Always evaluate tools according to your own organization's policies.
Evaluation
Scored from trust signals (evidence-eval-v1): 28 GitHub stars; 1 contributors; last commit 74d ago; license no license.