Best Alternatives to open-connector
API Integration·★ 6.1k·Apache-2.0
Open-source auth gateway connecting 1000+ SaaS providers to AI agents through SDK, CLI, MCP, HTTP, and OpenAPI.
#API Gateway#AI Agents#Connectors#Workflow Automation#OpenAPI#Credential Management#Runtime Environment#Microservices
01
Best Alternatives to open-connector
ToolDescriptionStarsLicenseUpdated
01
GitHub MCP Server
GitHub MCP ServerGitHub's official MCP Server. Allows AI agents to interact directly with your GitHub repositories (read files, search code, issues).
★ 34.0k
MIT
5d ago
Details →02
python-sdk
python-sdkThe official Python SDK for Model Context Protocol servers and clients
★ 24.7k
MIT
1d ago
Details →03
Figma-Context-MCP
Figma-Context-MCPMCP server to provide Figma layout information to AI coding agents like Cursor
★ 16.1k
MIT
1d ago
Details →04
Integuru
InteguruThe first AI agent that builds permissionless integrations through reverse engineering platforms' internal APIs.
★ 4.8k
AGPL-3.0
4mo ago
Details →05
mcp
mcpAWS MCP Servers — helping you get the most out of AWS, wherever you use MCP.
★ 9.8k
—
1d ago
Details →06
aci
aciACI.dev is the open source tool-calling platform that hooks up 600+ tools into any agentic IDE or custom AI agent through direct function calling or a unified MCP server. The birthplace of VibeOps.
★ 4.9k
Apache-2.0
5d ago
Details →
08
python-utcp
python-utcpOfficial python implementation of UTCP. UTCP is an open standard that lets AI agents call any API directly, without extra middleware.
★ 653
MPL-2.0
3d ago
Details →02
Side-by-Side Comparison
| Field | open-connector | GitHub MCP Server | python-sdk | Figma-Context-MCP |
|---|---|---|---|---|
| Category | API Integration | API Integration | API Integration | API Integration |
| Stars | ★ 6.1k | ★ 34.0k | ★ 24.7k | ★ 16.1k |
| License | Apache-2.0 | MIT | MIT | MIT |
| Updated | 1d ago | 5d ago | 1d ago | 1d ago |
| Open Source | Yes | Yes | Yes | Yes |
03
Decision Guide: When to Choose open-connector vs Switch
+ When open-connector is the Best Choice
- You want your agents to use 1,000+ app integrations without handing provider credentials to the agent process.
- You want a self-hostable alternative to Composio, runnable with Docker, on Fly.io or on Cloudflare Workers.
- You want inspectable Action contracts (schemas, required scopes, executor source) with scopes, runtime tokens and allow and block policies.
! When to Look for Alternatives
- You need deep coverage of one service: integration depth varies across 1,000+ providers.
- You want no vendor path at all: hosted authentication and the commercial runtime come from OOMOL, and self-hosting means you run the runtime yourself.
- You do not want to connect and manage each provider's account, credentials and scopes.
04
Head-to-Head Comparison Notes
★ 4.9k·Apache-2.0
Both offer a catalogue of integrations with built-in OAuth for agents. OpenConnector lists 1,000+ providers and 10,000+ Actions and keeps credentials out of the agent. ACI lists 600+ integrations with dynamic tool discovery.
★ 5.8k·Apache-2.0
Klavis bundles Strata tool routing, 100+ MCP integrations and an MCP sandbox for RL training. OpenConnector is a connector gateway with a far larger catalogue.
05
Compare open-connector With Others
06
FAQ
What is open-connector?
OpenConnector is an open-source connector gateway that allows AI agents and applications to connect to over 1,000 providers and utilize 10,000+ prebuilt actions. It centralizes credential management and exposes a unified catalog, enabling robust and inspectable access to various user application accounts without exposing sensitive data to agent processes.
What is the best alternative to open-connector?
GitHub MCP Server is the top-rated alternative to open-connector in the API Integration category.
Is there a free alternative to open-connector?
GitHub MCP Server is a free, open-source alternative.
Is open-connector open source?
Yes, open-connector is open source on GitHub, licensed under Apache-2.0.
Why do users look for alternatives to open-connector?
You need deep coverage of one service: integration depth varies across 1,000+ providers.. You want no vendor path at all: hosted authentication and the commercial runtime come from OOMOL, and self-hosting means you run the runtime yourself.. You do not want to connect and manage each provider's account, credentials and scopes..