返回 MCP 目录
public公开dns本地运行

ACI MCP服务器

ACI.dev 是一个开源基础设施平台,旨在为 AI 代理提供统一的多租户认证、细粒度权限和动态工具发现功能。通过其 **统一模型-上下文-协议(MCP)服务器** 和轻量级 Python SDK,开发者可以轻松访问 600 多种预建集成,如 Google Calendar 和 Slack,而无需单独处理 OAuth 流程和 API 客户端。ACI.dev 支持多租户认证、自然语言权限边界和动态工具发现,确保代理的可靠性和灵活性。它适用于任何 LLM 框架,帮助开发者快速构建生产就绪的 AI 代理,广泛应用于个人助理、研究代理、外呼销售代理和客户支持代理等场景。

article

README

ACI.dev Logo

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

aipotheosis-labs%2Faci | Trendshift

Documentation PyPI version License Discord Twitter Follow

[!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!

GitHub Stars

📺 Demo Video

ACI.dev Unified MCP Server Demo

ACI.dev Unified MCP Server Demo

ACI.dev VibeOps Demo

ACI.dev VibeOps Demo

✨ Key Features

  • 600+ Pre-built Integrations: Connect to popular services and apps in minutes.
  • Flexible Access Methods: Use our unified MCP server or our lightweight SDK for direct function calling.
  • Multi-tenant Authentication: Built-in OAuth flows and secrets management for both developers and end-users.
  • Enhanced Agent Reliability: Natural language permission boundaries and dynamic tool discovery.
  • Framework & Model Agnostic: Works with any LLM framework and agent architecture.
  • 100% Open Source: Everything released under Apache 2.0 (backend, dev portal, integrations).

💡 Why Use ACI.dev?

ACI.dev improves tool-calling reliability and accountability:

  • Authentication at Scale: Connect multiple users to multiple services securely.
  • Discovery Without Overload: Find and use the right tools without overwhelming LLM context windows.
  • Natural Language Permissions: Control agent capabilities with human-readable boundaries.
  • Tool-use Logging: See how your agent called tools and the issues it ran into.
  • Build Once, Run Anywhere: No vendor lock-in with our open source, framework-agnostic approach.

🧰 Common Use Cases

  • VibeOps: Automate devOps by letting your agentic IDE access Vercel, Supabase, Cloudflare, Sentry and more to ship live products.
  • Personal Assistant Chatbots: Build chatbots that can search the web, manage calendars, send emails, interact with SaaS tools, etc.
  • Research Agent: Conducts research on specific topics and syncs results to other apps (e.g., Notion, Google Sheets).
  • Outbound Sales Agent: Automates lead generation, email outreach, and CRM updates.
  • Customer Support Agent: Provides answers, manages tickets, and performs actions based on customer queries.

🔗 Quick Links

💻 Getting Started: Local Development

To run the full ACI.dev platform (backend server and frontend portal) locally, follow the individual README files for each component:

👋 Contributing

We welcome contributions! Please see our CONTRIBUTING.md for more information.

Integration Requests

Missing any integrations (apps or functions) you need? Please see our Integration Request Template and submit an integration request! Or, if you're feeling adventurous, you can submit a PR to add the integration yourself!

Star History

Star History Chart

help

运行方式说明

cloud

托管运行

托管运行通常表示这个 MCP Server 由服务方环境承载,用户一般按页面提供的连接方式或授权流程接入,不需要在本地长期启动一个 MCP 进程

  1. 打开服务方连接页
  2. 完成授权或复制端点
  3. 在 MCP 客户端中连接
terminal

本地运行 / 其它方式

本地运行通常需要用户在自己的电脑或服务器上安装依赖,把 server_config 复制到 MCP 客户端,并按 env_schema 补齐环境变量、密钥或其它配置

  1. 复制 server_config
  2. 安装所需依赖
  3. 补齐环境变量后重启客户端