mcpField
M
MCP servers powered by

MCP servers powered by

Local
github.com/aipotheosis-labsAI & Agents253Updated 65w ago
Repository

About MCP servers powered by

MCP servers powered by ACI.dev is a package of MCP servers that expose ACI.dev managed functions as tools. It offers an apps server for specified applications and a unified server with two meta tools for discovering and executing any function.

Key features

  1. 01App-scoped function access through the apps server
  2. 02Unified server with search and execute meta tools
  3. 03Runs directly from PyPI with uvx
  4. 04Docker image for containerized runs
  5. 05Debugging with the MCP Inspector

Use cases

  1. 01Connecting an MCP client to tools from selected applications
  2. 02Discovering and executing any ACI.dev function through one server
  3. 03Running the MCP servers inside a container

MCP support

This project is a set of MCP servers that expose ACI.dev managed functions (tools) to MCP clients, through the aci-mcp-apps and aci-mcp-unified servers.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
  "mcpServers": {
    "aci": {
      "command": "uvx",
      "args": [
        "aci-mcp"
      ]
    }
  }
}
Run commanduvx aci-mcp

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
pypiaci-mcp

Tools

No tool list yet

Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.

Details

From the project 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.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.