herdr-mcp
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
herdr-mcp
Let ChatGPT, Grok Bot or another compatible assistant work with agents running on your own always-on machines.
herdr-mcp connects your AI client to Herdr Core, Herdr TUI, or both. From a chat, you can:
Find your running agents and see what they are doing.
Send a task, wait for it and read the result.
Start a new program on a chosen machine.
Read completed Pi replies without terminal borders or wrapped lines.
One MCP connection can reach the remote machines already configured in Core, using the same machine catalogue as Shepherdr. You do not need a separate MCP endpoint on every machine. Your machines must stay awake and connected.
Have your agent set it up
This gives the connected client shell-equivalent access, including Core's configured remote machines. It can launch programs and submit commands. This is not a sandbox. Only connect clients you trust, and consider a dedicated runtime session or OS account for separation.
Give an agent with terminal or SSH access to the machine hosting Herdr this prompt:
Read https://github.com/IgorWarzocha/herdr-mcp/blob/main/SETUP.md and set up herdr-mcp for me. Inspect my environment first, explain the requirements and access risk, and help me choose a compatible client and connection route. Install and configure it, preserve existing services, and verify the selected client can list my agents and read output. Stop for account logins or administrator approvals. Keep credentials out of chat and tracked files.
Your agent handles installation, the background service, connection settings and checks. You handle account logins, administrator approvals and the decision to grant access. You do not need to write code.
For ChatGPT, the agent configures OAuth and approves the connection from the bridge host. Your bridge credential never goes into ChatGPT or its browser form. Access tokens refresh automatically; reapproval is needed after 30 days without a refresh, or after revocation. See ChatGPT setup.
For Grok Bot and other bearer-token clients, put the existing token directly into the client's protected credential field. Never paste it into a chat. Client instructions cover ChatGPT, Grok Bot and Cursor. Other clients need compatible remote MCP and authentication support.
Related MCP server: herdmcp
What you need
A Linux, macOS or Windows machine with Herdr Core 0.1.14+ or Herdr TUI 0.9.5+, and Node.js 26.12.1+. TUI also needs Pi available for the deployment check. Your setup agent checks these prerequisites before proceeding.
A compatible MCP client using Streamable HTTP with OAuth or a bearer header. ChatGPT and Grok Bot have been tested live.
An HTTPS connection route. Hosted clients such as ChatGPT and Grok Bot need a publicly reachable endpoint. Tailscale Funnel can provide one without buying a domain; Cloudflare Tunnel uses a domain you manage. Private Tailscale access works only when the actual MCP client is on your tailnet, not merely the laptop displaying its chat.
Background setup uses systemd on Linux, launchd on macOS, or WSL2 with systemd on Windows. Native Windows can run the bridge in the foreground. Your agent can help choose the route and install missing prerequisites with your approval.
Use it from a chat
Once connected, try:
Read herdr_skill, then show my running agents.
Then ask it to send a task to a specific agent, check output, or start a program on a named machine. Names and new programs default to the local machine. Remote commands use --machine <name-or-ID>; the control guide explains the syntax.
Sending a task confirms delivery, not completion. Ask the client to wait and read the result. A wait can time out while the agent keeps working; that is not a reason to send the task again. Hosted clients may have shorter time limits than the bridge. See wait behaviour.
Modern clients can receive directory-change notifications. These do not guarantee that a client wakes up or starts another model turn. ChatGPT's separate MCP Events webhook integration is not implemented here.
Manual setup and troubleshooting
Follow SETUP.md for the ordered setup, platform recipes for service commands, and SKILL.md for control commands and recovery.
Terminal output can contain private information, and malicious prompts can steer an agent into misusing its access. Keep credentials out of chat, screenshots and committed files. If a bearer token leaks, replace it and update its clients. OAuth connections can be revoked separately. Remove only this bridge's public route when you no longer need it, preserving other services.
Licence
MIT © Igor Warzocha
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
Remote MCP server for supportsheep: run AI interviews and manage support content for your blog.
Remote MCP server for supportsheep: run AI interviews and manage support content for your blog.
Secure and manage MCP servers through the Speakeasy AI Control Plane from your agent.
Remote MCP server exposing your Node Command fleet (files, shell, processes, browser) to AI hosts.
Related MCP Servers
- AlicenseBqualityBmaintenanceEnables MCP clients to remotely control a running Herdr session: see agent status, arrange tabs and panes, start and prompt coding agents, and run worktree-isolated jobs over stdio or Streamable HTTP. Includes policy controls such as allowlists, read-only mode, disabled tools, and an audit log.322MIT
- AlicenseNot gradedqualityCmaintenanceLets MCP clients such as Claude Code, Cursor, and Claude.ai inspect and drive herdr workspaces, panes, and coding agents over a local socket, running either as a local stdio process or as an OAuth-protected HTTP endpoint published through a Cloudflare Tunnel. It exposes tools to create workspaces and tabs, split panes, start and prompt agents, read their output, and wait for results.MIT
- AlicenseBqualityCmaintenanceEnables MCP clients to observe and control a running Herdr session by inspecting panes, agents, layouts, and live lifecycle events, and by prompting agents, waiting for completion, running commands, and managing workspaces, tabs, panes, and worktrees.411MIT
- AlicenseNot gradedqualityCmaintenanceConnects an MCP client such as Codex to a running DeepSeek Harness instance, letting it start or continue workspace conversations as delegated tasks, poll task status, answer intercepted questions, and cancel turns. Agent progress, findings, and blockers flow back to the coordinator through a durable on-disk mailbox.MIT