AI Agent & MCP Integration Compatibility
Compatibility details for Claude Code, Codex, Cursor, Cline, custom MCP clients, HTTP MCP servers and local stdio tools protected by AgentGate.
Current product capability · updated September 2026
Available means the protocol path is implemented and exercised by the AgentGate evaluation suite. Compatiblemeans the named client or server category can use that path, while its schema, authentication, side effects and release-specific behavior still need validation in your environment. These labels do not imply a vendor partnership or certification.
The gateway handles MCP JSON-RPC initialize, tools/listand tools/call. The supplied evaluation suite verifies the HTTP fixture and compiled Local Connector flow across discovery, allowed calls, denied calls, approval and replay protection.
AI coding agents
| Client, server or protocol | Status | Technical basis |
|---|---|---|
| Claude Code | Compatible | HTTP MCP configuration; validate initialization and tool calls with the client release used by your team. |
| Cursor | Compatible | HTTP MCP configuration and local process entry; validate the installed client release. |
| Codex | Compatible | HTTP bearer-token environment configuration or local process entry; validate the installed client release. |
| Cline | Compatible | Uses the available HTTP or stdio paths; confirm the upstream schema and session model. |
| Custom MCP client | Available | JSON-RPC initialize, tools/list and tools/call gateway endpoints are implemented. |
MCP server categories
| Client, server or protocol | Status | Technical basis |
|---|---|---|
| GitHub and source control | Compatible | HTTP tools and repository capability inference; not a vendor-certified connector. |
| Postgres / SQL | Compatible | Database capability inference; production writes are denied by the default pack. |
| Filesystem / shell | Compatible | Local Connector command mode; long-lived process sessions are outside this mode. |
| Deploy pipeline (CI/CD) | Compatible | HTTP MCP tools with reviewed deployment capability mapping. |
| SaaS APIs, payments and CRM | Compatible | Generic HTTP MCP transport; credentials, schemas and side effects remain server-specific. |
| Browser automation | Compatible | HTTP or local command mode; persistent sessions require compatible upstream behavior. |
Transport protocols
| Client, server or protocol | Status | Technical basis |
|---|---|---|
| HTTP / Streamable HTTP requests | Available | Gateway JSON-RPC requests and upstream tool routing are implemented. |
| stdio via Local Connector | Available with limits | One upstream process per request; source binary available. Long-lived stdio supervision is not included. |
Validate your installed versions
Run the protected MCP quickstart with a disposable fixture before routing a sensitive upstream. Confirm discovery, policy decisions, approvals, audit export and fail-closed behavior with the exact agent and MCP server releases your team operates.