Aci MCP

This project provides two types of MCP servers for accessing functional tools managed by ACI.dev: the apps-server provides access to tools for specified applications, and the unified-server provides functions for discovering and executing all available tools.

Developer tools Artificial intelligence chatbots #MCP Server #Tool Integration #Function Access .Python

rating : 2.5 points

downloads : 37

update time : 2025-04-29

What is the MCP server?

The MCP (Model Context Protocol) server is a tool for extending and managing the model context protocol, supporting multiple application scenarios.

Why choose the MCP server?

By using the MCP server, you can easily integrate, manage, and extend model functions, improving development efficiency.

How to get started?

Simply configure according to the steps in the documentation to quickly start your MCP server instance.

ACI.dev MCP Server

Apps-Specific ServerProvides direct access to specified application functions.

Unified ServerProvides you with meta-functions for discovering and executing all available tools on the platform.

Install Dependencies

Configure the Server

Start the Service

What is the difference between the two server types?

How can I get my API key?

Can I run both servers simultaneously?

ACI.dev Documentation

Complete documentation and MCP server tutorials.

MCP Detection Tool

A tool for detecting the model context protocol.

🚀 Guide to Developing MCP Servers with ACI.dev

This guide offers a concise overview of developing MCP servers using ACI.dev. For comprehensive documentation and tutorials, please visit the ACI.dev official documentation.

🚀 Quick Start

Overview

This package provides two Model Context Protocol (MCP) servers for accessing features (tools) managed by ACI.dev:

aci-mcp-apps: An MCP server that provides direct access to features in specified applications.
aci-mcp-unified: An MCP server that offers two meta - features (tools) (ACI_SEARCH_FUNCTIONS and ACI_EXECUTE_FUNCTION) to discover and execute all features (tools) available on ACI.dev.

⚠️ Important Note

For detailed descriptions and tutorials of the two MCP servers, please visit the ACI.dev official documentation.

Running the MCP Server Locally

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

# If uv is not installed, install it first
curl -sSf https://install.pypa.io/get-pip.py | python3 -
pip install uv

$ uvx aci-mcp --help
Usage: aci-mcp [OPTIONS] COMMAND [ARGS]...

  The main entry point of the package.

Options:
  --help  Show this message and exit.

Commands:
  apps-server     Start an apps-specific MCP server for accessing tools...
  unified-server  Start a unified MCP server with unlimited feature access.

Integrating with MCP Clients

Refer to the Unified MCP Server and Apps MCP Server sections to learn how to integrate 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 "BRAVE_SEARCH,GMAIL" --linked-account-owner-id <LINKED_ACCOUNT_OWNER_ID>

Debugging

You can use the MCP inspection tool to debug the server:

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

# For the 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 display server logs, which may help troubleshoot issues.