arach

Grok Scout — Development skill for Claude Code

Development community

Scout for Grok Bot: hosted MCP and OAuth for local coding-agent coordination.

How to install Grok Scout

This entry records only its repository, not the path inside it, so there is no exact command to give. Open arach/grok-scout and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Grok Scout does

Scout for Grok Bot: hosted MCP and OAuth for local coding-agent coordination.

Alternatives in Development

  • Epic Claim — Claim an epic issue, stamp coordination state, and sync local ownership 243.5k ★
  • AgenticResourceRegistry — Share and discover coding agent resources across your team 4.5k ★
  • Google Ads Meta Ads MCP — Google Ads MCP server + Meta Ads MCP (Facebook Ads MCP) + GA4 + Search Console in one hosted remote MCP for Cl 3.2k ★

README

Scout for Grok Bot

Bring your local coding agents into a Grok Bot conversation. Scout connects Grok Bot to your OpenScout broker so you can delegate work, exchange messages, and follow results from one chat.

[Connection guide](https://openscout.app/grok/) · [OpenScout](https://openscout.app) · [MCP gateway](https://mcp.oscout.net)

Connect

**MCP URL: `https://mcp.oscout.net`**

  1. Open Grok Bot's Plugins settings and add a custom MCP server named OpenScout.
  2. Enter the URL above and leave custom headers empty.
  3. Sign in with GitHub using the account associated with your Scout bridge.
  4. Choose the agent identity that will appear in Scout and approve core tool access.
  5. Ask Grok Bot to call Scout's whoami tool and confirm the expected identity.

The connector uses OAuth; no API key needs to be pasted into Grok Bot. The OpenScout publisher application was submitted to Cursor on September 21, 2026 and is awaiting review. Custom MCP setup is available today.

Requirements

You need OpenScout installed, a running local broker, and a provisioned MCP bridge associated with your account. Your Scout machine and bridge must stay online. Bridge provisioning is currently operator-assisted for local developer pilots; adding this connector does not install Scout or provision a bridge.

If a call returns `node_unreachable`, check your machine and run `scout mesh bridge status` there. Complete bridge provisioning with your Scout operator if no bridge exists.

Try a handoff

Use Scout to ask a Claude agent in /path/to/project to review the latest changes. Keep the returned work handle for follow-up.

The path refers to your Scout machine. For fresh work, pass `projectPath` plus optional `harness` to `ask`. Let the broker route to a compatible worker. Continue by the returned ref, flight, conversation, work, or session handle; do not guess generic agent names.

Use `ask` for work that expects a reply. Use `messages_send` for one-way updates to a known agent o