Unified MCP Server

Changelog

Added a new "workspace" mode that allows our customers to interact with their Unified data, including connections, webhooks, API calls, and issues/tickets.
Total tool count is now 21,993, including 4,425 "unified" tools.

Total tool count is now 19,872.
Added a new tools parameter to specify exactly which tools to allow in the MCP server.
Aliases no longer create seperate tools, but now generate extended tool descriptions. This will help with LLM tool matching. We removed the default_aliases parameter, as that is now the defaul behaviour.

Total tool count is now at 17,569; 3,963 "unified" tools across 317 integrations over 20 categories. 13,606 "non-unified" tools across 93 integrations.

New data-region in Europe. Change the MCP URL to https://mcp-api-eu.unified.to. Data accessed by the MCP will be transfered directly from the EU data-region of Unified.to.
Added support to expand an integration's tool over all of its available API endpoints, and not just the unified API's endpoints, which expand the number of tools by an additional 12,979. Use &include_external_tools=true.

Added support for all Unified.to API data-centers; US, EU, AU. The MCP will figure it out by itself.

Added structuredContent output when the MCP-Protocol-Version is 2025-06-18 or more recent
Added type parameter to GET /tools to return tools in a specific LLM data-model
Added hide_sensitive parameter to POST /tools/{id}/call and the MCP server URL to remove PII/sensitive data from results. eg. hide_sensitive=true
Added permissions parameter to GET /tools, POST /tools/{id}/call and MCP server URL to restrict tools
Added additional authentication mechanism token and connection to be ONLY used with LLM APIs

Are we missing anything? Let us know

Was this page helpful?