Connecting Claude ​

InfraScout exposes a Model Context Protocol (MCP) endpoint over Server-Sent Events (SSE). You connect Claude Desktop — or any MCP-compatible client — to this endpoint, and InfraScout's full tool set becomes available to Claude for driving infrastructure assessments.

What You Need ​

Before configuring your MCP client, gather three things: Claude Desktop (or another MCP client that supports SSE transport), your InfraScout MCP endpoint URL, and your API key. Both the endpoint URL and the API key are found in the InfraScout dashboard under Settings → MCP Connection.

Connecting Claude Desktop ​

Claude Desktop reads MCP server configuration from a JSON settings file. Open Claude Desktop, go to Settings → Developer → Edit Config to open the file directly. If you prefer to locate it manually, the path depends on your operating system:

  • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
  • Windows: %APPDATA%\Claude\claude_desktop_config.json

Add an infrascout entry inside the mcpServers object:

json
{
  "mcpServers": {
    "infrascout": {
      "url": "YOUR_MCP_ENDPOINT_URL",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}

Replace YOUR_MCP_ENDPOINT_URL and YOUR_API_KEY with the values from the dashboard. Save the file and restart Claude Desktop. InfraScout should appear in Claude's tool panel with its full set of tools available.

TIP

Copy the endpoint URL and API key directly from Settings → MCP Connection in the InfraScout dashboard to avoid typos.

Verify the Connection ​

Once Claude Desktop has restarted, ask Claude:

"Use the auth_whoami tool to show me my InfraScout identity."

Claude should respond with your user name, email address, and assigned role. If it returns an error instead, double-check that the endpoint URL and API key in your config file exactly match the values shown in the dashboard.

Other MCP Clients ​

Any MCP client that supports SSE transport and Bearer token authentication can connect to InfraScout using the same endpoint URL and API key. The configuration details vary by client — consult your client's documentation for how to register a custom MCP server with a custom authorization header.

Roles and Access ​

Your InfraScout role determines which tools Claude can invoke on your behalf. Three roles exist:

  • User — read access to agents and assessment insights
  • Operator — can start and submit assessment sessions in addition to read access
  • Admin — full access, including managing agent groups, playbooks, and connections

Your role is assigned by your organization's InfraScout administrator. The auth_whoami tool always shows your current role so you can confirm what level of access Claude is operating with.

Next Steps ​

With the connection established, follow the Quick Start guide to run your first assessment, or jump directly to Running Assessments for a deeper walkthrough.