Find answers to common questions about your MCP connection, account, and usage limits. For what Scrut MCP can and can't do, see [Understand Scrut MCP](/docs/understand-scrut-mcp#capabilities-and-limitations). No. Scrut remains your system of record for your compliance program. Scrut MCP brings that context into the AI tools you already work in; it doesn't move your compliance program anywhere else. Yes. It is available for all plans (Foundation, Growth, and Scale) Yes. Scrut MCP provides a faster starting point for questionnaire responses, evidence filing, and status updates. It doesn't remove human review from evidence decisions or audit responses. Any Scrut user (admin, contributor, auditor) can connect Scrut MCP to their AI tool. Once connected, your AI assistant only sees what your existing Scrut role already lets you see. You don't need to configure separate MCP-specific permissions. If you're a partner or auditor with access to more than one workspace, your AI tool can reach every workspace you're already assigned to, and you can switch between them within the same session. Your new role applies automatically, and you don't need to reconnect. Scrut regularly checks your user record and role, so changes take effect within minutes. Scrut MCP requests from your account stop working. A deactivated user can't use Scrut MCP, just as they can't sign in to the Scrut platform. No. Scrut MCP acts in your own Scrut role with the same access you already have on the platform. It doesn't grant your AI tool broader access. No. Scrut MCP is self-serve, so you can connect it yourself by following the steps in [Connect Scrut MCP](https://help.scrut.io/docs/connect-scrut-mcp). Note: On Claude Team and Enterprise plans, your organization admin adds the Scrut MCP connector first. Each member then connects it individually. Yes. Each AI tool, such as Claude or Cursor, has its own separate sign-in. For example, disconnecting in Claude doesn't affect your MCP connection in ChatGPT or your Scrut web session. Yes, as long as the app that runs the model, such as Ollama, supports remote MCP servers with OAuth sign-in. Before you connect, contact [support@scrut.io](mailto:support@scrut.io) with the app's name so Scrut can add its callback URL. Without this, you see a **Callback URL mismatch** error when you try to connect. **Note: **MCP Results depend on how well the model handles tool calling, so smaller local models may give less reliable answers. No. Each person connects with their own Scrut login, and there's no limit on how many users can be connected at once. No. Scrut MCP uses short-lived access tokens that refresh automatically, so you stay connected. Your connection ends only when one of these happens: - You disconnect Scrut MCP in your AI tool. - Your sign-in grant expires or you revoke it. - Your Scrut account is deactivated. When a connection ends, your AI tool prompts you to sign in again. No. Scrut doesn't currently enforce rate limits on Scrut MCP requests, so you don't need to space out your prompts. No. Scrut MCP reads data from Scrut, including cloud test results and their remediation steps. It doesn't connect to your cloud environment or your code repository. If your AI tool already has access to your repository, the **scrut-fix-test** skill can use the remediation steps from Scrut to help you apply a fix there. See [Use Scrut MCP Skills](https://help.scrut.io/docs/use-scrut-mcp-skills). Yes, Scrut logs all actions taken through Scrut MCP the same way it logs a human user's actions. For example, if user "John" has uploaded an evidence file via MCP, Scrut will display this audit log: "John uploaded \[evidence attachment name]." Yes. If a workspace has multiple entities configured, you can ask your AI assistant to filter artifacts, such as evidence, controls, or policies, by entity within that workspace. Entity access still follows the permissions you already have in Scrut. Yes. If you have access to multiple workspaces, for example, as a partner or auditor, you can switch between them within a single MCP session. You don't need to disconnect and reconnect for each workspace you want to review. Contact [support@scrut.io](mailto:support@scrut.io) or your CSM for further assistance.

FAQs: Scrut MCP