AIControl Docs

Platform & Framework Guide

A framework can use AIControl's gateway when its agent can send HTTP requests to a configurable base URL with a custom Authorization header, and can add the extra params fields that call_tool requires.

What this guide does and does not verify. The gateway's requirements below come from the AIControl code. Each framework entry is a statement about that framework's MCP client configuration that has not been tested against a live AIControl gateway; treat it as "expected to work" until you have tried it.

What the gateway requires of any client:

  • Base URL: http://your-aicontrol-host:8001/mcp/<server_id>, with two routes under it: POST /tools/list and POST /call_tool, each taking a JSON-RPC body.
  • Auth header: Authorization: Bearer <agent-scoped-token> (see Integration for how to issue one).
  • Extra params on call_tool: session_id (one UUID per agent run) and sequence_number (call order within the run). A call without them is denied as malformed and audited. A stock MCP client does not send these fields, so the client or a wrapper must add them. See Integration.

LangChain / LangGraph (Python)

Both ship MCP client support. Configure the MCP server entry with AIControl's gateway URL and the Authorization header above instead of your downstream server's real URL, and add session_id and sequence_number to each tool call.

CrewAI (Python)

Point CrewAI's MCP server configuration at the gateway URL with the Authorization header, and add the call_tool params above.

Google ADK

Point Google ADK's MCP toolset connection at the gateway URL with the Authorization header, and add the call_tool params above.

Anthropic Claude Agent SDK / OpenAI Agents SDK

Both accept MCP servers as a tool source. Point either at the gateway URL with the Authorization header, and add the call_tool params above.

Any other framework

If it can send a custom Authorization header to a configurable base URL and add session_id and sequence_number to call_tool params, it can reach an agent-scoped gateway endpoint. If it cannot set the header, it cannot authenticate to the gateway.

For the four named agent-platform integration points (Amazon Bedrock, Azure AI Foundry, Vertex AI / Gemini Enterprise, Microsoft Copilot Studio) — none of which are "just point an MCP client at a URL" in the same way — see Platform Discovery.