M
MCP Directory CURATED DIRECTORY
911 MCP servers indexed
中文
← Back to directory
O

OpenConnector

Community
Gateway / proxy
Connect once. Use everywhere.

This gateway aggregates or proxies other MCP servers; it only becomes useful once you connect real servers behind it.

How to install ↓ Compare GitHub source repository ↗
Category
Other #131 of 230
Stars
★ 6.0k Very popular
Runtime
Docker · Node.js 22+ · Hosted (no local runtime)
Credentials
Optional API key
License
Apache-2.0
Last commit
52FMRS · D

The source describes OpenConnector as an open-source, self-hosting-compatible connector gateway supporting MCP, HTTP, OpenAPI, an SDK, and a CLI, with credential, policy, Action-contract, and run-log management. It does not provide specific MCP tool identifiers, client compatibility details, or a client installation configuration, so those fields remain empty.

Strongest · Documentation 13/20 Weakest · Reliability 8/20

Reliability
8/20
Security and permissions
10/20
Maintenance
10/20
Documentation
13/20
Setup experience
11/20
Why each score
Reliability 8/20
The README describes Docker, Node.js, an MCP endpoint, HTTP/OpenAPI paths, and a no-auth Action example, making the happy path plausible. However, the server manifest is unavailable, and there is no verifiable MCP tool list, initialization-handshake evidence, committed CI configuration, or key-path test evidence. Tool/behavior consistency and error or edge-case handling therefore remain unverified, warranting deductions.
Security and permissions 10/20
The README identifies credential encryption, OAuth, scopes, runtime tokens, Action allow/block policies, a credential boundary, and redacted run logs, showing baseline attention to permissions and data boundaries. However, source-level evidence is unavailable; dangerous side-effect confirmation, default least privilege, token lifecycle, network data flows, and audit details cannot be verified. No evidence clearly triggers a security red line.
Maintenance 10/20
The project states an Apache-2.0 license and is not archived. It also links contribution, code-of-conduct, and security documentation, indicating basic governance and a security contact path. But the supplied material contains no commit history, release record, dependency-update evidence, vulnerability-response details, or maintainer-response evidence, so sustained maintenance cannot be established.
Documentation 13/20
The README covers architecture, usage paths, Docker, Node.js, Cloudflare, Fly.io, credentials, OAuth, configuration, runtime API, MCP, and development, with several command examples. The manifest is unavailable, and tool parameters, capability limits, costs, troubleshooting, and complete mainstream MCP-client configuration are missing or not verifiable from the supplied material, so points are deducted.
Setup experience 11/20
Docker Compose, source-based Node.js setup, Node.js 22+, Cloudflare, and Fly.io deployment paths are documented, with local console and API examples. A complete path from runtime preparation to connection through a mainstream MCP client is not provided, and OAuth, persistence, and deployment configuration involve substantial manual setup. No verifiable CI or end-to-end installation evidence is supplied, so the score is limited.

Static review · not runListed 2026-07-29

Read the FMRS scoring method →

Fit and risk

What it can accessUses the networkChanges third-party account data

Best for

  • Agent products that need access to many SaaS, developer, data, or communication services
  • Teams that need inspectable Action request and response contracts
  • Developers and teams that want control over credentials and runtime deployment

Not for

  • Simple integrations that need only one service and no connector gateway
  • Users who require a documented list of specific MCP tool identifiers or client integrations
  • Users who do not want to manage credentials, deployment, or runtime configuration

Required permissions

  • API keys, OAuth clients, and provider-specific scopes may need to be configured
  • The runtime may require connections, runtime tokens, and Action allow or block policies
  • Required permissions depend on the connected provider and executed Action

Risks and side effects

  • Connected third-party accounts may let an agent access or modify user data
  • Incorrect scopes, Action policies, or runtime-token settings may broaden access
  • Credentials, transit files, and run logs must be protected in the deployment environment; logs support redaction but still require review
  • Third-party provider APIs, permissions, and availability can affect execution results

Setup

Before you start

Runtime：Docker · Node.js 22+ · Hosted (no local runtime)

The repository provides a Docker Compose startup path: run docker compose up. Alternatively, use Node.js 22 or newer, install dependencies, and run npm run dev. The local console and API documentation are then available from the runtime. The source does not provide a specific MCP client configuration example.

Check that it works

Start the runtime with docker compose up, then connect an MCP client to http://localhost:3000/mcp and confirm connector actions appear in the tool list; alternatively run a no-auth action: curl -s -X POST http://localhost:3000/v1/actions/hackernews.get_top_stories -H 'content-type: application/' -d '{"input":{}}'.

Troubleshooting

  1. Confirm that Node.js 22 or newer is installed
  2. Check that the runtime listens on http://localhost:3000 and the development console uses http://localhost:5173
  3. Review provider credentials, OAuth settings, scopes, and connection aliases
  4. Check runtime tokens and Action allow/block policies
  5. Inspect the console’s runtime overview, recent failures, and run logs
  6. For hosted deployments, confirm required migrations, secrets, and platform resources are configured

Things to try

Once connected, you can ask your AI assistant things like:

  • Use the hackernews.get_top_stories action to show me the current top stories.
  • Search the connector catalog for GitHub actions and show me what schemas they require.
  • Run github.get_current_user to confirm my GitHub connection works.
  • List the providers available on my OpenConnector gateway and their executable actions.

Use cases

Give AI agents durable access to users’ SaaS applications
Execute connector Actions through MCP, HTTP, or OpenAPI
Manage OAuth, API keys, connection identities, scopes, and run logs
Deploy a connector gateway locally or on self-hosted infrastructure

Overview

OpenConnector is an open-source connector gateway for AI agents. It connects more than 1,000 SaaS providers and exposes more than 10,000 prebuilt Actions through an SDK, CLI, MCP, HTTP, and OpenAPI. The runtime manages credentials, OAuth, scopes, policies, and run logs, and supports local, Docker, Fly.io, Cloudflare-compatible, and OOMOL-hosted deployments.

Similar servers

BioMCP 75 · B

One binary. One grammar. Evidence from the biomedical sources you already trust.

★ 659 · Tools 11 Compare with this →
Compare with other MCP servers

Source revision ac0cf61313f7 Data synced 2026-10-19 Read the FMRS scoring method