Overview

The Platform MCP Server can be integrated with both Claude Code and Claude Desktop.

Claude Code is an agentic command line tool that enables developers to delegate coding tasks using natural language prompts.
Claude Desktop is the desktop application that supports conversational brainstorming and queries using the Claude AI assistant.

Although Claude Code is a distinct application from Claude Desktop, a single desktop application may display both a Code tab (Claude Code) and Chat tab (Claude Desktop). Each application connects to the Platform MCP Server independently and must be configured separately; configuring one does not configure the other.

Claude Code

Claude Code can connect to the Platform MCP through MCP to Platform API documentation, tenant data, developer resources on the Intelligent Risk Platform, and Platform MCP tools.

Model Context Protocol (MCP) secures access to MCP Server data resources and operations by defining the scope of MCP client privileges. The scope of MCP Server authorization defines the access rights that are granted to MCP clients.

The Platform MCP Server can be configured with a local (per-directory) or project scope. The user (machine-wide) scope is not supported. The Platform MCP Server supports two scopes: local and project. The user scope is not supported.

Scope	Description	File Location
`local`	A project-specific configuration stored locally that is generally not under version control.	`./claude.json`
`project`	A shared configuration under version control that is shared with everyone with access to a repository.	`<project-dir>/.mcp.json`
`user`	Not supported.	N/A

Configure Claude Code with Local Scope

The configuration specifies the MCP Server endpoint and API key.

Ensure the that the domain of specified MCP Server URL is the correct region-specific domain. The domain specified in the MCP Server endpoint must match the domain specified in the tenant's host domain. See Platform MCP Server Endpoints.

To configure integration with local scope:

Navigate to the project's root directory.

In the CLI terminal, run the command:

claude mcp add --transport http --scope local irp-integration-mcp \
  https://api-use1.rms.com/platform/integration/v1/mcp \
  --header "Authorization: YOUR_IRP_API_KEY"

The --scope flag is optional and can be omitted if local is specified.

This command writes the Platform MCP Server URL and client credentials to the Claude Code configuration file. The name and location of the Claude Code configuration file depends on whether the scope of the configuration is set to local or project.

If the scope is set to local, the claude.json will look something like the following example. Note that the default scope is not written to the file:

{
  "projects": {
    "/absolute/path/to/current/directory": {
      "mcpServers": {
        "irp-integration-mcp": {
          "type": "http",
          "url": "https://api-use1.rms.com/platform/integration/v1/mcp",
          "headers": {
            "Authorization": "YOUR_IRP_API_KEY"
          }
        }
      }
    }
  }
}

The project directory (/absolute/path/to/directory) is captured automatically when from the current directory.

Configure Claude Code with Project Scope

The configuration specifies the MCP Server endpoint and API key.

To configure with project scope:

Navigate to the project's root directory.
In the CLI terminal, run the command to create the local configuration.

Ensure the that the domain of specified MCP Server URL is the correct region-specific domain. The domain specified in the MCP Server endpoint must match the domain specified in the tenant's host domain.
```
claude mcp add --transport http --scope project irp-integration-mcp \
  https://api-use1.rms.com/platform/integration/v1/mcp \
  --header "Authorization: YOUR_IRP_API_KEY"
```

If the scope is set to project, the configuration is written to an .mcp.json file that is stored in the <project-dir>/.mcp.json.

{
  "mcpServers": {
    "irp-integration-mcp": {
      "type": "http",
      "url": "https://api-use1.rms.com/platform/integration/v1/mcp",
      "headers": {
        "Authorization": "${IRP_API_KEY}"
      }
    }
  }
}

{
  "mcpServers": {
    "irp-integration-mcp": {
      "type": "http",
      "url": "https://api-euw1.rms.com/platform/integration/v1/mcp",
      "headers": {
        "Authorization": "${IRP_API_KEY}"
      }
    }
  }
}

Validate Claude Code Connection

To validate connection:

$ claude mcp list
irp-integration-mcp: https://api-euw1.rms-ppe.com/platform/integration/v1/mcp (HTTP) - ✔ Connected

$ claude mcp get irp-integration-mcp

irp-integration-mcp:
  Scope: Local config (private to you in this project)
  Status: ✔ Connected
  Type: http
  URL: https://api-euw1.rms-ppe.com/platform/integration/v1/mcp
  Headers:
    Authorization: ${IRP_API_KEY}

To remove this server, run: claude mcp remove irp-integration-mcp -s local

Claude Desktop

Claude Desktop is a separate product from Claude Code. Like Claude Code, Claude Desktop supports Platform MCP Server integration and can access and utilize all Platform MCP Server tools including execute-api.

Unlike Claude Code, Claude Desktop does not natively support connecting to remote MCP Servers. Claude Desktop supports two options for remote MCP Server integration:

Custom connectors support header authentication. Header authentication is available to organizations with the Team, Enterprise, Pro, and Max plans. If header authentication is not available, ask your Claude Administrator to request access.
mcp-remote is an open-source utility that allows Claude Desktop to connect to a remote MCP server such as the Platform MCP Server.

If your organization has licensed a version of Claude Desktop that supports custom connectors, Moody's strongly recommends that you choose that option.

Configure Claude Desktop with custom connector

A custom connector is a user-defined integration that connects Claude Desktop to an MCP Server.

A Claude custom connector can send authentication credentials such as API keys as a request header. Custom connectors with header authentication is currently only available to a limited set of organizations.

Different methods are available to you depending on the version of Claude Desktop licensed by your organization.

For organizations with the Team and Enterprise plans, custom connectors can be configured by an Owner or Primary Owner in Organization Settings. Once created, team members can select the custom connector in Connectors of the Claude Desktop. To learn more, see https://support.claude.com/en/articles/11175166-get-started-with-custom-connectors-using-remote-mcp.
For organizations with the Pro and Max plans, individuals can create custom connectors in Settings > Connectors.

The configuration enables you to specify the MCP Server endpoint and the authentication credentials. Claude surely stores the specified credentials and never displays the key again. Claude Desktop sends these credentials with every request.

To configure with custom connector (Pro and Max plans):

In Claude Desktop, open Settings > Connectors.
Click Add > Add Custom Connector.
Specify a name of the custom connector. The specified name is displayed in the list of connectors.
Specify the URL of the Platform MCP Server.

Ensure the that the domain of specified MCP Server URL is the correct region-specific domain. The domain specified in the MCP Server endpoint must match the domain specified in the tenant's host domain. See Platform MCP Server Endpoints.
```
https://api-use1.rms.com/platform/integration/v1/mcp
```
```
https://api-euw1.rms.com/platform/integration/v1/mcp
```
Click Continue.
Review the authentication settings, and update as needed. Click Continue.
In the Authentication section, specify the authentication method. Select the No Sign In option.
In the Request Headers section, specify the credentials to be used by the client (e.g. an API key). Do not include the Bearer prefix.
Click Add.

Configure Claude Desktop with mcp-remote

mcp-remote is an open-source utility (distributed as an npm package) that allows Claude Desktop to connect to a remote MCP server such as the Platform MCP Server.

If your organization has not licensed a version of Claude Desktop that supports header authentication, you use mcp-remote to bridge a connection to the remote server. To learn more, see https://www.npmjs.com/package/mcp-remote.

To configure with mcp-remote:

Confirm that the host (MacOS or Windows) machine has Node.js version 18.0 or later installed. If Node.js is missing or is available only in an older version, you must install Node and ensure that version 18 or later is available. For step-by-step instructions, see https://nodejs.org/en/download.
Select Settings > Developer > Edit Config.

The claude_desktop_config.json is displayed.
- macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
- Windows: %APPDATA%\Claude\claude_desktop_config.json
Add irp-integration-mcp server entry in the claude_desktop_config.json. The object enables the MCP host to download and run the mcp-remote package.

Ensure the that the domain of specified MCP Server URL is the correct region-specific domain. The domain specified in the MCP Server endpoint must match the domain specified in the tenant's host domain. See Platform MCP Server Endpoints.
```
{
  "mcpServers": {
    "irp-integration-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://api-use1.rms.com/platform/integration/v1/mcp",
        "--header",
        "Authorization: YOUR_IRP_API_KEY"
      ]
    }
  }
}
```
```
{
  "mcpServers": {
    "irp-integration-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://api-euw1.rms.com/platform/integration/v1/mcp",
        "--header",
        "Authorization: YOUR_IRP_API_KEY"
      ]
    }
  }
}
```
The configuration defines parameters that enable the Claude Desktop to download and run the mcp-remote package using the npx package runner. The mcp-remote package creates the bridge that enables the Claude Desktop to connect to the specified MCP Server using the specified API key. The -y flag ensures that the installation of the mcp-remote package is automatically accepted.
Restart Claude Desktop.