FastMCP FastMCP
Sign In
A

Ambient Code Platform MCP Server

Delegates expensive or long-running AI tasks to Kubernetes-hosted Claude agents running on OpenShift...

27 views
0 installs
Updated Feb 20, 2026
Not audited
Cloud Platforms Developer Tools
Tools I Recommend
ClaudeKit ClaudeKit Sponsor
Delegates expensive or long-running AI tasks to Kubernetes-hosted Claude agents running on OpenShift. Enables creating, managing, and monitoring remote agentic sessions for complex work like codebase analysis and security audits.

  1. Open the FastMCP connection dialog

    • Click the "Install Now" / connection button for the MCP and open the FastMCP connection interface where you can add environment variables (ENV key/value pairs).

  2. Add the required bearer token ENV

    • In the FastMCP interface add an ENV with key ACP_TOKEN.
    • For the value, paste your ACP Bearer token (example value: ya29.xxx... or eyJhbGci...).
    • Note: this token is required for the MCP to authenticate to the ACP public-api gateway.

  3. (Optional) Add cluster-config path ENV if you use a local clusters.yaml

    • If you prefer configuring clusters via a local file, add an ENV with key ACP_CLUSTER_CONFIG and value set to the absolute path to the clusters.yaml on the MCP host (example: /home/ubuntu/.config/acp/clusters.yaml).
    • If you do this, the MCP will read cluster endpoints and per-cluster tokens from that file instead of the single ACP_TOKEN env.

  4. Create the clusters.yaml file (if using file-based config)

    • On the MCP host create ~/.config/acp/clusters.yaml with contents like: 
      clusters:
  my-cluster:
    server: https://public-api-ambient.apps.your-cluster.example.com
    token: your-bearer-token-here
    default_project: my-workspace
default_cluster: my-cluster
    • Replace server, token, default_project, and default_cluster with your cluster values.

  5. Secure the clusters.yaml file

    • Set strict permissions so the file is readable only by the MCP user:
      • chmod 700 ~/.config/acp
      • chmod 600 ~/.config/acp/clusters.yaml

  6. How to obtain the Bearer token

    • Primary option: Request the token from your ACP platform administrator (they can create/provide a bearer token).
    • If you have access to the ACP gateway’s auth UI or endpoint, create or mint a token there (name it clearly, copy it immediately — tokens are often shown only once).
    • If your org uses an automated identity system, follow the org’s process to generate a gateway bearer token and then copy it.

  7. Paste the token into FastMCP and save

    • After obtaining the token, paste it into the ACP_TOKEN ENV value in the FastMCP interface (or ensure the ACP_CLUSTER_CONFIG path points to a clusters.yaml containing the token).
    • Save/apply the connection settings in the FastMCP dialog.

  8. Restart the MCP client (if required)

    • Some MCP clients require a full restart for env changes to take effect. Quit and restart the client/service that runs the MCP server.

  9. Verify the connection

    • Use the MCP tool acp_whoami or send a simple MCP request like “List my ACP sessions” to verify authentication and cluster access.
    • If you see authentication errors (401/403), confirm the token is correct and not expired, or verify the clusters.yaml content and file permissions.

  10. If you need more details

    • If your admin requires a specific gateway URL or token creation steps, follow your organization’s ACP gateway documentation or ask the ACP platform administrator for the exact token creation URL and permissions required.

Quick Start

View on GitHub

More for Cloud Platforms

View All →

More for Developer Tools

View All →

Similar MCP Servers

Report Issue

Thank you! Your issue report has been submitted successfully.