Skip to main content
Workspace admins can add remote MCP tools from Spaces > Tools > Add tool > Add MCP server in the Ruby application. Enter the server’s public HTTPS URL and choose its authentication method. Prefer automatic OAuth discovery when the server provides it. For a server that requires a static OAuth client, create that client with the provider, then enter its client ID, client secret, and authorization settings in Ruby. Ask the provider for its current token and authorization endpoints. For OAuth callbacks, register https://app.ruby.ad/oauth/mcp/finalize for dynamic client registration or https://app.ruby.ad/oauth/mcp_static/finalize for a static client, as appropriate. Test the connection before making the tool available to agents. Custom servers must be reachable over HTTPS and must enforce the authentication method selected in Ruby. The MCP Inspector can help validate a server independently.

Restrict an MCP server to skills

In the server’s Availability tab, enable Restrict this tool to skills to make its tools available only through skills that reference them. Restricted tools are hidden from direct selection in the Agent Builder and input bar, cannot be added directly to conversations or agents, and are excluded from just-in-time tool discovery.

Manage tools and availability

The server settings have separate General, Tools & Stakes, and Availability tabs. Use Tools & Stakes to search for tools, select individual tools or Select all, and apply changes to the selected tools. Use Availability to control access across the workspace or selected Spaces. See Static egress IP addresses if your server requires a network allowlist. Ruby only calls an MCP server through a configured static egress route when the server’s hostname belongs to a domain verified for your workspace.