aci
ACI.dev is a platform that connects agents to external tools. The README says it hooks up 600+ tools into agentic IDEs or custom agents, with multi-tenant auth, granular permissions and dynamic tool discovery, exposed either as direct function calls or through a Unified MCP server. The idea is to avoid writing separate OAuth flows and API clients for each service such as Google Calendar or Slack.
The README's feature list covers 600+ pre-built integrations, built-in OAuth and secrets management for developers and end users, natural-language permission boundaries, tool-use logging and a framework- and model-agnostic design. Dynamic discovery is meant to let an agent find the right tool without stuffing every definition into the context window. Listed use cases include VibeOps (an IDE agent working with Vercel, Supabase, Cloudflare and Sentry), personal assistants, research agents, sales outreach and customer support.
This repository is the platform itself: backend and developer portal, each with its own README for local setup. The Unified MCP server lives in a separate `aci-mcp` repo, and there are Python and TypeScript SDKs. A managed service is offered at aci.dev. The README states everything is released under Apache 2.0. The last push was 2026-05-28. This review is based on the README and repository data; we have not run it ourselves.
Features
Why choose it
Trade-offs
Maintenance check
- Last commit
- 2026-10-23
- Commits, last 90 days
- 9
- Releases, last 90 days
- 0
- Latest release
- v0.0.1-beta.3 (2024-12-01)
- Open issues
- 74
- Recent issues with at least one comment
- 1/10
Oldest week on the left; the latest four weeks are orange. Source: GitHub commit activity.
Status rule: archived on GitHub = Archived; last commit within 90 days = Active; 91 to 365 days = Slowing; older = Stale. All figures come from the GitHub API on the date shown.
Most discussed open issues
- #283 Does aci not support calling Local MCP Server?10 comments · 2025-04-30
- #469 Setting up your workspace...6 comments · 2025-06-09
- #308 App configuration page, replace the app link with a "Go to App" button5 comments · 2025-05-03
- #346 Enable Sentry Bug Report Widget on the Dev Portal4 comments · 2025-05-09
- #317 Log instruction filter related info for analytics4 comments · 2025-05-04
Issue titles are quoted from GitHub. Open the link to check whether a problem still applies to the version you use.
Who it fits
- You want 600+ pre-built integrations with built-in OAuth and secrets management, so you do not write a client per service.
- You want dynamic tool discovery so tool definitions stay out of the context window.
- You want to use it as an MCP server or through Python and TypeScript SDKs, with no framework lock-in.
- You want a single MCP server to install: the MCP server lives in a separate repository, and self-hosting runs a backend plus a portal.
- You do not want user credentials and tool calls to pass through a third party: that is how the managed service works.
- You need a very actively developed project: our data shows the last push on 2026-05-28.
How it differs
vs open-connector★ 6.1kACI lists 600+ integrations with dynamic discovery. OpenConnector lists 1,000+ providers and puts emphasis on keeping credentials out of the agent process.
Compatibility
Quick start
Use cases
Alternatives
Featured in these lists
Comments
No comments yet. Be the first!