Zum Hauptinhalt springen
This page is not translated yet. Deutsch is switched on so the navigation and URLs can be tested; the text below is the English original. Use the language selector in the header to switch back, or see the documentation home.

Rescale MCP Server — Getting Started

Overview​

The Rescale MCP Server connects supported AI assistants and agentic development tools to the Rescale platform through the open Model Context Protocol (MCP). After you connect and sign in with your Rescale account, you can use natural-language requests to inspect and manage jobs, workstations, files, analyses, hardware, and other supported Rescale resources.

Before You Begin​

You need:

  • An active Rescale account.
  • Access to the organization and workspace you want to use.
  • Rescale MCP access enabled for your account or workspace.
  • A supported client that can connect to a remote MCP server over Streamable HTTP and complete an OAuth browser flow.

Contact your workspace administrator or Rescale Support if you are unsure whether your account has access.

Choose Your Regional Endpoint​

Use the MCP endpoint for the same Rescale region as your account.

RegionMCP server URL
United States (commercial)https://mcp.services.platform.rescale.com/mcp
Europehttps://mcp.services.eu.rescale.com/mcp
Japanhttps://mcp.services.platform.rescale.jp/mcp
Koreahttps://mcp.services.kr.rescale.com/mcp
Pick your platform to see just your values, here and across the docs:

The examples below use the United States endpoint. Substitute your regional URL when needed.

Connect from Claude Desktop​

If Rescale MCP is available in the Claude Connectors Directory, select it and click Connect. Otherwise, add the hosted server as a custom connector.

Claude Free, Pro, and Max​

  1. Open Customize → Connectors.

  2. Click Add custom connector.

  3. Enter Rescale MCP as the name and enter your regional MCP server URL.

    The name and the regional server URL are the only two values you enter.
  4. Continue with the authentication settings detected by Claude.

  5. Click Add, then Connect.

    Rescale MCP appears in your connectors once added. Connect starts the sign-in.
  6. Sign in to Rescale in the browser window and approve access.

For more information, see Third-party connectors with remote MCP.

Claude Team and Enterprise​

An organization owner adds the connector once:

  1. Open Organization settings → Connectors.
  2. Click Add, then select Custom. If prompted for a connector type, select Web.
  3. Enter Rescale MCP as the name.
  4. Enter your regional MCP server URL.
  5. Continue with the authentication settings detected by Claude. Do not enter a Rescale API key or custom request header.
  6. Click Add.

Each user can then open Customize → Connectors, find Rescale MCP, and click Connect to sign in.

Connect from Claude Code​

Add the hosted server at user scope so it is available across your projects:

claude mcp add --transport http --scope user rescale-mcp \
https://mcp.services.platform.rescale.com/mcp

Start the OAuth sign-in:

claude mcp login rescale-mcp

Your browser opens the Rescale sign-in flow. After authentication, start Claude Code and run:

/mcp

Confirm that rescale-mcp appears as connected. You can also use the Authenticate or Re-authenticate action from this panel.

For more information, see Connect Claude Code to tools via MCP.

Connect from ChatGPT (Desktop)​

If Rescale MCP is available in ChatGPT Plugins, install it and complete the Rescale sign-in flow. To add the server directly as a developer-mode app:

  1. In ChatGPT, open Settings → Security and login.

  2. Turn on Developer mode. Availability may depend on your ChatGPT plan and workspace policy.

  3. Open ChatGPT Plugins and click the Add button, then Add MCP Server.

  4. Create a developer-mode app named Rescale MCP.

  5. Select type Streamable HTTP.

  6. Enter your regional MCP server URL (from the table above).

    Streamable HTTP is the transport to select. Save before authenticating.
  7. Click Save.

  8. Once saved, click Authenticate.

    Authenticate appears on the saved server row.
  9. When prompted, sign in to Rescale and approve access.

For more information, see ChatGPT Developer mode.

Connect from Codex CLI​

Add the hosted Streamable HTTP server:

codex mcp add rescale-mcp \
--url https://mcp.services.platform.rescale.com/mcp

Start the OAuth sign-in:

codex mcp login rescale-mcp

Complete the Rescale sign-in flow in your browser. Then verify the connection:

codex mcp list

In the Codex terminal interface, you can also run /mcp to view the server and its tools. The ChatGPT desktop app and Codex IDE extension provide an MCP servers settings page where you can add the same Streamable HTTP URL and select Authenticate.

For more information, see Model Context Protocol in Codex.

Connect from Another MCP Client​

Use these settings if your client supports remote MCP servers and OAuth:

  • Name: Rescale MCP
  • Transport: Streamable HTTP
  • Server URL: Your regional endpoint
  • Authentication: OAuth

The client should discover the Rescale authorization service automatically. Do not configure an API key header for the hosted OAuth connection.

Sign In and Authorize Access​

The first connection or tool call may open a browser window:

  1. Sign in with your Rescale credentials.

  2. If your Rescale identity has access to more than one workspace, select the workspace you want the MCP connection to use. Users with access to only one workspace skip this page.

    Select the workspace whose jobs, files, and other resources you want to access. The displayed client name varies by MCP client.

    The OAuth grant and access token are bound to the workspace you select. Your existing permissions within that workspace still apply.

  3. Review and approve the requested access.

  4. Return to your AI client.

The client sends an access token with subsequent MCP requests and refreshes the connection when supported. If access expires or is revoked, use the client's Authenticate, Re-authenticate, or MCP login action.

Verify the Connection​

Start with read-only requests:

  • "List my five most recent Rescale jobs and summarize their status."
  • "Show the status history and available output files for job [JOB_ID]."
  • "Which analyses and hardware resources are available to me?"

Then test a state-changing workflow in a non-production workspace:

  • "Prepare a Rescale job using this analysis, hardware, command, and input file. Ask me before submitting it."

The exact tools available to your AI client can vary by region, product access, workspace permissions, and the current Rescale MCP tool set.

Use Rescale MCP Safely​

Review state-changing actions

Rescale MCP can expose tools that create, update, submit, stop, delete, upload, download, or otherwise change Rescale resources. AI assistants can make mistakes. Review the proposed action, identifiers, parameters, and tool input before approving a write operation.

The connector does not bypass Rescale access controls. Every request runs with your authenticated Rescale identity and remains subject to your existing organization, workspace, and resource permissions.

For initial testing:

  • Use a designated test workspace and non-critical resources.
  • Begin with read-only requests.
  • Ask the assistant to prepare or explain an action before executing it.
  • Confirm job IDs, file IDs, hardware, software versions, commands, and cost-sensitive settings.
  • Do not place passwords, API keys, access tokens, or other secrets in prompts.

Troubleshooting​

The server does not connect​

  • Confirm that you used the endpoint for your Rescale region.
  • Confirm that the URL ends in /mcp.
  • Confirm that your client supports Streamable HTTP and OAuth for remote MCP servers.
  • Update your client to a current version and retry.

The browser sign-in does not open​

  • Use the client's Authenticate, Re-authenticate, or MCP login action.
  • In Claude Code or Codex, copy the displayed authorization URL into a browser if it does not open automatically.
  • Confirm that local security software is not blocking the OAuth callback to your client.

Authentication succeeds, but a tool returns a permission error​

The MCP server uses your existing Rescale permissions. Confirm that you can access the same organization, workspace, job, file, or operation in the Rescale platform.

Tools are missing or appear outdated​

Refresh the connector or restart the client so it retrieves the current tool list. Workspace administrators may also restrict available connectors or tools.

Authentication expired or was revoked​

Re-authenticate the server from your client. If the problem continues, remove the connection, add it again, and contact Rescale Support.

  • MCP Server for when to reach for it, and how it compares with Rescale Edison and agents.
  • REST API for the endpoints behind the MCP tools.
  • CLI for a terminal-based way to drive the same operations.