Skip to content
Integrations

Keep your stack. Choose your connection.

Configure native service calls through the Action Gateway or add supported SDK hooks inside your application. Both connect to shared identity and tenant policy.

Gateway-compatible native clients

Configure the connection. Keep your native client.

Use the assigned sidecar gateway for MCP, API, GraphQL and A2A calls. These examples use native framework clients; an AgenticDome SDK adapter is not required for the routed calls.

Docker Agent

Configure remote tools through the sidecar gateway and keep your existing MCP server. Add Docker’s mandatory native guard for local shell, file and tool proposals through deployment configuration.

Explore both Docker pathways →

CrewAI & LangGraph

Use compatible MCP clients or application HTTP calls through the gateway. Add SDK hooks when you also need internal tool checks and deeper framework context.

Compare SDK integrations →

Other compatible clients

Route supported MCP, API, GraphQL and A2A requests with the existing destination URL and verified caller identity. Security teams define permitted destinations once.

Read the connection guide →

Copy real gateway connection settings and framework examples from your signed-in Action Gateway workspace.

Published MCP schemas become runtime checks.

The updated sidecar validates tool-call arguments against the authenticated server’s published inputSchema before forwarding. Your client keeps its protocol messages; identity and action policy still decide which requests may proceed.

Discovery retains reported contract hashes and changes. Optional enforced pins in Tool & MCP Registry let security teams approve a sensitive tool’s input contract.

Explore MCP argument validation →

Get the SDK or runtime plugin.

Download the public packages directly, explore their source, and choose the installation extras for your framework.

Meet Abi

Your AI deployment concierge.

Describe your environment and what you want to protect. Abi helps compare Gateway, Docker native guard and SDK options, explain identity and MCP schema checks, and prepare a deployment blueprint for your team to review.

Explore Abi
17 SDK & native plugin integration paths

Connect inside the application.

Using Copilot Studio? Explore the external-provider integration.

Start with the workflow that matters.

Explore a local action-security example, plan your approach with Abi or bring your environment to a deployment review.