aci MCP Server

Use This MCP server To

Let my coding assistant deploy a site to Vercel Check my calendar and post a Slack update in one go Research a topic and save the notes into Notion Draft outreach emails and log each one in my CRM Give one assistant many apps without separate logins each time

README

ACI: Open-Source Infra to Power Unified MCP Servers and VibeOps

Note

This repo is for the ACI.dev platform. If you're looking for the Unified MCP server built with ACI.dev, see aci-mcp.

ACI.dev is the open-source tool-calling platform that hooks up 600+ tools into any agentic IDE or custom AI agent. It gives agents intent-aware access to tools with multi-tenant auth, granular permissions, and dynamic tool discovery—exposed as either direct function calls or through a Unified Model-Context-Protocol (MCP) server.

Examples: Instead of writing separate OAuth flows and API clients for Google Calendar, Slack, and more, use ACI.dev to manage authentication and provide AI agents with unified, secure function calls. Access these capabilities through our Unified MCP server or via our lightweight Python SDK, compatible with any LLM framework.

Supercharge vibe coding and automate devOps by adding a single unified MCP server to your favourite agentic IDE. Configure the MCP with Vercel, Supabase, Cloudflare, and other platforms. Let AI handle provisioning, deployment, database configs, and debugging to turn a vibe coded prototype into a live product.

ACI.dev Architecture

Join us on Discord to help shape the future of Open Source AI Infrastructure and VibeOps.

🌟 Star ACI.dev to stay updated on new releases!

aci FAQ

Which apps can it reach?

More than 600, including Google Calendar, Slack, Notion, Vercel, Supabase and Cloudflare.

Do I have to sign in to every app separately?

You connect each account once through ACI, and it handles the sign-in for your assistant from then on.

Can I use this to let my coding tool set up a database?

Yes, that is one of its main uses, with Supabase, Vercel and Cloudflare among the supported services.

Can I limit what the assistant is allowed to do?

Yes, permissions are written in plain language per tool, and every action the assistant takes is logged.

Does it work with assistants other than Claude?

Yes, it is model- and framework-agnostic and works with any MCP-compatible tool or custom agent.

How hard is it to set up?

Running the platform yourself needs a developer to start the backend and portal; the hosted version at aci.dev is much quicker.

Is the code open?

Yes, the backend, developer portal and integrations are all released under Apache 2.0.