Skip to main content

​
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 connects to MCP servers over Streamable HTTP. Provide the server’s HTTP(S) URL (e.g. https://your-server.com/mcp). SSE-only servers are not currently supported.

​
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

Validate the connection

There’s no separate “Test Connection” button. When you save the integration, Diga validates the connection to the MCP server and syncs its tools automatically.If validation fails:
  • Verify the server URL is correct
  • Confirm the credentials are active
  • Make sure the MCP server is online and accessible
4

Sync Tools

When you save the integration, Diga automatically:
  1. Discovers what tools the server offers
  2. Reads their descriptions and parameters
  3. Displays them in your tools list
The initial tool sync happens when the integration is created. Tools are also re-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:
  1. It will explain to the user what it will do
  2. It will ask for explicit confirmation
  3. It will only execute if the user accepts

​
Tool Synchronization

Since tools are synced from the MCP server, any changes on the server (new tools, updates) will be reflected in Diga the next time you list the tools or assign the integration to an agent.
If the MCP server isn’t managed by you, we recommend periodically checking the tools to make sure everything is up to date.

​
Next Steps

Assign to Agents

Learn how to assign MCP integrations to your agents and filter tools.

HTTP Integrations

Discover how to create custom tools with HTTP.