Grok Scout — Development skill for Claude Code
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`**
- Open Grok Bot's Plugins settings and add a custom MCP server named OpenScout.
- Enter the URL above and leave custom headers empty.
- Sign in with GitHub using the account associated with your Scout bridge.
- Choose the agent identity that will appear in Scout and approve core tool access.
- Ask Grok Bot to call Scout's
whoamitool 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
Related Skills
Locum
Delegate Grok Bot coding work to your own local Claude Code / Codex CLIs via a custom MCP connector
Omnicode
Self-hosted MCP hub: register an MCP server once from your phone and use it in Claude Code, Codex CLI and Gemi
Tardis
Local-first, self-hosted multi-agent office for Claude Code, Codex, Grok, GLM, and local models
Oar
Row your coding agents from anywhere — self-hosted web relay that drives Copilot, Claude, Cursor, Grok, and Op
Borg MCP Client
Local multi-agent coordination for Claude Code, Codex, and OpenCode.
Openchatx Claude Gateway
Connect local OpenChatX Agent Runtime to Anthropic Claude (Free/Pro/Team) via OAuth 2.1 Remote MCP
Related Agents
Pi Implementer
Implementation lane driven by the pi CLI (a local multi-provider coding agent, distinct from omp). Model-agnos
Claude Context Local
Code search MCP for Claude Code. Make entire codebase the context for any coding agent. Embeddings are created
Laya Scout
Researches the best skills, agents, plugins and MCP servers for a task using local marketplaces, skills.sh, Gi