MCP Client Setup

Scout exposes an MCP (Model Context Protocol) endpoint that lets coding agents query your observability data, including traces, logs, metrics, service topology, and alerts, using natural language.

Prerequisites

• Your Scout MCP endpoint URL (<SCOUT_URL>/mcp/v1), see Finding your Scout URL below
• A Scout account in the corresponding tenant realm
• Node.js installed (for Claude Desktop only)

Claude Code CLI

Add the Scout MCP server:

claude mcp add scout --transport http <SCOUT_URL>/mcp/v1

This opens an authentication window in your browser. After logging in, the connection is established automatically.

Authenticate inside Claude Code:

/mcp 

Choose Scout and Select Authenticate

Verify the connection:

claude mcp list

To remove:

claude mcp remove scout

Claude Desktop App

Edit the config file at:

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

Add the mcpServers section:

{
  "mcpServers": {
    "scout": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "<SCOUT_URL>/mcp/v1",
        "--static-oauth-client-metadata",
        "{\"scope\":\"\",\"client_uri\":\"http://localhost\"}"
      ]
    }
  }
}

Restart the Claude Desktop app. On first connection, a browser window opens for authentication.

Gemini CLI

Edit ~/.gemini/settings.json:

{
  "mcpServers": {
    "scout": {
      "httpUrl": "<SCOUT_URL>/mcp/v1",
      "oauth": {
        "scopes": []
      }
    }
  }
}

Run gemini and the OAuth flow starts automatically on first use.

Verify the Connection

Once connected, ask your coding agent a simple question:

What services are running in my environment?

The assistant should use Scout's MCP tools to query your observability data and return a list of services.

If you run into issues, contact the base14 team.

Finding Your Scout URL

Replace <SCOUT_URL> in the examples above with your organization's Scout MCP base URL. It follows this pattern:

https://<your-org>.api.<region>-scout.base14.io

For example, if your organization is acme and your region is as1, your Scout URL would be:

https://acme.api.as1-scout.base14.io

And the full MCP endpoint:

https://acme.api.as1-scout.base14.io/mcp/v1

note

This host serves MCP only. The Scout HTTP API is on a different URL, with your organization as a path segment rather than a subdomain — see the API quickstart for how to discover it.

If you are unsure about your organization name or region, check with your team or contact the base14 team.