Public Streamable HTTP MCP endpoint

Connect agents to Scout OS.

A stateless MCP proxy for Scout. Bring Scout agents, tables, collections, documents, workflows, triggers, and drive files into MCP-compatible clients without putting private keys in chat.

Stateless by design

The service forwards your Scout Authorization header to Scout OS. It does not store credentials or register accounts.

JWT recommended

Sign short-lived JWTs locally. Your private key stays in your runtime, keychain, or secret manager.

Tool coverage

Use the grouped Scout MCP tools from one endpoint.

agentstablescollectionsdocumentsworkflowstriggersdrive

Connect in three steps.

Use values from studio.scoutos.com/settings/api-keys. The private key is base64url DER and must be converted to PEM before JWT signing. The JWT kid is the SHA-256/RFC 7638 thumbprint of the public key; the credential id is your workspace id.

Copy key material locally

Store SCOUT_PRIVATE_KEY, SCOUT_PUBLIC_KEY, and SCOUT_CREDENTIAL_ID outside your agent prompt.

Generate a signed JWT

Use the TypeScript helper in the repo to convert DER to PEM, compute kid, and mint a 5-minute RS256 token.

Configure your MCP client

Set the server URL to https://scout-mcp-service.onrender.com/mcp and send Authorization: Bearer <jwt>.

Claude Code config

Add the Scout MCP service as an HTTP MCP server. Generate SCOUT_AUTHORIZATION locally before launching your client.

{
  "mcpServers": {
    "scout": {
      "type": "http",
      "url": "https://scout-mcp-service.onrender.com/mcp",
      "headers": {
        "Authorization": "Bearer ${SCOUT_AUTHORIZATION}"
      }
    }
  }
}