Custom integrations
Connect an MCP server
Model Context Protocol (MCP) is the open standard for exposing tools to AI agents. If your team or vendor has an MCP server, Dezifi can register it as a tool source in minutes — no custom adapter code.
What you'll learn
- What MCP is and when to use it over REST or SQL
- How Dezifi discovers tools from an MCP server
- Which auth modes are supported
- How to register and test your MCP server
When to use MCP
Use MCP when the tool provider already ships an MCP server, or when you control the tool surface and want a standard protocol. MCP exposes tools, resources and prompts in a typed schema that any compliant agent can consume. If you only have a plain HTTP service, wrap it as a REST tool instead.
How Dezifi consumes an MCP server
- 1
Transport
Dezifi connects over HTTPS using the MCP streamable HTTP transport. WebSocket and stdio transports are not exposed to agents directly — wrap stdio servers behind an HTTP proxy. - 2
Capability discovery
On registration, Dezifi calls listTools, listResources and listPrompts. Every tool surfaces as a typed action in the agent builder, with parameters, descriptions and required/optional flags. - 3
Versioning
The MCP server's protocol version is captured at registration. Schema changes are detected on each re-sync — Dezifi flags breaking changes before they hit production agents. - 4
Auth
Three supported modes — API key in header, OAuth 2.1 with PKCE, or mutual TLS. Per-tenant credentials are stored encrypted; the agent never sees the secret.
How to register an MCP server
- 1
Open Integrations
Sidebar → Integrations → New → MCP Server. - 2
Provide the endpoint
Enter the HTTPS URL of your MCP server. Give it a workspace-unique name like "Internal Pricing MCP". - 3
Configure auth
Pick API key, OAuth or mTLS. Paste the credential or upload the client certificate. Test connection — Dezifi makes a handshake call and reports the protocol version. - 4
Review discovered tools
After handshake, Dezifi lists every tool, resource and prompt the server exposes. Tick the ones you want available to agents. The rest stay hidden. - 5
Attach to an agent
In the agent builder, the MCP server appears as a single tool source. Select the actions to grant. Test in the chat panel — every MCP tool call is visible in the trace.
Frequently asked questions
- Does Dezifi run my MCP server?
- No. You host the MCP server. Dezifi calls it as a client. This keeps your business logic and credentials inside your perimeter.
- Can a single MCP server be shared across workspaces?
- Yes if the server is multi-tenant aware. Use OAuth so each workspace authenticates with its own credentials. Otherwise register one connection per workspace.
- What happens when the MCP server adds a new tool?
- Run Re-sync on the integration. Dezifi calls listTools again and surfaces new actions as a diff. Approve which ones to enable for agents.
- Are MCP tool calls observable like first-party integrations?
- Yes. Every call appears in the run trace with the same fields — tool name, parameters, response, latency, error state. Guardrails apply to MCP outputs identically.