ACI MCP Servers

Content

ACI MCP Servers provide MCP access to ACI.dev managed functions. The package offers a unified server with search-and-execute meta tools and an app-specific server for exposing functions from selected apps.

This entry points at the open-source aipotheosis-labs/aci-mcp package rather than the broader ACI.dev platform repository. The upstream README describes two server modes: aci-mcp-unified for searching and executing available functions, and aci-mcp-apps for direct access to functions from explicitly selected apps.

Source Review

• https://github.com/aipotheosis-labs/aci-mcp
• https://github.com/aipotheosis-labs/aci
• https://www.aci.dev/docs/mcp-servers/introduction
• https://www.aci.dev/docs/mcp-servers/unified-server
• https://www.aci.dev/docs/mcp-servers/apps-server
• https://pypi.org/project/aci-mcp/

These sources were reviewed on 2026-06-05. Prefer the live ACI.dev docs for current API key, linked account owner, app selection, client configuration, and deployment behavior.

Features

• Unified MCP server with search and execution tools for ACI.dev functions.
• App-specific MCP server for exposing selected app functions directly.
• PyPI package runnable with uvx.
• Docker usage documented by the upstream project.
• ACI.dev-managed authentication, linked accounts, app integrations, and function execution.
• Documentation for unified and app-specific MCP client integration.

Installation

For the unified server:

{
  "mcpServers": {
    "aci": {
      "command": "uvx",
      "args": [
        "aci-mcp",
        "unified-server",
        "--linked-account-owner-id",
        "YOUR_LINKED_ACCOUNT_OWNER_ID"
      ],
      "env": {
        "ACI_API_KEY": "YOUR_ACI_API_KEY"
      }
    }
  }
}

For narrower access, use the upstream apps-server mode and pass only the apps needed for the workflow.

Use Cases

• Give Claude one MCP connection for many ACI.dev-managed integrations.
• Use the unified server to discover relevant functions during exploratory workflows.
• Use the app-specific server for safer, narrower access to approved apps.
• Prototype assistants that need calendars, email, search, CRM, ticketing, or developer-platform tools behind a common MCP interface.
• Compare unified tool discovery with explicit function allowlisting before production use.

Safety and Privacy

ACI MCP Servers can expose high-impact third-party actions through one MCP connection. Prefer the smallest useful app set, review linked account scopes, and require human approval for write, send, deployment, billing, admin, or destructive operations.

Treat ACI API keys, linked account IDs, prompts, function arguments, execution results, OAuth data, logs, and connected-service records as sensitive. Review ACI.dev account controls and connected app permissions before using the server with production or customer data.

Duplicate Check

No aipotheosis-labs/aci-mcp entry or source URL was found in content/mcp. This is distinct from individual app MCP servers because it focuses on ACI.dev's unified and app-specific function gateway rather than one service-specific API.

Disclosure

Editorial listing. No paid placement or affiliate link is used. The MCP package is open source, but the workflow depends on an ACI.dev account and managed function infrastructure.

• Source repositorygithub.com 2026-07-20T21:02:10-07:00
• Documentationaci.dev
• Websiteaci.dev
• Submitted by oktofeesh12026-06-05