Unified.to MCP Server

Generate a connection-scoped MCP URL

get_unified_connection_mcp_url

Get the MCP remote server URL for a specific connection ID. Returns a ready-to-use, connection-scoped Streamable HTTP MCP endpoint that exposes that connection's integration-specific tools. Authenticate with a workspace API key to use this. The URL embeds a credential and grants tool access without a further login, so treat it as a secret. It does NOT expire on its own. Revocation depends on the mode (see the mode parameter): an 'api'-mode URL carries the workspace API key and is revoked by rotating that key (which affects every URL that used it); a 'user'-mode URL is scoped to this one connection and is revoked by deleting the connection. Optional server options (permissions, tools, aliases, defer_tools, hide_sensitive, include_external_tools) are baked into the returned URL as query parameters.

Input Schema

TableJSON Schema

Name	Required	Description
`mode`	No	Authentication mode for the generated URL
`tools`	No	Comma-separated list of tool IDs or wildcard patterns to limit which tools the URL exposes (e
`aliases`	No	Custom description aliases in the form 'key:alt1,alt2;key2:alt3' to improve tool matching (e
`defer_tools`	No	Defer tool loading to reduce context usage
`permissions`	No	Comma-separated permission scopes to limit the tools exposed by the URL (e
`connection_id`	Yes	The ID of the connection to generate an MCP remote URL for
`hide_sensitive`	No	When true, strips PII and other sensitive fields from tool responses before they reach the LLM
`include_external_tools`	No	When true, exposes the vendor's raw passthrough endpoints as additional callable MCP tools

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 24, 2026

removedInput schema / properties / dc

Removed value: -{
-  "description": "Preferred data center / region for the generated URL",
-  "enum": [
-    "us",
-    "eu",
-    "au",
-    "dev"
-  ],
-  "type": "string"
-}

AddedJul 14, 2026

TDQS

A4.6/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The description goes well beyond the sparse annotations by disclosing that the URL embeds a credential, does not expire on its own, and has mode-dependent revocation behavior. It even warns that rotating an api-mode key affects every URL that used it. This is rich behavioral context that an agent cannot get from the schema or annotations alone.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the tool's purpose and output, then logically moves through authentication, secret handling, revocation, and optional parameters. It is longer than a simple one-liner, but the length is justified by the security-sensitive nature of the operation, and every sentence carries relevant information without fluff.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description covers the key concerns: what is returned, how to authenticate, security implications, non-expiry, revocation, and how optional parameters affect the output. However, it does not specify the default behavior or requirement of the optional mode parameter beyond the enum, and it only loosely characterizes the return format since there is no output schema. These are minor gaps for an otherwise rich description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds meaningful semantics for the mode parameter: api-mode carries the workspace API key and is revoked by rotation, while user-mode is scoped to the connection and revoked by deletion. It also explains that optional server options are baked into the returned URL as query parameters, which adds value beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The opening sentence states a specific verb and resource: 'Get the MCP remote server URL for a specific connection ID.' The next sentence clarifies the returned artifact as a ready-to-use, connection-scoped Streamable HTTP MCP endpoint, which distinguishes it from sibling tools like get_unified_connection or list_unified_connections. An agent can select this tool confidently without needing to infer scope.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides an explicit prerequisite: 'Authenticate with a workspace API key to use this.' It also warns that the URL should be treated as a secret, which is important usage context. It does not explicitly name alternatives or state when not to use this tool, so it falls just short of a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Unified.to MCP Server tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?