MCP Server

Your best work doesn't all happen in one place. You're in Cursor, Claude Code, or Codex, and Scout is where your agents, automations, and data live. Until now, connecting the two meant custom glue code or a local server to manage.

Not anymore. Scout now has an official, hosted MCP server. Any MCP-compatible client can connect straight to Scout and work with your resources through standard tool calls, so your agents can run a workflow, query a database, or pull a file from Drive without ever leaving the tool you’re already in.

Because it’s hosted by us, there’s nothing to install, run, or keep up to date. And every connection is secure by default, scoped to exactly what your token is allowed to do.

Getting connected

Point your client at the endpoint https://mcp.scoutos.com/mcp and authenticate with your Scout token:

Authorization: Bearer YOUR_SCOUT_TOKEN

Setup takes about a minute in Claude, Claude Code, Codex, Cursor, VS Code, and v0. Here are a couple of examples. In Claude Code, one command adds the server:

claude mcp add --transport http scout https://mcp.scoutos.com/mcp

Or drop this into Cursor, VS Code, or any client that takes JSON config:

{
  "mcpServers": {
    "scout": {
      "url": "https://mcp.scoutos.com/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_SCOUT_TOKEN"
      }
    }
  }
}

Full per-client instructions and verification steps live in the setup guide.

What you can access

Once connected, your client discovers Scout’s tools automatically. From there, you and your agents can:

• Workflows — list, create, and run your Scout workflows
• Agents — list, upsert, and chat with your agents
• Databases — create and inspect collections, tables, and views
• Documents — create, update, and batch-edit table records
• Triggers — list, create, update, and fire triggers
• Drive — upload and download files

Grab a token from your API key settings, point your client at the endpoint, and you’re live.

We can’t wait to see what you and your agents build with it.