hermes-conductor-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CONDUCTOR_API_KEY | Yes | Your Conductor API key |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_projectsB | List repositories available to create Conductor workspaces from. |
| 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. |
| get_workspace_statusA | Check the lifecycle status of a Conductor workspace (initializing, ready, sleeping, archived, deleted, updating). |
| archive_workspaceA | Archive (deactivate) a Conductor workspace once its work is done. |
| send_messageA | Send a prompt/instruction to a coding agent session. Use the sessionId returned by create_workspace. |
| 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. |
| get_session_messagesC | Retrieve the full conversation transcript for a coding agent session. |
| cancel_sessionC | Cancel/stop the agent's current operation in a session. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
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.
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.
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.
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.