This release is a pre-release and may not be stable for production use.
MCP servers powered by ACI.dev
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 appsaci-mcp-unified: An MCP server that provides two meta functions (tools) (ACI_SEARCH_FUNCTIONSandACI_EXECUTE_FUNCTION) to discover and execute ALL functions (tools) available on ACI.dev
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.
Metadata
Release files for iflow-mcp_aipotheosis-labs-aci-mcp 1.0.0b13
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| iflow_mcp_aipotheosis_labs_aci_mcp-1.0.0b13.tar.gz | 597.7 kB | Without provenance | Details for iflow_mcp_aipotheosis_labs_aci_mcp-1.0.0b13.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| iflow_mcp_aipotheosis_labs_aci_mcp-1.0.0b13-py3-none-any.whl | Python 3 | none | any | Details for iflow_mcp_aipotheosis_labs_aci_mcp-1.0.0b13-py3-none-any.whl |
Total release size: 611.4 kB
Release files / iflow_mcp_aipotheosis_labs_aci_mcp-1.0.0b13.tar.gz
| Download URL | iflow_mcp_aipotheosis_labs_aci_mcp-1.0.0b13.tar.gz |
|---|---|
| Size | 597.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6daa66c4d95d4bb88ff4b2bd3776a92c80951f3aa28ef1336049810e54339957
|
|
BLAKE2b-256 checksum How to use checksums |
481a53b067e4e898d261ac2d9dec8ce669f5b173be807e9817a20fac6f651dba
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.10.0 {"installer":{"name":"uv","version":"0.10.0","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Debian GNU/Linux","version":"13","id":"trixie","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Release files / iflow_mcp_aipotheosis_labs_aci_mcp-1.0.0b13-py3-none-any.whl
| Download URL | iflow_mcp_aipotheosis_labs_aci_mcp-1.0.0b13-py3-none-any.whl |
|---|---|
| Size | 13.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
7e82bf6d89eee58180173f01c3173bfc95a59c98eeb4b1f08f2de57af0443571
|
|
BLAKE2b-256 checksum How to use checksums |
712a6a0ee1f2a7ccd7fd1c3e6a8c454b5daa21852bcff5f9adea0d9eeffff415
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.10.0 {"installer":{"name":"uv","version":"0.10.0","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Debian GNU/Linux","version":"13","id":"trixie","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Security for iflow-mcp_aipotheosis-labs-aci-mcp 1.0.0b13
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.