home / mcp / ambient code mcp server

Ambient Code MCP Server

Offload AI tasks to a Kubernetes-based Claude cluster via agentic sessions, enabling scalable analysis workflows.

Installation

Add the following to your MCP client configuration file.

Configuration

{
  "mcpServers": {
    "jeremyeder-mcp": {
      "command": "bun",
      "args": [
        "run",
        "/path/to/mcp/src/index.ts"
      ],
      "env": {
        "ACP_BASE_URL": "https://ambient-code.apps.rosa.vteam-stage.7fpc.p3.openshiftapps.com"
      }
    }
  }
}

Ambient Code Platform MCP Server lets you delegate expensive or long-running AI tasks to a Kubernetes-hosted Claude agent cluster. It enables session-based workflows where you create a session, poll status, fetch results, and stop the session to free resources, making complex code analysis and other AI tasks practical and scalable.

How to use

You interact with the MCP server through a client that talks to the Ambient Code Platform API. Start by ensuring you are authenticated to your OpenShift cluster, then list projects, create a new agentic session with a clear prompt, and control the session as it runs. Your client will automatically route actions like checking status, fetching events, and stopping the session to the MCP server.

Typical workflow you can perform:

How to install

Prerequisites you need before installing and running the MCP server client:

- Node.js or Bun installed on your workstation (the server example uses Bun to run the MCP client entry point).

- Access to your OpenShift cluster and the ability to run OpenShift commands.

Follow these concrete steps to set up and run the MCP client side that communicates with Ambient Code Platform.

1. Clone the project repository and navigate into it.

2. Install dependencies with Bun.

git clone https://github.com/jeremyeder/mcp.git
cd mcp
bun install

Configure and run the MCP server client locally

Configure your environment so the client can reach Ambient Code Platform and run the MCP entry point. You need to provide the API URL for the Ambient Code Platform and the command to start the local MCP client.

Use the following example configuration to connect a local setup or Claude Desktop to the MCP server.

{
  "mcp": {
    "ambient_code": {
      "type": "local",
      "command": ["bun", "run", "/path/to/mcp/src/index.ts"],
      "environment": {
        "ACP_BASE_URL": "https://ambient-code.apps.rosa.vteam-stage.7fpc.p3.openshiftapps.com"
      }
    }
  }
}

Additional setup for Claude Desktop

If you are using Claude Desktop, place a similar configuration in your Claude desktop config to connect to Ambient Code Platform.

{
  "mcpServers": {
    "ambient-code": {
      "command": "bun",
      "args": ["run", "/path/to/mcp/src/index.ts"],
      "env": {
        "ACP_BASE_URL": "https://ambient-code.apps.rosa.vteam-stage.7fpc.p3.openshiftapps.com"
      }
    }
  }
}

Notes on authentication and usage

The MCP server relies on your OpenShift token to access resources. You must be logged in to OpenShift with a valid session. Tokens may expire, so re-authenticate if you encounter authentication errors. The server transmits the token via Authorization: Bearer and X-Forwarded-Access-Token headers.

Troubleshooting

If you run into issues starting sessions or accessing projects, verify that your ACP_BASE_URL is correct and that your OpenShift login is active. Check that the local MCP client process is running and reachable at the configured endpoint.

Available tools

acp_whoami

Check OpenShift authentication status for the current user.

acp_list_projects

List available OpenShift projects or namespaces you can access.

acp_list_sessions

List agentic sessions within a project.

acp_get_session

Retrieve details and status for a specific session.

acp_get_events

Get a status snapshot of a running or completed session.

acp_create_session

Create a new agentic session with a specified prompt.

acp_send_message

Send a follow-up message to an active session.

acp_stop_session

Stop a running session to free resources.