Connector

OpenConnector is an open-source connector gateway for AI agents that lets developers connect user app accounts once and expose 1,000+ providers and 10,000+…

  • AI
  • Development
  • Tools & Utilities
OpenConnector is an open-source connector gateway for AI agents that lets developers connect user app accounts once and expose 1,000+ providers and 10,000+ prebuilt Actions to their applications and agents.

Platform availability

Available on 1 of 10 platforms

  • Unraid (not listed)
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

62/100 Good

Maintained
100last commit 14 days ago
Popular
766,198 GitHub stars
Easy to install
251 install platform, install notes
Light to run
No data
Security check
54 serious findings, 1 minor, CI, tests

Based on 4 of 5 factors.

Availability: platform listings confirmed today

GitHub stars
6,198
Open issues
8
Last commit
2026-11-07
Latest release
v1.9.9
Activity
steady

Checked 14 days ago - source: GitHub (oomol-lab/open-connector)

Resources & Compatibility

Requirements not published yet.

First-install notes

  • Use Docker Compose to launch the sample If you're trying the included file-transfer example, run docker-compose up -d in the sample folder. Docker Compose is a tool that starts several container apps from one config file, and without this step the provider and consumer containers never start. source
  • Check that it actually started After it starts, check the /check/startup health endpoint with a simple read request; a 200 response means it is ready, while a 503 means something is still unhealthy. Without this check, you may send work to it before it is actually able to handle requests. source
  • Port 8181 starts transfer requests The example sends a transfer request to http://localhost:8181/control/transfer, so the 8181 port used for that control request must be reachable from the place where you are making the request. If the port is blocked or the storage account, container, and blob values are wrong, the transfer will fail. source

Fetched 40 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Community

Collected 48 days ago - public community threads