**Who can use this feature** - Supported on **Foundation, Growth,** and **Scale** plans ## Claude Connect Scrut MCP to Claude to bring your Scrut compliance data directly into your Claude conversations. ### 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. - A Claude account, either Claude Desktop or [Claude.ai](https://claude.ai/new) Web. Important: Make sure you're logged in to Scrut in your browser before you connect. The OAuth flow redirects you to Scrut to sign in and approve the connection, so having an active session helps this go smoothly. For Claude, the setup depends on how your Claude account is managed. Individual users can add and connect the Scrut MCP connector directly from their own Claude settings. Team or Enterprise users need an organization admin to add the Scrut MCP connector once under Admin settings → Connectors; then each team member connects the available connector individually. ### For Individual Users ### 1. Open Claude, go to **Customize → Connectors → Add**. 2. Click **Add → Add custom connector**. 3. Enter the required details: - Name (for example, Scrut MCP) - MCP Server URL. Paste 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 URL. - India | [https://mcp.scrut.io/mcp](https://mcp.scrut.io/mcp) - US | [https://mcp.us.scrut.io/mcp](https://mcp.us.scrut.io/mcp) - EU | [https://mcp.eu.scrut.io/mcp](https://mcp.eu.scrut.io/mcp) - Australia | [https://mcp.au.scrut.io/mcp](https://mcp.au.scrut.io/mcp) **Note:** Connecting with the wrong region's URL won't return your compliance data. If you're unsure of your Scrut region, contact your CSM or [support@scrut.io](mailto:support@scrut.io). 4. Click **Continue**.

5. In Authentication, choose **Always Required**. 6. In OAuth Client, enter the client ID:** vpubmKiuV6hrcQLBwMLyo4aVWgheoH8U. **This value is the same across all regions and organizations. 7. Leave OAuth Client Secret blank. 8. Click **Add**.

9. Click **Connect**. You'll be redirected to Scrut to complete the authentication.

10. Return to **Claude → Connectors** and confirm that the Scrut connector shows as connected. Configure tool permissions, as required. Claude can now call Scrut MCP tools directly in your conversations.

### For Team or Enterprise Users ### If you're using Claude through a Team or Enterprise plan, your organization admin must add the Scrut MCP connector before you can connect it. Heads Up! The admin needs to add the connector for the entire org. Each team member must then enable it individually in their Claude account. #### **For organization admins** 1. In Claude, go to **Organization settings → Connectors**. 2. Follow the steps above under **For Individual Users** to add the Scrut MCP connector and click **Add to your team**. 3. Individual users can then authenticate with the connector to start using it with Claude. #### **For each team member** #### 1. Open Claude, go to **Customize → Connectors** 2. Search for the Scrut connector that your admin has added. 3. Click **Connect**. You'll be redirected to Scrut to complete the authentication.

4. Return to **Claude → Connectors** and confirm that the Scrut connector shows as connected. 5. Claude can now call Scrut MCP tools directly in your conversations. ## ChatGPT Connect Scrut MCP to ChatGPT to bring your Scrut compliance data directly into your ChatGPT conversations. ### 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. **Important:** Make sure you're logged in to Scrut in your browser before you connect. The OAuth flow redirects you to Scrut to sign in and approve the connection, so having an active session helps this go smoothly. ### Steps to Connect ChatGPT ### 1. Turn on Developer Mode if it isn't already enabled. Go to **Settings → Plugins**, scroll to the Developer Mode section, and turn on the toggle.

2. Click **Plugins** in the left navigation bar, then click the **+** icon to open the New Plugin dialog.

3. Enter a **Name** for the plugin, for example, Scrut MCP. 4. Under **Connection**, keep **Server URL** selected and enter the MCP Server URL that matches your Scrut tenant's region. For example, if your Scrut tenant is hosted in India, use the India URL. - India | [https://mcp.scrut.io/mcp](https://mcp.scrut.io/mcp) - US | [https://mcp.us.scrut.io/mcp](https://mcp.us.scrut.io/mcp) - EU | [https://mcp.eu.scrut.io/mcp](https://mcp.eu.scrut.io/mcp) - Australia | [https://mcp.au.scrut.io/mcp](https://mcp.au.scrut.io/mcp) **Note: **Connecting with the wrong region's URL won't return your compliance data. If you're unsure of your Scrut region, contact your CSM or [support@scrut.io](mailto:support@scrut.io). 5. Set **Authentication** to **OAuth**. 6. Expand **Advanced OAuth settings**. - Under **Registration method**, select **User-Defined OAuth Client**. (You may see a note that CIMD is unavailable — this is expected and needs no action.) - In the OAuth Client ID field, enter the client ID: `vpubmKiuV6hrcQLBwMLyo4aVWgheoH8U`. This value is the same across all regions and organizations. - Leave **OAuth Client Secret** blank. 7. Check **I understand and want to continue** to acknowledge the custom MCP server notice. 8. Click **Create**.

9. On the **Add Scrut MCP to ChatGPT** screen, click **Sign in with Scrut MCP**. You'll be redirected to Scrut to sign in and approve the connection.

10. After you approve the connection, you'll be redirected back to ChatGPT. 11. Go to **Settings → Plugins** and open **Scrut MCP**. Under **Information**, click **Refresh** to load the available Scrut MCP actions. **Heads Up!** ChatGPT keeps a frozen snapshot of Scrut MCP's tools from the time it was approved. If Scrut MCP's available actions change later, click Refresh in the app so ChatGPT picks up the update.

12. To verify the connection, start a new chat and ask a question about your Scrut compliance data, for example, "How many frameworks do I have in Scrut?" ChatGPT calls the matching Scrut MCP tool and returns an answer sourced from your Scrut data. ## Cursor Connect Scrut MCP to Cursor to bring your Scrut compliance data directly into your Cursor IDE sessions. ### 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. - Cursor IDE installed **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. 1. Go to Cursor Settings → Integrations & MCP → Add New MCP Server. 2. Fill in the fields: - **Name** (for example, Scrut MCP) - **MCP Server URL:** Paste 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 URL. - India | [https://mcp.scrut.io/mcp](https://mcp.scrut.io/mcp) - US | [https://mcp.us.scrut.io/mcp](https://mcp.us.scrut.io/mcp) - EU | [https://mcp.eu.scrut.io/mcp](https://mcp.eu.scrut.io/mcp) - Australia | [https://mcp.au.scrut.io/mcp](https://mcp.au.scrut.io/mcp) **Note:** Connecting with the wrong region's URL won't return your compliance data. If you're unsure of your Scrut region, contact your CSM or [support@scrut.io](mailto:support@scrut.io). - **Client ID: vpubmKiuV6hrcQLBwMLyo4aVWgheoH8U. **This value is the same across all regions and organizations. 3. Click **Save**. 4. After saving, return to Cursor Settings → Integrations & MCP. 5. Find the Scrut MCP server entry you just added. 6. Click Connect. Complete the OAuth authentication when prompted. 7. You'll be redirected to Scrut to review the connection request. 8. Click Continue. You'll be redirected back to Cursor. 9. The connector should appear as Connected. 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. ## Claude Code (CLI) Connect Scrut MCP to Claude Code to call Scrut MCP tools directly from your terminal sessions. ### 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. - Claude Code installed on your machine **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. 1. Open your terminal. 2. Run the following, replacing the URL with your region's values: For example, if your Scrut tenant is hosted in India, use the India URL. - India | [https://mcp.scrut.io/mcp](https://mcp.scrut.io/mcp) - US | [https://mcp.us.scrut.io/mcp](https://mcp.us.scrut.io/mcp) - EU | [https://mcp.eu.scrut.io/mcp](https://mcp.eu.scrut.io/mcp) - Australia | [https://mcp.au.scrut.io/mcp](https://mcp.au.scrut.io/mcp) **Note:** Connecting with the wrong region's URL won't return your compliance data. If you're unsure of your Scrut region, contact your CSM or [support@scrut.io](mailto:support@scrut.io). ```typescript claude mcp add --transport http scrut https://mcp.us.scrut.io/mcp \ --client-id vpubmKiuV6hrcQLBwMLyo4aVWgheoH8U \ --callback-port 8787 ``` 3. A browser window opens for authentication. Sign in to Scrut and approve the connection. 4. 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. ## Codex Connect Scrut MCP to Codex to call Scrut MCP tools directly from your Codex sessions. #### 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. - Codex installed **Important:** Make sure you're logged in to Scrut 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. Codex requires a fixed OAuth callback port, separate from Claude Code's, so both tools can connect at the same time without conflict. 1. Enable the RMCP client in Codex if it isn't already. Open (or create) `~/.codex/config.toml` and add: ```typescript [ 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): ```typescript 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. Use the same URL for both `--url` and `--oauth-resource` For example, if your Scrut tenant is hosted in India, use the India URL. - India | [https://mcp.scrut.io/mcp](https://mcp.scrut.io/mcp) - US | [https://mcp.us.scrut.io/mcp](https://mcp.us.scrut.io/mcp) - EU | [https://mcp.eu.scrut.io/mcp](https://mcp.eu.scrut.io/mcp) - Australia | [https://mcp.au.scrut.io/mcp](https://mcp.au.scrut.io/mcp) **Note:** Connecting with the wrong region's URL won't return your compliance data. If you're unsure of your Scrut region, contact your CSM or [support@scrut.io](mailto:support@scrut.io). ```typescript 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: ```typescript codex mcp remove scrut codex mcp add scrut --url https://mcp.us.scrut.io/mcp \ --oauth-client-id vpubmKiuV6hrcQLBwMLyo4aVWgheoH8U codex mcp login scrut ``` 5. Complete authentication: ```typescript codex mcp login scrut ``` 6. A browser opens for authentication. After you sign in and grant permissions for Scrut, return to the terminal. 7. Verify the connection. ```typescript codex mcp get scrut ``` 8. Launch Codex normally. ```typescript codex ``` Codex can now call Scrut MCP tools in your sessions. ## FAQs Scrut MCP uses the open MCP standard, so it works with any MCP-compatible AI tool. We've only tested and documented setup steps for Claude, Claude Code, ChatGPT, Cursor, and Codex, which is why those tools have dedicated guides above. To connect from another MCP-compatible tool, contact [support@scrut.io](mailto:support@scrut.io) with the tool name so we can add its callback URL. The exact configuration steps will differ by tool. 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. Check the following: - 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, checking with your admin if you're not sure. - Disconnect and reconnect the connector in your AI tool, start a new chat, and try again. If you’re still having issues, contact [support@scrut.io](mailto:support@scrut.io). No. Scrut MCP only accesses what your Scrut account already has permission to view and act on. It doesn't grant your AI tool broader access. 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. You don't need to configure any additional permissions for MCP access. This means the AI tool you're using isn't yet allowlisted with Scrut's OAuth provider. Scrut currently pre-configures callback URLs only for the tools with dedicated setup steps above (Claude, Claude Code, ChatGPT, Cursor, Codex). If you're connecting from another MCP-compatible tool, contact [support@scrut.io](mailto:support@scrut.io) with the tool name, and we'll add its callback URL so you can connect. --- Contact [support@scrut.io](mailto:support@scrut.io) or your CSM for further assistance.