OpenConnector

OpenConnector is a connector gateway that gives AI agents and applications authenticated access to the SaaS accounts their users already have. You connect a user's app accounts once, and agents then call a shared catalog of more than 1,000 providers and 10,000 prebuilt Actions through the gateway. It positions itself as an alternative to Pipedream and Composio.

Provider credentials stay behind the gateway. Apps and agents discover Actions, inspect their request and response schemas and required scopes, choose a connection alias, and execute. The agent receives metadata, safe account labels, and results, never the provider secrets. The runtime handles API keys, OAuth2, custom credentials, and no-auth providers, and applies runtime tokens, scopes, allow and block policies on Actions, temporary file transit, and redacted run logs.

Clients reach the gateway four ways: a TypeScript SDK from app code, the oo CLI as a relay for local agents, an MCP endpoint for agent hosts, and HTTP with a generated OpenAPI document. A web console browses connectors, configures credentials and OAuth clients, creates runtime tokens, debugs Actions, and shows usage, failures, and recent calls.

OpenConnector runs self-hosted with Docker or Node.js, storing state in SQLite or PostgreSQL and transit files locally or in S3-compatible storage, and on Kubernetes through a Helm chart. It also deploys to Cloudflare Workers (with D1 and R2), Fly.io, and other platforms. OOMOL offers a hosted runtime with preconfigured OAuth apps, using the same provider IDs, Action IDs, and schemas as the open-source runtime.