by aipotheosis-labs
AIPo Labs — dynamic search and execute any tools available on ACI.dev for fast, flexible AI-powered workflows.
Connects MCP clients to the ACI.dev platform to search and execute any of the available tools/functions. Provides both direct app access and unified discovery across all ACI.dev functions.
AIPo Labs is a community-built MCP server published by aipotheosis-labs that provides AI assistants with tools and capabilities via the Model Context Protocol. AIPo Labs — dynamic search and execute any tools available on ACI.dev for fast, flexible AI-powered workflows. It is categorized under developer tools.
You can install AIPo Labs in your AI client of choice. Use the install panel on this page to get one-click setup for Cursor, Claude Desktop, VS Code, and other MCP-compatible clients. This server runs locally on your machine via the stdio transport.
MIT
AIPo Labs is released under the MIT license. This is a permissive open-source license, meaning you can freely use, modify, and distribute the software.
Add new capabilities to Claude beyond text generation
Example
Access external data sources, execute code, interact with tools and services
Transform Claude from chatbot to action-taking agent
Provide Claude with access to relevant context and data
Example
Load project documentation, access knowledge bases, query databases
Get more accurate, context-aware responses
Automate multi-step workflows combining AI and external tools
Example
Research → Summarize → Create document → Send notification
Complete complex tasks end-to-end without manual steps
Share your MCP server with the developer community
AIPo Labs is among the better-indexed MCP projects we tried; the explainx.ai summary tracks the official description.
According to our notes, AIPo Labs benefits from clear Model Context Protocol framing — fewer ambiguous “AI plugin” claims.
AIPo Labs reduced integration guesswork — categories and install configs on the listing matched the upstream repo.
We wired AIPo Labs into a staging workspace; the listing’s GitHub and npm pointers saved time versus hunting across READMEs.
Useful MCP listing: AIPo Labs is the kind of server we cite when onboarding engineers to host + tool permissions.
AIPo Labs is a well-scoped MCP server in the explainx.ai directory — install snippets and categories matched our Claude Code setup.
Strong directory entry: AIPo Labs surfaces stars and publisher context so we could sanity-check maintenance before adopting.
AIPo Labs has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.
AIPo Labs is among the better-indexed MCP projects we tried; the explainx.ai summary tracks the official description.
I recommend AIPo Labs for teams standardizing on MCP; the explainx.ai page compares cleanly with sibling servers.
showing 1-10 of 31
[!IMPORTANT] This README only covers basic development guide. For full documentation and tutorials on ACI.dev MCP servers please visit aci.dev docs.
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
<img src="./assets/apps-mcp-server-diagram.svg" alt="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
<img src="./assets/unified-mcp-server-diagram.svg" alt="Unified Server">[!IMPORTANT] For detailed explanation and tutorials on the MCP servers please visit aci.dev docs.
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.
See the Unified MCP Server and Apps MCP Server sections for more information on how to configure the MCP servers with different MCP clients.
# 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>
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.
Prerequisites
Time Estimate
15-60 minutes depending on server complexity
Steps
Troubleshooting
✓ Do
✗ Don't
💡 Pro Tips
Architecture
Model Context Protocol standardizes how AI hosts (Claude, Cursor) communicate with external tools and data sources through server implementations.
Protocols
Compatibility
✓ Use when
Use when you need Claude to access external data, execute actions, or integrate with tools. Best for extending AI capabilities beyond conversation.
✗ Avoid when
Avoid when native integrations exist (use official APIs directly), for real-time critical systems, or when security/compliance requires zero external dependencies.