Unified MCP Server
MCP Server Options
Add these URL parameters to the MCP URL:
connection | The connection ID to access. Only used when the credential is a workspace API key or an enterprise-managed token. |
token | The credential: a workspace API key or a connection-scoped token. Deprecated as a URL parameter; send it in the Authorization: Bearer (or x-api-key) header instead. See Authentication. |
hide_sensitive | When true, removes sensitive (PII) fields from tool results: name, email, emails, telephones, address, addresses, gender, date_of_birth, ssn_sin, compensation, and credential fields such as token, access_token and client_secret. |
permissions | A comma-delimited list of permissions, eg. crm_contact_read,crm_company_read. It can only narrow the tools: a permission the connection was not granted is ignored. |
tools | A comma-delimited list of tool IDs to restrict the MCP server to. Supports the wildcards * and ?, matched case-insensitively, eg. list_*,*invoice*. |
defer_tools | A comma-delimited list of tool IDs (or partial IDs) to mark with defer_loading, so the LLM does not load or tokenize them up front. Use all to defer every tool. Only applies to the GET /tools endpoint, which also adds Anthropic's tool-search tool to the list. |
aliases | A list of words and their aliases that add extra descriptions to tools, in the format word1:alias1,alias2;word2:alias1,alias2. eg. ?aliases=employee:user,person;employees:users,people |
include_external_tools | When true, also include tools for the rest of the integration's own API, not just the unified API. These tools are prefixed external_. |
disable_events | When true, the server does not offer MCP Events for this connection: it does not declare the events extension, and events/* requests return "Method not found". Default false. Also accepted by get_unified_connection_mcp_url. |
integration_type | Without a credential, serves that integration's tool definitions as an unauthenticated preview. The tools can be listed but not called. An unknown type returns 404. |
signup | signup=true lets an agent with no credential connect and call signup_unified_workspace to create a workspace. See Agent Signup. |
dc | Removed. Was a region hint, but nothing ever routed on it — the hostname selects the region. It is no longer accepted by get_unified_connection_mcp_url and is no longer added to generated URLs. A URL that still carries ?dc= keeps working; the value is ignored. Use the region hostname. |
For example:
https://mcp-api.unified.to/mcp?connection=<CONNECTION_ID>&hide_sensitive=true&tools=list_*,get_*&disable_events=true
The boolean options (hide_sensitive, include_external_tools and disable_events) default to false.
Events and permissions
MCP Events are offered only when the server is for one connection: a connection-scoped token, or a workspace API key or enterprise-managed token with connection. OAuth sign-in serves Core Unified API mode, which has no events.
- An enterprise-managed token can poll the events of the categories it can read (eg.
crm.readforcrm_contact.created), but cannot create webhook subscriptions. permissionsandtoolsdo not narrow the event types; usedisable_events=trueto turn events off.
Data regions
The hostname selects the data region; regions do not resolve across one another. Use the host your workspace's data lives in — US mcp-api.unified.to, EU mcp-api-eu.unified.to, AU api-au.unified.to. See Endpoints.
Are we missing anything? Let us know
Was this page helpful?