Skip to main content
Glama

hermes-conductor-mcp

MCP server that exposes Conductor Cloud as tools for Hermes Agent, so Hermes (running as your Telegram brain) can dispatch real coding work to Conductor's sandboxed developer agents.

Telegram  <->  Hermes Agent (brain)  <->  this MCP server  <->  Conductor Cloud (dev agents)

Tools exposed

  • list_projects — repos available to create a workspace from

  • create_workspace — spin up a sandboxed workspace + first session (agent: claude | codex | cursor | acp)

  • get_workspace_status — poll workspace lifecycle (initializing → ready → ...)

  • archive_workspace — tear a workspace down when done

  • send_message — send an instruction/prompt into a coding session

  • get_session_status — poll whether the agent is idle | working | error

  • get_session_messages — read the full transcript

  • cancel_session — stop the agent mid-task

Typical flow a Hermes conversation would drive: list_projects → create_workspace → send_message (the task) → poll get_session_status until idle → get_session_messages for the result → archive_workspace.

Related MCP server: hermes-claude-bridge

Setup

  1. Get a Conductor API key (requires Conductor Pro): https://app.conductor.build/users/api-keys

  2. Install and build:

    npm install
    npm run build
  3. Register it in Hermes's ~/.hermes/config.yaml:

    mcp_servers:
      conductor:
        command: "node"
        args: ["/Users/rohanarora/Desktop/hermes-conductor-mcp/dist/index.js"]
        env:
          CONDUCTOR_API_KEY: "<your conductor api key>"
  4. Restart Hermes. It should discover tools prefixed mcp_conductor_* (e.g. mcp_conductor_create_workspace).

  5. Make sure Hermes's Telegram gateway is already configured (BotFather token + your user ID) — see https://hermes-agent.nousresearch.com/docs/user-guide/messaging/telegram. That part is independent of this server.

Local dev

CONDUCTOR_API_KEY=sk-... npm run dev

Runs the server directly via tsx over stdio — pair with any MCP inspector/client to test tool calls without going through Hermes.

Available Tools

8 tools
archive_workspaceA

Archive (deactivate) a Conductor workspace once its work is done.

Inputs: workspaceId (required).

cancel_sessionC

Cancel/stop the agent's current operation in a session.

Inputs: sessionId (required).

create_workspaceA

Create a new Conductor workspace (a sandboxed coding-agent environment) and start a session in it. Provide either projectId (existing repo already connected to Conductor) or repositoryUrl.

Inputs: agent (required), name, model, branch, +4 more.

get_session_messagesC

Retrieve the full conversation transcript for a coding agent session.

Inputs: sessionId (required).

get_session_statusA

Poll whether a coding agent session is idle, working, or errored. Poll this after send_message to know when the agent finished.

Inputs: sessionId (required).

get_workspace_statusA

Check the lifecycle status of a Conductor workspace (initializing, ready, sleeping, archived, deleted, updating).

Inputs: workspaceId (required).

list_projectsB

List repositories available to create Conductor workspaces from.

Inputs: no named parameters.

send_messageA

Send a prompt/instruction to a coding agent session. Use the sessionId returned by create_workspace.

Inputs: message (required), sessionId (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.7/5.0

    Scored across 8 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action: projects, workspaces, sessions, and operations on them. No two tools appear to overlap in purpose, making selection unambiguous.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern in snake_case (e.g., list_projects, create_workspace, send_message). This creates a predictable and readable interface.

    Tool Count5/5

    With 8 tools, the server covers workspace lifecycle and session management without bloat. Each tool serves a clear need, and the count is well within the ideal range.

    Completeness4/5

    The surface covers workspace creation, status, archiving, session messaging, polling, transcripts, and cancellation. A notable gap is the lack of a list_workspaces tool to enumerate existing workspaces, but core workflows are otherwise complete.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers