OpenConnector ships v1.2.0 of its agent credential gateway

OpenConnector released v1.2.0 on July 16, the latest version of a self-hosted gateway that keeps SaaS credentials out of AI agents' hands entirely, per the oomol-lab repository. Anyone connecting an agent to a real SaaS account has to decide how much that agent can see. Handing over raw API keys means a bad tool call or prompt injection can act with full account privileges.

OpenConnector is Apache 2.0 licensed and has picked up 2,682 GitHub stars since June 29, per the repository. It pitches itself as an open alternative to Composio, connecting to more than 1,000 SaaS providers and exposing over 10,000 actions. It returns only execution results and metadata to the agent, never the underlying credential.

It supports API keys, OAuth2, custom credentials, and no-auth providers. The tool exposes a TypeScript SDK, an oo connector CLI relay, an MCP endpoint at /mcp, an HTTP/OpenAPI surface at /v1/actions/*, and a debug dashboard.

That's a wide surface for a young project to maintain. The repo doesn't say how OpenConnector handles provider API changes across its 1,000-plus integrations, or what happens when one breaks.

The timing fits a pattern: credential managers and agent tooling now keep secrets behind a runtime boundary the agent never crosses. OpenConnector is a fully open, self-hosted bet on that idea, for anyone who doesn't want a third party holding the keys to a thousand integrations.