A

AIPo Labs

Allow dynamic search and execute any tools available on ACI.dev.

9 views
0 installs
Updated Jan 5, 2026
Not audited
Allow dynamic search and execute any tools available on ACI.dev.
  1. Create or sign in to your ACI.dev account

    • Go to the ACI.dev platform and sign in (or create a project if you don’t have one). (aci.dev)
  2. Open the Project Settings

    • From your project dashboard, open the Project Settings / Manage Project area where agents and apps are configured. (aci.dev)
  3. Create or select an Agent

    • If you don’t already have an agent, create one inside the project. Agents are assigned API keys that the MCP servers use. (aci.dev)
  4. Enable the apps your agent needs (Allowed Apps)

    • In Project Settings / Agent settings, add or toggle the apps you want the MCP server to access (Allowed Apps). This ensures the API key will be permitted to use those integrations. (aci.dev)
  5. Copy the ACI API key

    • In the agent or project settings locate the API key (ACI_API_KEY) for that agent and copy it to your clipboard. (aci.dev)
  6. (Optional) Note the linked-account-owner-id

    • If your MCP server commands require a linked account owner id (used to execute functions on behalf of a user), copy that ID from the project or OAuth flow steps—you may store it as LINKED_ACCOUNT_OWNER_ID. (aci.dev)
  7. Open the FastMCP connection interface and click “Install Now”

    • Start the FastMCP “Install Now” flow for adding this MCP server.
  8. Fill the FastMCP environment fields

    • Paste the API key value into the environment variable named ACI_API_KEY.
    • If you captured a linked account owner id and want it as an env, add LINKED_ACCOUNT_OWNER_ID (or supply it in the server args as required).
    • Make sure the variable names match exactly: ACI_API_KEY (and LINKED_ACCOUNT_OWNER_ID if used). (aci.dev)
  9. Save and complete the Install Now flow

    • Confirm and save the environment variables in FastMCP, finishing the installation.
  10. Verify the MCP server connectivity

    • Restart or re-register the MCP server in your client (or restart Claude Desktop / your MCP client) and, if available, run the MCP inspector or check logs to confirm the server authenticates using the ACI_API_KEY. (aci.dev)
  11. Secure the key

    • Keep the ACI_API_KEY secret (store in your secrets manager or FastMCP secret field) and rotate it via ACI.dev project settings if it is ever exposed. (aci.dev)

Quick Start

More for API Development

View All →

More for Developer Tools

View All →

Report Issue

Thank you! Your issue report has been submitted successfully.