Browsing the Registry
The Registry lists MCP servers complete with verified metadata:- Server Title & Description: Functional overview and provider details
- Tool Catalog: Full list of callable tools with JSON input parameter schemas
- Quickstart Configs: Copy-ready configurations for Claude Desktop, Cursor, and Streamable HTTP clients
- Required Secrets: Environment variables and authentication headers needed at runtime
- Repository Links: Source code and deployment manifests
Connecting a Registry Server to Your Gateway
From any Registry detail view, click Connect to Gateway to multiplex the server into your active MCP Gateway:- Karada creates an isolated namespaced connection using the server’s canonical prefix (e.g.,
github__,stripe__). - Configures the upstream Streamable HTTP endpoint automatically.
- Prompts for required API keys or secrets, storing them in your encrypted vault.
Publishing to the Registry (Direct Gateway Distribution)
Publishing your MCP tools to the Karada Registry gets them directly in front of users using our universal gateway across Cursor, Claude Code, Windsurf, and enterprise agent fleets without manual client configuration. Any MCP server built on Karada—via Auto-MCP or custom code—can be published to the Registry:- Open your Project Dashboard.
- Select Publish to Registry from the project menu.
- Karada runs automated compliance checks to ensure your server responds to protocol handshakes (
initializeandtools/list). - Upon passing validation, your server is indexed with live documentation and parameter schemas.
Claim Precedence & Verification
For high-volume public APIs (such as Stripe, GitHub, and Jira), Karada enforces claim precedence. The initial verified publisher holds the canonical listing. Additional contributors can submit claim requests or publish specialized variants under dedicated namespaces.Registry Plugins
The Registry also indexes Plugins—modular extensions that inject telemetry, caching, or security logic into any MCP server:- Discover approved plugins for your organization
- Package custom handlers and deploy them across team workspaces
- Hook into the MCP request lifecycle without altering upstream server code