Skip to main content
Ruby can expose your workspace as a remote MCP Server, so compatible MCP clients can use Ruby where you already work. This lets tools such as IDEs and AI assistants call Ruby to search workspace knowledge, work with conversations, and access files or Pods through the Model Context Protocol. Use this page when you want to connect an MCP client to Ruby. If you want to add an external MCP Server as a tool inside Ruby, see Adding an MCP Server instead.

Server URL

Use https://app.ruby.ad/mcp as the Ruby MCP server URL. Add this URL in any compatible MCP client that supports remote MCP servers with OAuth authentication. Client-specific setup steps vary by product and are not covered in this page.

What it enables

Once connected, the Ruby MCP Server lets your MCP client work with Ruby on behalf of the authenticated user. The first version exposes tools to:
  • identify the current Ruby user and workspace;
  • list available agents;
  • list conversations, create conversations, create messages, and retrieve conversation messages;
  • retrieve Pod information and Pod tasks;
  • list, read, create, search, and resolve files scoped to conversations or Pods;
  • search across workspace Spaces.
The exact tools exposed by the server may evolve over time. The Ruby MCP Server does not proxy every third-party tool configured in your Ruby workspace.

Authentication and permissions

The Ruby MCP Server uses OAuth. In most compatible clients, authentication starts automatically after you add the MCP Server URL. You will be asked to sign in to Ruby and select the workspace to connect. The connected client acts as the authenticated Ruby user. It can only access the Ruby data, Spaces, conversations, Pods, and files that this user can access in Ruby. Tokens issued for the MCP Server are scoped to MCP usage and are not Ruby API keys. Note: API keys are not used to connect to the Ruby MCP Server. Use the OAuth flow initiated by your MCP client.

OAuth client registration

Ruby supports the OAuth client registration mechanisms used by MCP clients:
  • Dynamic Client Registration (DCR), for clients that register dynamically with the authorization server during setup.
  • Client ID Metadata Documents (CIMD), for clients that identify themselves through a client metadata document.

Required resource parameter

MCP clients must include the OAuth resource parameter in both authorization and token requests. This parameter identifies the MCP Server the token is intended for and allows Ruby to issue tokens scoped to the Ruby MCP Server. Clients that omit the resource parameter are not supported. If your client fails during OAuth, check whether it follows the MCP authorization specification for resource parameters: Model Context Protocol authorization specification.

Admin controls

Workspace admins can disable Ruby MCP Server access for their workspace. Admins can also control which redirect URIs are allowed during client authentication. If a user cannot connect, check that the Ruby MCP Server is enabled for the workspace and that the MCP client’s redirect URI is allowed.

Compatibility

The Ruby MCP Server is designed for clients that support remote MCP servers and the latest MCP authorization flow, including OAuth resource parameters. Some MCP clients may not work if they do not implement the expected OAuth metadata discovery or required authorization parameters. If authentication fails before the Ruby login screen, update the client and confirm that it supports remote MCP servers with OAuth, including the resource parameter.

Troubleshooting

If the connection does not work:
  1. Confirm that you are using the correct region URL, either https://app.ruby.ad/mcp or https://app.ruby.ad/mcp.
  2. Confirm that your MCP client supports remote MCP servers with OAuth authentication.
  3. Confirm that your MCP client includes the OAuth resource parameter in authorization and token requests.
  4. Ask a Ruby workspace admin to confirm that Ruby MCP Server access is enabled for the workspace.
  5. If the client shows a redirect URI or OAuth error, ask an admin to verify that the redirect URI is allowed.