Fetching from the wire…
01
02
03
04
05
06
07
08
Public story · 2026-07-16 · high
The Apache-licensed Composio alternative drew 2,682 GitHub stars in under three weeks by keeping credentials out of agents' reach.
Why now: OpenConnector's climb to 2,682 GitHub stars in under three weeks, through July 16, is what makes v1.2.0 worth watching.
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.
Each link below shares sources, entities, or timing with this story.
Cursor uses MCP / Shared entities / Same source domain / What happened next
Linked by a graph relationship (Cursor uses MCP); both cover Apache, CLI, Given, MCP; reported by the same outlet (github.com).
Claude Code uses MCP / Shared entities / Same source domain / Shared topic / What happened next
Linked by a graph relationship (Claude Code uses MCP); both cover Apache, HTTP, July; reported by the same outlet (github.com).
Claude Code uses MCP / Shared entities / Shared topic / What happened next
Linked by a graph relationship (Claude Code uses MCP); both cover CLI, Given, MCP; overlapping topics (above, action, agent).
Microsoft supports MCP / Shared entities / Same source domain / Shared topic / Earlier coverage
Linked by a graph relationship (Microsoft supports MCP); both cover HTTP, July, MCP; reported by the same outlet (github.com).
Cursor uses MCP / Shared entities / What happened next
Linked by a graph relationship (Cursor uses MCP); both cover Apache, HTTP, July, MCP; picks up the Apache thread on 2026-07-26.
MCP uses OAuth / Shared entities / Same source domain / Shared topic / What happened next
Linked by a graph relationship (MCP uses OAuth); both cover HTTP, MCP; reported by the same outlet (github.com).
OpenAI supports MCP / Shared entities / Same source domain / What happened next
Linked by a graph relationship (OpenAI supports MCP); both cover HTTP, July, MCP; reported by the same outlet (github.com).
OpenCode supports MCP / Shared entities / Same source domain / What happened next
Linked by a graph relationship (OpenCode supports MCP); both cover CLI, July, MCP; reported by the same outlet (github.com).