Unified's MCP Server

May 26, 2025

Unified has launched an MCP server that connects any Unified connection to LLM (Large Language Model) providers supporting the newest MCP protocols. The available MCP tools will be determined by the integration's feature support and the connection's requested permissions.

Use-cases:

• End-Customer Conversation with LLMs: Allows your end-customers to interact with a LLM and access their 3rd-party information that was authorized in a Unified connection.
• Debugging End-Customers' Connections: Allows your product and support teams to assist your end-customers by debugging their Unified connections. Please make sure that you observe all privacy policies, both yours and your regions's, since your end-customer's data will be shared with the LLM.

MCP is a new protocol and it is moving fast. We expect more LLM & agent clients to support its newer Streamable HTTP transport protocol. We also expect that the MCP protocol will continue to expand quickly. Stay tuned as we also keep up.

Sample queries:

• List candidates for job X
• List deals for contact with email address joe@foo.com
• update application 12345 with a status of HIRED
• summarize the accounting balance sheet report
• find the vacation policy by listing the pages in Notion

Technical Specifications:

• Streamable HTTP MCP URL: https://mcp-api.unified.to/mcp
• SSE MCP URL: https://mcp-api.unified.to/sse

Authentication:

You must provide a token to the MCP server either as a token URL parameter (eg. ?token={token}) or in the Authorization header as a bearer token (eg. Authorization: bearer {token})

The token is generated as follows:{connection_ID}-{nonce}-{signature}

Installation:

Claude.ai (online):

Go to https://claude.ai, then navigate to Settings > Integrations. Click on "Add custom integration". Enter the MCP URL:

https://mcp-api.unified.to/sse?token={connectionID}-{nonce}-{signature}

Make sure to provide your end-customer the appropriate token value.

Claude (desktop client):

Edit the claude_desktop_config.json file:

{
    "mcpServers": {
        "unified-mcp": {
            "command": "npx",
            "args": [
                "-y",
                "mcp-remote",
                "https://mcp-api.unified.to/sse?token={connectionID}-{nonce}-{signature}",
                "--allow-http",
            ]
        }
    }
}

Make sure to provide your end-customer the appropriate token value.

Cursor:

Navigate to Cursor > Settings > Cursor Settings > MCP and edit the MCP configuration. Replace unified-mcp with the name of your own application and then make sure to provide your end-customer the appropriate token value.

{
    "mcpServers": {
        "unified-mcp": {
            "url": "https://mcp-api.unified.to/sse?token={connectionID}-{nonce}-{signature}"
        }
    }
}