What are MCP Integrations?
MCP (Model Context Protocol) is a standardized protocol that allows external services to automatically expose tools to AI systems. Instead of manually creating each tool like with HTTP, MCP integrations sync with a server and obtain all available tools automatically. It’s like connecting a plugin: the MCP server tells the agent what tools it offers, what parameters they need, and how to call them. You can learn more about MCP in the official protocol documentation.MCP Available in Diga
Diga accepts MCP servers via HTTP with streaming. We support two communication methods:Streamable HTTP (/mcp)
If your MCP server exposes an endpoint that ends in /mcp, Diga will use MCP’s native streamable HTTP protocol. This is the recommended method for new implementations.
Example: https://your-server.com/mcp
Server-Sent Events (SSE)
If your endpoint doesn’t end in/mcp, Diga will use Server-Sent Events (SSE) for bidirectional communication with the MCP server.
Both methods support the same set of MCP capabilities. The protocol choice is automatic based on the URL you provide.
Create an MCP Integration
1
Access Integrations
From the dashboard, go to the Integrations section and click New Integration.Select the MCP type.
2
Configure the MCP Server
Provide the connection details to the server:Name: Identifies your integration (e.g., “Salesforce MCP”, “HubSpot MCP”)Server URL: MCP server endpointCredentials: Depending on the server, it may require:
- Bearer Token
- Custom Headers
- No authentication
3
Test the Connection
Click Test Connection to verify you can communicate with the MCP server.If it fails:
- Verify the server URL is correct
- Confirm the credentials are active
- Make sure the MCP server is online and accessible
4
Sync Tools
Once connected, Diga automatically:
- Discovers what tools the server offers
- Reads their descriptions and parameters
- Displays them in your tools list
Tools are automatically synced when you list the tools or assign the integration to an agent.
5
Review and Filter Tools
Review the available tools.You can:
- View description: Understand what each tool does
- View parameters: Review what information it needs
- Configure confirmation: Require user approval for sensitive tools
6
Save the Integration
Once configured, save the integration.The synced tools are ready to be assigned to agents.
Manage Synced Tools
Unlike HTTP where you create tools manually, with MCP the tools come from the server. However, you can manage them:Configure User Confirmation
Although the tool comes from the MCP server, you can add a confirmation layer:1
Select the tool
In the list of synced tools, find the one that needs confirmation.
2
Enable confirmation
Check Requires User Confirmation.
3
Behavior
Now, when the agent tries to use this tool:
- It will explain to the user what it will do
- It will ask for explicit confirmation
- It will only execute if the user accepts
