# Open Connector

> Open-source auth gateway connecting 1000+ SaaS providers to AI agents through SDK, CLI, MCP, HTTP, and OpenAPI.

- **Type:** MCP server
- **Install:** `agentstack add mcp-oomol-lab-open-connector`
- **Verified:** Yes — security-reviewed for prompt injection and unsafe behavior
- **Seller:** [oomol-lab](https://agentstack.voostack.com/s/oomol-lab)
- **Installs:** 0
- **Category:** [Cloud & Infrastructure](https://agentstack.voostack.com/c/cloud-infrastructure)
- **Latest version:** 0.1.0
- **License:** Apache-2.0
- **Upstream author:** [oomol-lab](https://github.com/oomol-lab)
- **Source:** https://github.com/oomol-lab/open-connector
- **Website:** https://oomol.com/

## Install

```sh
agentstack add mcp-oomol-lab-open-connector
```

Requires the [AgentStack CLI](https://agentstack.voostack.com/docs/cli). Works with Claude Code, Cursor, and any MCP-compatible agent.

## About

# OpenConnector

[English](README.md) | [简体中文](README.zh-CN.md)

[](LICENSE.txt)

[](https://oomol.com/apps)
[](https://oomol.com/apps)

OpenConnector is an open-source alternative to Composio for agent-ready SaaS auth, tools, and
integrations. It is a connector layer for agents that need reliable access to user accounts in
external apps. It handles auth, tool execution, and agent-ready integrations. The open-source catalog
currently includes 680+ providers and 7,000+ prebuilt Actions, runs locally or on
Cloudflare-compatible infrastructure, and exposes the same tools through the
[Connector SDK](https://github.com/oomol-lab/connector-sdk), MCP, HTTP, OpenAPI, and a local Web
Console.

OpenConnector gives agents a controlled path into real products while keeping credentials, scopes,
schemas, policies, and run logs inside an inspectable runtime. The gateway, provider catalog, and
Action executors are open source, so teams can review contracts, extend providers, and control the
deployment boundary.

The open-source catalog is the portion of OOMOL's connector catalog that has completed migration
into maintainable provider definitions and executors. The hosted OOMOL product covers 1,000+
providers today. Both surfaces use compatible connector interfaces and Action contracts, so teams
can start hosted for speed and later move the same connector layer to private or self-hosted runtime
infrastructure.

[oo CLI](https://github.com/oomol-lab/oo-cli) support for the open-source runtime is being added and
is targeted for mid-July 2026. Until then, use the SDK, MCP, HTTP API, OpenAPI, and local Web
Console paths below.

## What OpenConnector Provides

- A working connector catalog: [680+ providers and 7,000+ prebuilt Actions](docs/providers.md)
  across products such as GitHub, Gmail, Notion, BigQuery, Google Analytics, Supabase, Airtable,
  Slack, and more.
- Credential handling in one runtime: API keys, OAuth2, custom credentials, and providers that do
  not require auth.
- Inspectable Action contracts: request/response schemas, required scopes, and
  lazy-loaded executors live in source.
- Deployment options for different runtime boundaries: local Docker or Node.js for development, plus
  Cloudflare-compatible deployment on Workers, D1, R2, and Static Assets.
- Agent-facing interfaces: [Connector SDK](https://github.com/oomol-lab/connector-sdk),
  MCP, HTTP API, OpenAPI, and a local Web Console, with
  [oo CLI](https://github.com/oomol-lab/oo-cli) support being adapted for the open-source runtime.
- Runtime guardrails for production use: connection identity, scopes, runtime tokens, action
  allow/block policies, temporary file transit, and redacted run logs.

## Where It Fits

OpenConnector fits products where agents need to work inside the tools users already use,
with a clear operating boundary for credentials, scopes, schemas, and execution logs. The hosted and
open-source versions stay interface-compatible, so the same connector layer can move from OOMOL's
hosted service to private or self-hosted infrastructure as deployment requirements change.

- Agent products that need reusable access across work apps, developer tools, data systems,
  communication platforms, and AI services.
- Products adding agent workflows that need stable, inspectable Action contracts for user app
  access.
- Teams that want to start hosted for speed and keep a path toward private or self-hosted runtime
  control.

## Developer Tools

| Tool                                                        | Purpose                                                                                                       |
| ----------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------- |
| [Connector SDK](https://github.com/oomol-lab/connector-sdk) | Call connector Actions, proxy upstream APIs, and inspect the catalog from TypeScript apps and agent runtimes. |
| [oo CLI](https://github.com/oomol-lab/oo-cli)               | Open-source runtime support is being added and is targeted for mid-July 2026.                                 |
| MCP                                                         | Expose app Actions to MCP-capable agent hosts through `http://localhost:3000/mcp`.                            |
| HTTP / OpenAPI                                              | Call `/v1/actions/*` directly or inspect the generated `/openapi.json` document.                              |

## Provider Coverage Preview

For coverage planning, the full provider list is available in
[docs/providers.md](docs/providers.md). This preview highlights recognizable productivity apps,
developer tools, analytics products, and AI services from the catalog.

Provider names and trademarks belong to their respective owners and are used only for identification
and interoperability.

## How It Works

```mermaid
flowchart LR
  Agent["AI Agent / App"] -->|"SDK / MCP / HTTP"| Gateway["OpenConnector Gateway"]
  Gateway --> Auth["Credential & OAuth Boundary"]
  Gateway --> Catalog["Provider Catalog"]
  Gateway --> Actions["Open-source Action Executors"]
  Gateway --> Policy["Tokens, Scopes, Allow/Block Policy"]
  Gateway --> Logs["Run Logs"]
  Actions --> Providers["680+ Providers"]
  Console["Web Console"] --> Gateway
  Cloudflare["Cloudflare Workers, D1, R2"] -. deploy .-> Gateway
```

Apps and agents discover Actions, inspect schemas and scopes, select a connection alias, and execute
through the gateway. Provider secrets stay behind the runtime boundary; agents receive the metadata,
safe account labels, and execution results needed for the run.

## Usage Paths

| Path                         | Best for                                            | Includes                                                                                                                                 |
| ---------------------------- | --------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------- |
| Open-source self-host        | Developers and teams that want full control         | Local Docker or Node runtime, SQLite storage, MCP, HTTP, OpenAPI, and Web Console                                                        |
| Cloudflare-compatible deploy | Teams that want a lightweight hosted runtime        | Workers runtime, D1 state, R2 transit files, and Static Assets for the console                                                           |
| [OOMOL](https://oomol.com/)  | Teams blocked by OAuth approval or launch deadlines | Hosted auth, runtime, and 1,000+ provider catalog; compatible with the open-source interface for later private or self-hosted deployment |

## Cloudflare Quick Start Video

[](https://www.youtube.com/watch?v=R0V1ZdCuTgc)

The
[Cloudflare Workers deployment walkthrough](https://www.youtube.com/watch?v=R0V1ZdCuTgc) shows how
to launch OpenConnector on Cloudflare with Workers, D1, R2, and the Web Console. The video follows
the same flow as [docs/cloudflare.md](docs/cloudflare.md): create Cloudflare resources, copy
`wrangler.example.jsonc` to `wrangler.local.jsonc`, apply D1 migrations, set required secrets, and
run `npm run deploy:cloudflare`.

## Quick Start

Start the runtime with Docker Compose:

```bash
docker compose up --build
```

Open the local console and generated API reference:

```text
http://localhost:3000
http://localhost:3000/docs
```

Run a no-auth Action to verify the runtime:

```bash
curl -s -X POST http://localhost:3000/v1/actions/hackernews.get_top_stories \
  -H 'content-type: application/json' \
  -d '{"input":{}}'
```

See [docs/quickstart.md](docs/quickstart.md) for the full local setup, first provider connection,
OAuth flow, and runtime settings.

## Connect A Provider

GitHub is the simplest credentialed example because it can use a personal access token:

```bash
curl -s -X PUT http://localhost:3000/api/connections/github \
  -H 'content-type: application/json' \
  -d '{"authType":"api_key","values":{"apiKey":"github_pat_..."}}'

curl -s -X POST http://localhost:3000/v1/actions/github.get_current_user \
  -H 'content-type: application/json' \
  -d '{"input":{}}'
```

For OAuth2 apps, named connections, credential encryption, token refresh, and action policies, see
[docs/credentials.md](docs/credentials.md) and [docs/configuration.md](docs/configuration.md).

## Agent Tool Interfaces

OpenConnector exposes the same Action catalog through several agent-facing interfaces:

- MCP: `http://localhost:3000/mcp`
- HTTP runtime API: `/v1/actions`
- OpenAPI document: `/openapi.json`
- Action guides: `/api/actions/:actionId/agent.md`
- Web Console examples: cURL, TypeScript, and agent prompt snippets for each Action

See [docs/runtime-api.md](docs/runtime-api.md) for endpoint details, response envelopes, auth
headers, MCP tools, and Action guide examples.

## Web Console

Open `http://localhost:3000` after starting the runtime. The console supports provider browsing,
API key and OAuth client configuration, runtime token creation, Action schema inspection, Action
debugging, recent run review, and access to the generated OpenAPI and MCP metadata.

## Cloudflare Deployment

OpenConnector supports Cloudflare Workers as a metadata and runtime-state deployment target using
Workers, D1, R2, and Static Assets.

See [docs/cloudflare.md](docs/cloudflare.md) for resource creation, migrations, secrets, local Worker
preview, and remote deployment.

## OOMOL And Wanta

Teams can choose the product path that matches their preferred level of runtime ownership.
[OpenConnector](https://github.com/oomol-lab/open-connector) provides open-source self-hosting and
deployment control. [OOMOL](https://oomol.com/) provides hosted auth, runtime infrastructure, and
the broader 1,000+ provider catalog while keeping compatible connector interfaces and Action
contracts.

For small teams or individuals using a desktop Agent directly, [Wanta](https://wanta.ai/) connects
apps through a desktop product experience with team app sharing, permission control, multiple
connected accounts, and workspace-specific connections.

## Documentation

- [Quickstart](docs/quickstart.md)
- [Developer tools](docs/sdk-cli.md)
- [Provider coverage](docs/providers.md)
- [Runtime API and MCP](docs/runtime-api.md)
- [Cloudflare deployment](docs/cloudflare.md)
- [Configuration](docs/configuration.md)
- [Credentials and OAuth](docs/credentials.md)
- [Catalog format](docs/catalog-format.md)
- [Verification language](docs/verification.md)
- [Contributing](CONTRIBUTING.md)
- [Code of Conduct](CODE_OF_CONDUCT.md)
- [Security](SECURITY.md)

## Development

Use Node.js 22 or newer:

```bash
npm install
npm run build:web
npm run dev
```

Before opening a pull request:

```bash
npm run fix-check
npm test
```

Provider code lives under `src/providers/`. See
[CONTRIBUTING.md](CONTRIBUTING.md#adding-providers) for provider contribution rules.

## License Scope

Unless otherwise noted, the source code, scripts, generated project scaffolding, tests, and
documentation authored for this repository are licensed under the Apache License, Version 2.0. See
[LICENSE.txt](LICENSE.txt).

The Apache-2.0 license for this repository does not grant rights to third-party products,
providers, apps, APIs, trademarks, service marks, trade names, logos, icons, brand assets,
documentation, screenshots, or other copyrighted materials owned by their respective holders.

Provider and app names, metadata, links, scopes, permissions, and optional logos/icons are included
only to identify services and enable interoperability. All third-party brand and product rights
remain with their respective owners. Inclusion in this catalog does not imply endorsement,
sponsorship, partnership, certification, or verification by those owners.

If you contribute provider metadata or assets, only submit material you have the right to submit.
Prefer linking to official public assets instead of copying brand files into this repository.

## Community

Please keep issues and pull requests focused, respectful, and actionable. Participation in this
project is governed by [CODE_OF_CONDUCT.md](CODE_OF_CONDUCT.md).

## Source & license

This open-source MCP server is cataloged on AgentStack and links to its original source — we do not rehost the code.

- **Author:** [oomol-lab](https://github.com/oomol-lab)
- **Source:** [oomol-lab/open-connector](https://github.com/oomol-lab/open-connector)
- **License:** Apache-2.0
- **Homepage:** https://oomol.com/

Install and usage instructions live in the source repository linked above.

## Pricing

- **Free** — Free

## Security capabilities

Automated source analysis of v0.1.0 — what this tool can access:

- **Network access:** yes
- **Filesystem access:** no
- **Shell / process execution:** no
- **Environment & secrets:** no
- **Dynamic code execution:** no

*"Yes" means the capability is present in the source — more access means more to trust, not that it is unsafe.*


## Versions

- **0.1.0** — security scan: passed — Imported from the upstream source.

## Links

- Listing page: https://agentstack.voostack.com/l/mcp-oomol-lab-open-connector
- Seller: https://agentstack.voostack.com/s/oomol-lab
- Browse the marketplace: https://agentstack.voostack.com/browse

---
Listed on AgentStack — the marketplace for AI agent skills and MCP servers. Every listing is security-reviewed. Creators keep 70%.