Built-in connector catalogs never cover every API a B2B product needs. The Custom Connector Registry lets developers register any API as a first-class connector in Scalekit — with full OAuth configuration, tool schemas, and proxied execution. The connector catalog is now extensible by the developer, not gated on Scalekit's release cycle.

A developer building an operations agent for enterprise customers needs to call a proprietary ERP system and an internal approval workflow API. They register both as custom providers in Scalekit — defining the OAuth config, tool schemas, and proxy routing. From that point, agents treat these exactly like any built-in connector: authenticated, proxied, and manageable through the dashboard.

For teams running their own MCP servers: register the MCP server URL as a custom provider, configure auth, and Scalekit handles tool discovery and authenticated execution automatically. No separate MCP client plumbing required.

What's included

• OAuth, static credentials, API keys, and M2M — all auth patterns work for custom providers.
• Custom providers get the same proxy routing, auth injection, and credential management as built-in connectors.
• Custom MCP servers are a supported provider type — bring-your-own-MCP-server is now first-class.
• The dashboard surfaces custom providers alongside built-ins with filtering controls.