Connect your AI assistant to UprootSecurity

Create a secret key on your profile, then paste the UprootSecurity endpoint and that key into your assistant's MCP configuration. MCP — the Model Context Protocol — is a standard way to let an AI assistant use UprootSecurity on your behalf. Connecting an assistant takes about two minutes.

Step 1: Create your key

Go to My Profile and find the API key section. If you don't have a key yet, choose Create key.

Your key is shown once, at the moment you create it. Copy it right then — into a password manager, or straight into your assistant's configuration file. After that, the API key section shows only when the key was created and when it was last used. There is no way to see the key again.

Treat it like a password. Anyone holding it acts as you inside UprootSecurity: same organization, same role, same modules you get when you sign in, and never more. What your assistant can see — and what it can change draws that line in full.

No API key section on your profile? You're a Portal User, and Portal Users can't create a key. Every other role can.

Step 2: Paste the endpoint and key into your assistant

Two values do the whole job:

• Endpoint: https://api.uprootsecurity.com/v1/mcp
• Header: Authorization: Bearer <your key> — every UprootSecurity key starts with uprs_

Use the block for your client, and swap uprs_YOUR_KEY for the key you copied.

Claude Code — .mcp.json in your project root

{
  "mcpServers": {
    "uprootsecurity": {
      "type": "http",
      "url": "https://api.uprootsecurity.com/v1/mcp",
      "headers": { "Authorization": "Bearer uprs_YOUR_KEY" }
    }
  }
}

Cursor — ~/.cursor/mcp.json (global) or .cursor/mcp.json (per project)

{
  "mcpServers": {
    "uprootsecurity": {
      "url": "https://api.uprootsecurity.com/v1/mcp",
      "headers": { "Authorization": "Bearer uprs_YOUR_KEY" }
    }
  }
}

Any other MCP client

Any MCP-capable client works, as long as it can call an HTTPS endpoint and send a fixed authorization header. Give it the same URL and the same header — only the shape of its configuration file differs. We've verified the setup end to end in Claude Code and Cursor.

Step 3: Confirm it worked

Start (or restart) your assistant so it reads the new configuration, then ask it: "List my failed compliance tests." If it names real tests from your organization back to you, you're connected.

If it can't name any tests — or says it doesn't have access to UprootSecurity at all — Why a capability is missing, or a request failed covers the usual causes.

Regenerating your key

Regenerate creates a fresh key and retires the old one immediately. Everywhere the old key still lives — each assistant, each machine, each configuration file — stops working and needs the new key pasted in. You hold one key at a time, so regenerate only when you're ready to update every place at once. Regenerate when the key may have leaked, when you're handing back a machine, or when you want to cut an assistant off.

The new key is shown once too. Copy it then.