Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@herdr-mcp Read herdr_skill, then list my panes."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Let an AI agent read and send messages to Herdr terminal panes on your own machine.
herdr-mcp connects Grok Bot, Cursor cloud agents, Cursor desktop and other MCP clients to a running Herdr session. Ask your agent to list your agents, check their output, send a task or wait for a status change. You can follow work from a remote client without sitting at the terminal.
It is for people who already use Herdr and want to give an agent remote access. Your Herdr machine must stay awake and connected.
If you want to keep chatting with an agent while it works, SSH into the machine and use Herdr directly. If you want a remote agent to wait for a result before continuing its own task, use the MCP connection.
Coding tasks take minutes, not seconds. Each MCP wait lasts up to 90 seconds by default. If it returns wait_timeout, read the screen when looking for a reply: an answer can be visible while the agent is still working. If you still need the result, repeat the wait with the same timeout until it is ready or your overall deadline is reached. Otherwise, carry on with other work and check back later.
The wait limit is configurable for local clients or others that tolerate longer calls. Hosted clients can impose their own shorter deadline. See client timeout settings.
Related MCP server: @chitmark/haven-mcp
Herdr 0.9 or later, with its server running.
Node.js 22 or later on the same machine.
Linux, macOS or Windows. Background setup uses systemd on Linux, launchd on macOS, or WSL2 with systemd on Windows. Native Windows can run the bridge in the foreground.
An MCP client that supports Streamable HTTP and a custom bearer-token header. A client that requires OAuth without custom headers is not supported.
A connection route:
Tailscale Funnel: a public HTTPS address without buying a domain. Requires a Tailscale account and permission to enable HTTPS and Funnel.
Cloudflare Tunnel: a public HTTPS address on a domain you manage through Cloudflare.
Tailscale-only: private access when the MCP client itself is on your tailnet. Having Tailscale on your laptop does not put a hosted agent's backend on it.
The agent will help you choose. You do not need both tunnel providers.
The token gives shell-equivalent access as the user running Herdr. A connected agent can read what is on screen and type commands into panes. This is not a sandbox.
A malicious prompt or document can steer an agent into using that access.
Terminal output may contain passwords, keys or private work.
Public tunnels make the endpoint reachable from the internet. The token protects access.
A hosted client stores or handles your token. You are trusting that provider too.
Use a dedicated Herdr session for remote agents. For stronger separation, use a separate OS account without access to sensitive files. Keep the token out of chat, screenshots and committed files. If it leaks, revoke and replace it, then update your clients. Disable this bridge's tunnel route when you no longer need it, without disturbing other services.
Give a coding agent with terminal access to your Herdr machine this prompt:
Read https://github.com/IgorWarzocha/herdr-mcp/blob/main/SETUP.md and follow its setup flow. Inspect my environment first, explain what I need, and ask which tunnel and MCP client I want. Set it up with a check after each step. Stop for human-only actions, preserve existing services, and give me the connector settings without putting the token in chat.
The agent handles installation, service configuration, the selected tunnel and connection checks. You handle account logins, administrator approvals, accepting the access risk and pasting the token into your client. It will tell you when one of those steps is needed.
Once connected, ask:
Read herdr_skill, then list my panes.
Sending a message confirms delivery, not that the agent has finished. Ask it to read the response afterwards. Waiting tracks agent state rather than a particular message.
For manual setup or troubleshooting, see the setup walkthrough, platform recipes and usage and error guide.
MIT © Igor Warzocha
This server cannot be deployed
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.
Hosted MCP server for task-first delegation to remote workstations and workers.