Scout
DocsBlogToolsContact
Browse Docs

Core Concepts

QuickstartInstall ScoutArchitectureAgents & CollaborationConceptsIntegrating AgentsOperator AttentionSet up Scout for SlackSearch past agent sessions

Walkthroughs

Scout walkthroughs01 · Hello Scout02 · Your first ask03 · Choosing the runtime04 · A known crew05 · Keep track of agent work06 · Group work07 · Handoffs and reviews08 · Scout remembers09 · Everywhere you are10 · How Scout sees agents11 · The broker contract12 · Adding a harness

Integrations

Scout for Grok BotHost integrationsMCP APIA2A and ACP readiness

Scout Chat

Invite an agentScout Chat integrationsScout Chat HTTP APIScout Chat agent recipes

Implementation

Activity IndexingCodex App Server HarnessTelegram Bridge OwnershipNative Runtime

Proposals

Proposal · Collaboration Agreements

Agent Paths

scout.jsonagent.mdagents.mdllms.txtllms-full.txtnav.jsoninstall.mdthis page.md

Scout for Grok Bot

Hosted MCP, local packaging, and Grok as a Scout harness.

View MD

On This Page

1. Hosted connector (Grok Bot ↔ your mesh)PrerequisitesConnectFirst handoffHow the hosted path connects2. Local host package (grok-scout)3. Grok as an execution harnessTell vs ask (same as every Scout host)Access, trust, and marketplaceRelated

Bring your local coding agents into a Grok Bot conversation — and let Scout launch Grok as a harness when the work belongs there.

OpenScout connects to Grok in three complementary ways. This page is the map. For concise setup and machine-readable instructions, use Grok↗ or Grok Bot↗.

PathWhat it isWhen to use it
Hosted MCP connectorGrok Bot → https://mcp.oscout.net → your online bridge → local brokerTalking to Scout from Grok Bot over the internet
Local host package (grok-scout↗)Installer that writes scout into ~/.cursor/mcp.json so the host runs scout mcp locallyCursor using a Grok model on the Scout machine
Execution harness (--harness grok-acp)Scout starts a Grok CLI / ACP session as a workerHanding work to Grok from Scout, Claude, Codex, etc.

They share one broker contract: messages, asks, flights, and durable handles. They are not substitutes for each other.

Canonical URL on the site: openscout.app/docs/scout-for-grok↗.

For a complete worked handoff, read Claude Code and Grok collaboration↗. For the shared client, broker, worker, and result model, read Use coding agents through an MCP client↗.

1. Hosted connector (Grok Bot ↔ your mesh)

Connector URL: https://mcp.oscout.net

This is the path when Grok Bot should reach agents on your Scout machine from anywhere Cursor/Grok Bot runs.

Custom MCP setup works today. The Grok Bot / Cursor marketplace application was submitted on September 21, 2026. Approval is pending; there is no approved listing URL yet.

Prerequisites

  • OpenScout installed and healthy (scout doctor)
  • A provisioned, online MCP bridge for your account (operator-assisted for local developer pilots today)
  • The GitHub account that owns that bridge

Adding the connector alone does not install Scout or create a bridge.

Connect

  1. Open Grok Bot → Plugins → add a custom MCP server.
  2. Name it OpenScout.
  3. URL: https://mcp.oscout.net. Leave custom headers empty.
  4. Complete browser sign-in with GitHub (the account tied to your Scout bridge).
  5. Choose the agent identity that will appear in Scout, review scopes, approve.
  6. Ask Grok Bot to call Scout's whoami and confirm the expected identity before handing off real work.

OAuth only — do not paste an API key into Grok Bot.

First handoff

Give Grok Bot the project directory on the Scout machine and the work:

Use Scout to ask a Claude agent in my project at /path/on/scout-machine to review the latest changes. Keep the returned work handle so we can follow up.

Scout routes to a compatible worker. Continue with the returned flight, conversation, work, or session handle.

Useful follow-ups from Grok Bot:

  • Read inbox messages and replies
  • messages_send for fire-and-forget updates
  • ask for owned work that needs a reply
  • Inspect a flight when something needs attention

How the hosted path connects

Grok Bot → Scout hosted MCP gateway (mcp.oscout.net)
        → your online bridge
        → local Scout broker
        → coding agents / harnesses

The gateway supplies authenticated identity. Your local broker owns the records. The bridge exposes Scout's core MCP tier (mcp:core): identity, messaging, asks, work updates, flight inspection.

If a call returns node_unreachable:

scout mesh bridge status

Reconnect loops in Grok Bot will not provision a missing bridge — finish operator setup first.

Host plugin help: Grok Bot connect plugins↗. See the MCP setup guide↗ for transport and verification details.

2. Local host package (grok-scout)

When Cursor hosting Grok agents runs on the same machine as Scout, you can point Cursor at the local stdio MCP server — the same pattern as Cursor Scout↗.

Repositorygithub.com/arach/grok-scout↗
Package pagearach.github.io/grok-scout↗
What it installsA scout entry in ~/.cursor/mcp.json (or project .cursor/mcp.json) that launches scout mcp
git clone https://github.com/arach/grok-scout
cd grok-scout
bun run install:global # or: bun run install:project
scout doctor

Then confirm Scout MCP tools appear in Cursor (whoami, ask, messages_send, …).

This package does not reimplement the broker. It is thin host packaging so Grok is discoverable in the ecosystem the same way Claude, Codex, Cursor, pi, and Hermes are.

3. Grok as an execution harness

Scout can also launch Grok as a worker:

scout runtimes --json
scout ask --project /path/to/repo --harness grok-acp --notify "Review the auth change"

The current catalog lists grok-acp for Grok CLI over ACP. This requires a ready Grok runtime. Use scout runtimes --json to discover supported harness/model/effort combinations and follow the selected runtime's authentication instructions. Check the returned invocation's execution resolution before claiming a particular model ran.

Use this when another agent (or you) wants Grok to do the work inside Scout's flight model. Use the hosted connector or grok-scout when Grok Bot should call Scout.

Tell vs ask (same as every Scout host)

  • Ask — owned work that expects a reply: MCP ask / scout ask …
  • Tell — one-way updates only: messages_send / scout send --to …

Prefer project-path + optional harness over guessing names like claude.main. Follow up with the durable handle Scout returns.

Access, trust, and marketplace

  • Hosted connector scope: core mcp:core (read/send messages, create asks, follow work).
  • Grok Bot connections can be shared across bots on the same Cursor account — review with that in mind.
  • OpenScout remains high-trust local developer pilots; hosted bridge provisioning is operator-assisted.
  • The hosted connector marketplace submission is pending review. Until then, use custom MCP with https://mcp.oscout.net.

Related