Scout
DocsBlogToolsContact
Scout + Grok Bot● Grok Bot asks an agent

Your coding agents.In Grok Bot.

From a Grok Bot chat, hand work to the coding agents on your Mac.

Invite-only pilot · you need an operator-provisioned bridge · Cursor Marketplace review pending (submitted 2026-09-21)

Use supported agents you have installed, authenticated and connected.

Set it upLet your agent do itGrok Bot reads the setup for you
Grok Bot

Ask my Scout agents to review the open PR in ~/dev/app.

  • Used scout · askworking…on it
  • Used scout · invocations_waitworking…reply ready

Claude Code reviewed the PR. 1 finding:

  1. src/sync.ts:57 the retry loop never clears its timer.
Message Grok Bot
+

Grok Bot calls Scout

Pilot

MCP (hosted) · pilot

Connect Grok Bot ↓

Scout runs Grok Bot

No

scout ask --harness grok-acp launches the Grok CLI, not this connector

Replies reach your open session

Not documented

The guide doesn't say. Follow the returned ref.

01

Start here

  1. 01 · Connect

    Get one route working

    Check the prerequisites and access gates, then get one documented route working before asking for work.

    Follow the setup →
  2. 02 · Try

    Your first useful task

    Once access is provisioned, ask Grok Bot to have a coding agent explain one function in a specified project.

    Name the project and keep the request small. Asking for no edits describes the task; it does not restrict the agent’s permissions.

  3. 03 · Read

    Wait for the answer

    Keep the returned reference. Check the work’s status and read the completed response; a queued receipt is not the answer.

    Check what success looks like →

Before your next ask

Where will the reply appear?

Keep the returned reference and retrieve the completed response through your configured Scout interface. Automatic delivery into this open session is not established by this guide.

What if the answer hasn’t arrived?

Inspect the existing task before submitting another one. A wait timeout does not establish that work failed. If it needs access or input, resolve that condition before continuing.

How do I follow up?

Continue using the returned reference or exact session handle supported by this integration. Keep it with the findings so your next question follows the same work.

Can Scout run this integration, or only receive asks from it?

These are separate capabilities. Check the supported directions on this page. Connection alone does not establish that Scout can launch the integration or reach an existing session.

02

Set it up

Fastest

Give this to Grok Bot

Connect yourself to Scout for me. Read openscout.app/grokbot/agents.md and follow it step by step: check the prerequisites first, ask me before any step that needs a token or other credential, and finish with its verification step. Tell me what you verified.

  1. reads agents.md
  2. checks prerequisites
  3. asks before any credential
  4. runs the verification

You need

  • Before you start: this connector reaches a Scout broker on a specific machine through a bridge that the Scout operator provisions for your GitHub account. There is no self-serve sign-up yet. If you have not been told your bridge is live, the connector will authorize and then return node_unreachable.
  • Grok Bot with custom MCP support.
  • OpenScout installed and a healthy local broker (scout doctor).
  • A provisioned Scout MCP bridge associated with your GitHub account. Provisioning is currently operator-assisted.
  • The Scout machine and its bridge must stay online. Adding an MCP server does not install Scout or provision a bridge.
calls Scout

Connect Grok Bot

Start here
  1. 01

    Add Scout in Grok Bot

    Open Plugins settings and add a custom MCP server named OpenScout. Enter this endpoint and leave custom headers empty.

    https://mcp.oscout.net
  2. 02

    Authorize the connection

    Sign in with the GitHub account associated with your provisioned bridge. Choose your Scout agent identity and approve core tool access.

  3. 03

    Verify before delegating

    Ask the client to list Scout tools, then call whoami. Confirm that the identity belongs to your intended Scout account before requesting work.

  4. 04

    Make your first handoff

    Ask Grok Bot: “Use Scout to ask a Claude agent to review the latest changes in /absolute/path/to/project. Do not edit files. Keep the work handle and report the result.” The directory is on your Scout machine.

03

Done when

  • Call whoami first.
  • Confirm the expected identity, then run a small ask and follow its returned handle.

Do not treat an accepted invocation as completed work.

04

If it breaks

node_unreachable
On the Scout machine run scout mesh bridge status. Confirm the broker, machine, and bridge are online. If there is no provisioned bridge, stop and contact your Scout operator; repeated OAuth attempts will not create one.
OAuth fails or the wrong identity appears
Check the signed-in GitHub account and connector authorization. Reconnect to the intended account before running tools. Never paste tokens into a chat.
No tools appear
Save the MCP configuration, reconnect, and refresh the client tool list. Confirm HTTP transport and the exact endpoint; do not substitute a local stdio command in a remote client.
05

Where it stops

  • Invite-only: bridge provisioning needs the operator's relay credential. Operators run scout mesh bridge install and scout mesh bridge status on the Scout machine; see /mcp.
  • Because Grok Bot signs in with a Cursor account, connector credentials are shared across bots on the same Cursor account.
  • scout ask --harness grok-acp launches the Grok CLI, not this connector. The Grok CLI execution harness is separate; see /grok.
  • High-trust local developer pilots. Connection traffic may contain project paths, instructions, messages, and agent results. Data and privacy.
06

For agents

agents.mdThe setup contract your agent follows. Same content as this page.integration.jsonDirections, gates and steps as data.