{"id":"aipotheosis-labs-aci-mcp","name":"aci-mcp","af_score":58.2,"security_score":56.2,"reliability_score":25.0,"what_it_does":"Provides two ways to run MCP (Model Context Protocol) servers that expose ACI.dev managed functions/tools to MCP clients: an apps-specific server that exposes tools from selected apps, and a unified server that can discover and execute tools across all available functions (via meta-tools).","best_when":"You want an MCP-compliant integration to ACI.dev tools and can supply an ACI API key plus linked account owner ID, optionally restricting apps via CLI flags.","avoid_when":"You need strict least-privilege at the tool/function level beyond what the apps-server restriction provides, or you cannot run a local MCP server process/container.","last_evaluated":"2026-03-30T13:35:41.558967+00:00","has_mcp":true,"has_api":false,"auth_methods":["ACI_API_KEY via environment variable (shown in Docker examples)","CLI options include --linked-account-owner-id (paired with ACI_API_KEY)"],"has_free_tier":false,"known_gotchas":["Unified server claims 'unlimited tool access' and includes tool discovery/execution meta-functions; an agent may enumerate/attempt many tools unless the MCP client/agent is constrained.","Apps server requires explicit app selection (--apps); ensure you pass correct app identifiers to avoid missing tools.","The README does not describe MCP-level error codes or retry/backoff guidance; agents may need to rely on MCP client behavior for retries."],"error_quality":0.0}