Log inSubmit server
Open Connector logo

Open Connector

Routes AI agents to 1,000+ providers and 10,000+ prebuilt Actions through MCP, HTTP, OpenAPI, SDK, or CLI.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Open Connector

Pick your client, then add it in one click or paste the config.

No confirmed install command yet

We only publish a config when the install details come from the project itself — its README, its docs, or a verified owner. We haven’t found those for open-connector, and we’d rather show nothing than a guess you’d paste into your client.

Open setup steps on GitHub

Overview

open-connector MCP server gives AI agents access to a shared catalog of more than 1,000 providers and 10,000 prebuilt Actions. It keeps provider credentials behind a gateway while agents discover schemas, select connection aliases, and execute Actions through MCP, HTTP, OpenAPI, the Connector SDK, or the oo CLI. Deploy it locally, on your own infrastructure, or through OOMOL's hosted runtime. Reach for it when an agent product needs reusable access to users' SaaS accounts with scoped tokens, OAuth, policies, and inspectable run logs.

Use cases

  • Connect agent workflows to users' SaaS accounts
  • Expose provider Actions through MCP
  • Inspect schemas and scopes before executing operations
  • Apply allow and block policies to agent tool calls
  • Run a private connector gateway with Docker or Node.js

Key features

  • Catalog of 1,000+ providers and 10,000+ prebuilt Actions
  • MCP, HTTP, OpenAPI, SDK, and CLI access
  • OAuth 2.1 authorization with PKCE S256
  • API key, OAuth, custom, and no-auth credentials
  • Scoped runtime tokens and Action policies
  • SQLite, PostgreSQL, and S3-compatible storage options

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked Today

Recent health check succeeded.

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars6.2kStargazers on the source repository.
Last commitTodayMost recent push to the default branch.

How Open Connector works

What open-connector does

open-connector provides a connector gateway between AI agents or applications and services such as GitHub, Gmail, Notion, BigQuery, Google Analytics, Supabase, Airtable, and Slack. Its catalog contains more than 1,000 providers and 10,000 prebuilt Actions. Actions expose structured request and response schemas, required scopes, and executor information so applications can inspect an operation before running it.

The gateway is designed to keep provider credentials outside the agent process. Agents receive provider metadata, safe connection labels, and execution results, while credentials remain inside the runtime boundary. Supported credential patterns include API keys, OAuth 2, custom credentials, and providers that require no authentication.

How it works

An agent or application connects through MCP, HTTP, OpenAPI, the Connector SDK, or the oo CLI. It can search the catalog, inspect an Action, choose a connection alias, and submit the operation to the gateway. The gateway applies connection identity, scopes, runtime-token rules, and Action allow or block policies before invoking the provider executor.

Remote MCP access is supported through the gateway's MCP endpoint, while direct HTTP calls use the /v1/actions/* routes. The generated OpenAPI document is available at /openapi.json. A built-in OAuth 2.1 authorization server supports dynamically registered clients, PKCE S256, and revocable access tokens with policy-scoped permissions.

A local Web Console covers connector browsing, credential setup, runtime-token creation, and usage inspection. Runtime data can include redacted execution logs, recent failures, tool-call trends, and recent calls. Temporary file transit is also supported through local or S3-compatible storage.

Setup and configuration

Self-hosted deployments can run with Docker or Node.js 22+ and use SQLite or PostgreSQL for state. File transit can use local storage or an S3-compatible service. The project also supports deployment on Cloudflare and lists additional managed deployment platforms, alongside OOMOL's hosted runtime.

With a self-hosted runtime, the operator manages storage and OAuth applications. The hosted option provides managed OAuth and a hosted runtime without requiring deployment or OAuth app setup. The Connector SDK offers a TypeScript HTTP client, while the oo connector command provides a local relay for searching, inspecting, and running Actions.

Tools and capabilities

  • MCP access for MCP-capable agent hosts through the gateway endpoint.
  • HTTP and OpenAPI access for custom clients.
  • Connector SDK support through OpenConnector, Connector, and ProjectConnector client variants.
  • Catalog search and Action inspection before execution.
  • Credential support for API keys, OAuth 2, custom credentials, and no-auth providers.
  • Runtime tokens, scopes, connection aliases, and Action allow/block policies.
  • OAuth 2.1 authorization with dynamic client registration, PKCE S256, and revocation.
  • Web Console administration, credential configuration, and runtime debugging.

Limitations and notes

Self-hosting transfers responsibility for storage and OAuth application configuration to the operator. Provider names and trademarks belong to their respective owners. The available catalog, Actions, scopes, and provider authentication requirements can vary by connector.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Open Connector

open-connector is an MCP server that connects AI agents to more than 1,000 SaaS and data providers through a gateway. Its main tools support catalog discovery, Action inspection, schema and scope review, connection selection, and Action execution while keeping provider credentials behind the runtime.

Run it locally with Docker or Node.js 22+, or use OOMOL's hosted runtime. Self-hosted deployments can store state in SQLite or PostgreSQL and use local or S3-compatible transit storage; the operator manages storage and OAuth applications.

open-connector keeps provider secrets inside the runtime boundary rather than passing them to the agent process. Agents work with metadata, safe account labels, connection aliases, and results, while scopes, runtime tokens, and Action policies control execution.

Yes, open-connector supports self-hosting with Docker or Node.js. You can run it locally or on your own infrastructure, use SQLite or PostgreSQL for state, choose local or S3-compatible transit storage, and expose MCP, HTTP, OpenAPI, and the Web Console.

Yes, open-connector can be used with Cursor through its MCP endpoint. The server exposes MCP over HTTP at the configured gateway endpoint, allowing an MCP-capable host to discover and run available connector Actions.

Related MCP servers

All in Aggregators All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewOpen Connector AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/open-connector?style=directory)](https://allmcps.com/mcp/open-connector)
HTML Embed
<a href="https://allmcps.com/mcp/open-connector"><img src="https://allmcps.com/api/badge/open-connector?style=directory" alt="Open Connector on AllMCPs" /></a>