Happy slice of mcp pizzaMCP.pizza

aci-mcp

MCP.Pizza Chef: aipotheosis-labs

Rather than installing a separate helper for every service, you create an account with ACI.dev, connect the services you use there, and this single add-on hands them all to your assistant. Two versions ship: one limited to the apps you name — the documentation's own example pairs Gmail with Brave Search — and one that searches the whole catalogue on demand and runs whatever it finds. A key from ACI.dev is required. Both the code and its published package have sat unchanged since August 2025 and are still labelled beta.

Unmaintained · no code changes since August 2025; package still labelled beta
Email
Other
Web/Research

Use This MCP server To

Set up many apps at once instead of one at a time Search the web through an account I have already linked Work with a linked mailbox without a separate mail add-on Let my assistant find the right tool without me naming it Keep logins in one place rather than in every settings file

README

MCP servers powered by ACI.dev

Important

This README only covers basic development guide. For full documentation and tutorials on ACI.dev MCP servers please visit aci.dev docs.

Table of Contents

Overview

This package provides three Model Context Protocol (MCP) servers for accessing ACI.dev managed functions (tools):

  • aci-mcp-apps: An MCP server that provides direct access to functions (tools) from specified apps Apps Server
  • aci-mcp-unified: An MCP server that provides two meta functions (tools) (ACI_SEARCH_FUNCTIONS and ACI_EXECUTE_FUNCTION) to discover and execute ALL functions (tools) available on ACI.dev Unified Server

Important

For detailed explanation and tutorials on the MCP servers please visit aci.dev docs.

Run MCP Servers Locally

The package is published to PyPI, so you can run it directly using uvx:

# Install uv if you don't have it already
curl -sSf https://install.pypa.io/get-pip.py | python3 -
pip install uv
$ uvx aci-mcp --help
Usage: aci-mcp [OPTIONS] COMMAND [ARGS]...

  Main entry point for the package.

Options:
  --help  Show this message and exit.

Commands:
  apps-server     Start the apps-specific MCP server to access tools...
  unified-server  Start the unified MCP server with unlimited tool access.

Integration with MCP Clients

See the Unified MCP Server and Apps MCP Server sections for more information on how to configure the MCP servers with different MCP clients.

Docker

# Build the image
docker build -t aci-mcp .

# Run the unified server
docker run --rm -i -e ACI_API_KEY=<ACI_API_KEY> aci-mcp unified-server --linked-account-owner-id <LINKED_ACCOUNT_OWNER_ID>

# Run the apps server
docker run --rm -i -e ACI_API_KEY=<ACI_API_KEY> aci-mcp apps-server --apps <APP1,APP2,...> --linked-account-owner-id <LINKED_ACCOUNT_OWNER_ID>

Debugging

You can use the MCP inspector to debug the server:

# For unified server
npx @modelcontextprotocol/inspector uvx aci-mcp unified-server --linked-account-owner-id <LINKED_ACCOUNT_OWNER_ID>

# For apps server
npx @modelcontextprotocol/inspector uvx aci-mcp apps-server --apps "BRAVE_SEARCH,GMAIL" --linked-account-owner-id <LINKED_ACCOUNT_OWNER_ID>

Running tail -n 20 -f ~/Library/Logs/Claude/mcp*.log will show the logs from the server and may help you debug any issues.

aci-mcp FAQ

Is this still being maintained?
Not visibly. The code has not changed since August 2025 and the installable package is a beta from the same day. The ACI.dev service behind it is run separately, so things may still work, but this connector is not getting fixes.
Do I need an account or a key?
Yes to both. You sign up at ACI.dev, link each service you want through them, and paste a key into your settings. That account setup, not the add-on, is where the real work is.
The write-up mentions three servers — how many are there really?
Two. The introduction says three, but only the apps version and the unified version exist, which is also all the built-in help lists.
Can I use this to search the web or handle email?
Yes, provided you connect those services on ACI.dev first. Nothing works until an account is linked on their side; the add-on only passes requests along.
How hard is the setup?
Hard enough to want a technical friend. It is started from a command line or a container, with your key and account identifier handed over as options, and the account linking happens on a separate website.
Which apps does it work in?
Any assistant that supports MCP. The project's own debugging notes assume Claude Desktop, and its maker's site covers other clients.