Documentation Index

Fetch the complete documentation index at: https://help.scrut.io/llms.txt

Use this file to discover all available pages before exploring further.

Connect Scrut MCP

  • Updated on Jul 21, 2026
  • Published on Jul 17, 2026
  • 6 minute(s) read
Prev Next

Who can use this feature

  • Supported on Foundation, Growth, and Scale plans

Connect Scrut to Claude, Cursor, Codex, or any MCP-compatible AI tool.

Prerequisites

  • An active Scrut account

  • Scrut MCP works for all Scrut roles: Admin, Contributor, and Auditor. It doesn’t require any additional access beyond what you already have in Scrut.

  • An MCP-compatible AI tool, such as Claude, Claude Code, Cursor, ChatGPT, or Codex.

Before You Begin

Important:

Make sure you're logged in to the Scrut platform in your browser before you try to connect. The OAuth flow redirects you to Scrut to sign in and approve the connection, so having an active session helps this go smoothly.

Step 1: Find Your Region-Specific Scrut MCP Server URL

Copy and save the Scrut MCP server URL that matches your Scrut tenant's region. For example, if your Scrut tenant is hosted in India, use the India row. You'll need this URL, along with the Client ID from Step 2, in Step 3.

Region

MCP Server URL

India

https://mcp.scrut.io/mcp

US

https://mcp.us.scrut.io/mcp

EU

https://mcp.eu.scrut.io/mcp

Australia

https://mcp.au.scrut.io/mcp

Important:

Connecting with the wrong region's URL won't return your compliance data. If you’re unsure of your Scrut region, connect with your CSM or contact support@scrut.io

Step 2: Copy the Client ID

Copy and save the Scrut MCP Client ID below. This value is the same across all regions and organizations. You'll need it alongside your region's server URL in Step 3.

Scrut Client ID: vpubmKiuV6hrcQLBwMLyo4aVWgheoH8U

Step 3: Connect Scrut MCP to Your AI Assistant

Once you have your region's MCP URL and Client ID, add them to your AI tool's MCP configuration. The steps below cover Claude, Claude Code, Cursor, ChatGPT, and Codex.

How to Connect Scrut MCP in ChatGPT

Note: You need a ChatGPT Business, Enterprise, or Edu plan to use MCP.

  1. Open ChatGPT and click your profile icon. Go to Settings → Apps & Connectors → Advanced Settings and turn on Developer Mode.

  2. Return to Apps & Connectors and click Create Connector or Add Custom Connector.

  3. Fill in the required information:

    • Name: For example, Scrut MCP.

    • MCP Server URL: Enter the HTTPS URL for your region from the table above.

    • Authentication method: Select OAuth.

  4. Click Connect. Complete the OAuth authentication when prompted.

  5. You'll be redirected to Scrut to review the connection request.

  6. Click Continue. You'll be redirected back to ChatGPT.

  7. The connector should appear as Connected.

ChatGPT can now call Scrut MCP tools in your conversations.

How to Connect Scrut MCP in Claude (Desktop and Claude.ai Web)

  1. Open Claude and click your profile, then go to Settings → Connectors.

  2. Click Add → Add custom connector.

    Note: If your organization allows custom connectors, you can continue with the setup below. If not, ask your organization admin to enable custom connectors first.

  3. Enter the required details:

    • Name: Enter a label, for example, Scrut MCP.

    • MCP Server URL: Enter the HTTPS URL for your region from the table above.

    • Advanced settings → OAuth Client ID: Enter your region's Client ID from the table above.

    • Leave OAuth Client Secret blank.

  4. Click Add.

  5. Navigate to settings and find the connector you just added.

  6. Click Connect. After creating the connection, you'll be redirected to Scrut to complete the authentication.

  7. Select the confirmation checkbox (I understand and trust this URL).

  8. Click Continue.

  9. Confirm the connector shows a tool count next to it (not 0). If it shows 0, disconnect and reconnect, then start a new chat.

Claude can now call Scrut MCP tools directly in your conversations.

Heads Up!

If you're on a Team or Enterprise plan, an admin can add the connector once under Admin settings → Connectors; each member then connects it individually under their own Settings.

How to Connect Scrut MCP in Claude Code (CLI)

  1. Open your terminal.

  2. Run the following, replacing the URL with your region's values from the table above:

claude mcp add --transport http scrut https://mcp.us.scrut.io/mcp \
  --client-id vpubmKiuV6hrcQLBwMLyo4aVWgheoH8U \
  --callback-port 8787

  1. A browser window opens for authentication. Sign in to Scrut and approve the connection.

  2. Return to your terminal. Claude Code confirms the connection is active.

Claude Code can now call Scrut MCP tools directly in your sessions.

Note:

Claude Code requires port 8787 to be free on your machine for the OAuth callback to complete.

How to Connect Scrut MCP in Cursor IDE

  1. Open Cursor Settings. Navigate to Tools & MCP.

  2. Click + New MCP Server (or Add New MCP Server).

  3. Fill in the fields:

    • Name: Enter a label, for example, Scrut MCP.

    • MCP Server URL: Enter the HTTPS URL for your region from the table above.

    • Client ID: Enter your region's Client ID from the table above.

  4. Click Save.

  5. After saving, return to Cursor's Settings, then Tools & MCP.

  6. Find the Scrut MCP server entry you just added.

  7. Once authentication is available, click Connect.

  8. After creating the connection, you'll be redirected to Scrut.

  9. Select the confirmation checkbox (I understand and trust this URL).

  10. Click Continue.

You can now use Scrut MCP directly within Cursor while you work.

Note:

A blank browser tab right after you approve the connection is normal. Check Cursor's MCP panel for the connected state instead.

How to Connect Scrut MCP in Codex

Codex requires a fixed OAuth callback port, separate from Claude Code's, so both tools can be connected at the same time without conflicting.

  1. Enable the RMCP client in Codex if it isn't already. Open (or create) ~/.codex/config.toml and add:

    [
features
]
experimental_use_rmcp_client = true

    This is required for Codex to connect to remote, OAuth-based MCP servers like Scrut's. Skipping this step will cause the next steps to fail or misconfigure the connection.

    Heads up! Some older Codex CLI versions use the key rmcp_client = true instead. If the next steps don't work, check which key your installed version expects and update accordingly.

  2. In the same ~/.codex/config.toml file, set a fixed callback port for OAuth (this only needs to be added once, and applies to all MCP servers you connect to in Codex):

    mcp_oauth_callback_port = 8788

    Note: Codex uses port 8788 so it doesn't conflict with Claude Code, which uses 8787. If you connect both tools on the same machine, make sure each port is free.

  3. Launch your preferred terminal (Terminal, PowerShell, iTerm, etc.).

  4. Run the following, replacing the placeholders with your region's MCP URL and Client ID from the tables above. Use the same URL for both --url and --oauth-resource:

codex mcp add scrut --url https://mcp.us.scrut.io/mcp \
  --oauth-client-id vpubmKiuV6hrcQLBwMLyo4aVWgheoH8U \
  --oauth-resource https://mcp.us.scrut.io/mcp

Note: Only use --oauth-resource if Codex doesn't already include a resource parameter in the Auth0 URL it generates. If you see the error resource parameter must be a string during login, remove the server and re-add it without --oauth-resource, then run login again:

codex mcp remove scrut
codex mcp add scrut --url https://mcp.us.scrut.io/mcp \
  --oauth-client-id vpubmKiuV6hrcQLBwMLyo4aVWgheoH8U
codex mcp login scrut

  1. Complete authentication:

codex mcp login scrut

  1. A browser opens for authentication. After signing in and granting permissions for Scrut, return to the terminal.

  2. Verify the connection:

codex mcp get scrut

  1. Launch Codex normally:

codex

Codex can now call Scrut MCP tools in your sessions.

How Sign-in and Access Work

Scrut MCP uses OAuth through Auth0. When you sign in, the connection is tied to your own Scrut user account. Your AI assistant acts in your existing Scrut role, so it can only reach what you can already reach on the Scrut platform. There are no additional permissions to configure for MCP access.

Verify the Connection

Open your AI tool and ask something specific to your compliance program, for example: Which SOC 2 controls don't have evidence mapped yet?

If the connection is working, your AI assistant returns an answer sourced from Scrut. If it doesn't:

  • Confirm you used the MCP server URL and Client ID for your own region.

  • Confirm you completed the sign-in and approval steps with Scrut.

  • Confirm your Scrut account is active. Check with your admin if you're not sure.

  • Disconnect and reconnect the connector in your AI tool, then start a new chat and try again.

Important: Scrut MCP only ever accesses what your Scrut account already has permission to see. It doesn't grant broader access through your AI tool.

Reach out to support@scrut.io or contact your CSM for further assistance.

Related articles