1. Conduid
  2. Developer Tools
  3. Aci
MCP server · Developer Tools

Aci

Enable AI agents to interact with web and desktop software through ACI, an open protocol for structured, agent-ready app access

86Excellent

Scored 6 hours ago · breakdown

About Aci

Aci is an MCP server published by aipotheosis-labs in the Developer Tools category: enable AI agents to interact with web and desktop software through ACI, an open protocol for structured, agent-ready app access. It has been installed 0 times through Conduid.

The repository has 4.7K stars and 458 forks, with the last commit 8 months ago. Six months or more without a commit doesn't mean the server is broken, but check the open issues (0) before depending on it in production.

Install

Install
npx aci

This server has no ConduID identity, so agent calls to it are not receipted. Pin the version you install and review the source before granting it credentials.

Ask AI

Ask AI about Aci

Powered by Claude · Grounded in docs

I know everything about Aci. Ask me about installation, configuration, usage, or troubleshooting.

Security checks

  • ·README presentNot checked yet.
  • ·License declaredNot checked yet.
  • ·Tests presentNot checked yet.
  • ·Dependencies pinnedNot checked yet.
  • ·No dynamic code executionNot checked yet.
  • !Scoped permissionsDoesn't declare a permission scope. Assume it can do anything its process can.

Releases

v0.0.1-beta.3v0.0.1-beta.3
v0.0.1-beta.2v0.0.1-beta.2
v0.0.1-beta.1v0.0.1-beta.1

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

📺 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

README mirrored from the source repository 6 hours ago. The original is authoritative.

Questions

About Aci

How do I install Aci?

Run npx aci, then add the server to your MCP client's configuration. Conduid has recorded 0 installs, so the command is known to work with current clients.

Is Aci safe to use with an AI agent?

Its trust score is 86 out of 100 (excellent). It passes 0 of 1 static security checks; the failures are listed above. It has no ConduID identity yet, so agent calls to it are not receipted.

Is Aci still maintained?

The last commit was 8 months ago, with 0 open issues. That's long enough that you should check whether the maintainer is responding to issues before depending on it.