hardline-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HARDLINE_CODEX_CMD | No | Path to the codex executable; overrides auto-discovery | |
| HARDLINE_CLAUDE_CMD | No | Path to the claude executable | |
| HARDLINE_HERMES_CMD | No | Path to the hermes executable, e.g., C:/Users/you/AppData/Local/hermes/hermes-agent/venv/Scripts/hermes.exe |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| sendA | Send a message from one agent to another. Always persists to the durable mailbox. If
|
| inboxA | Read messages addressed to
|
| ackA | Mark a message read so it stops appearing in the unread inbox. Returns |
| historyA | Recent messages, newest first — the visibility / audit feed.
|
| ask_hermesA | Ask the Hermes agent (MrAnderson) a question and wait for its reply. Spawns a one-shot |
| ask_codexA | Ask Codex a question and wait for its reply. Spawns an ephemeral |
| ask_codex_asyncA | Dispatch a Codex task in the background; returns immediately. Runs the same |
| ask_claudeA | Ask Claude Code a question and wait for its reply. With no options, preserves the original one-shot |
| ask_claude_asyncA | Dispatch a Claude task in the background; returns immediately. Runs the same |
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 9 tools
Each tool has a clearly distinct purpose: mailbox operations (send, inbox, ack, history) are separate from asking agents (ask_hermes, ask_codex, ask_claude), and sync vs async variants are clearly differentiated by name. The only potential overlap is among the three ask_* tools, but they target different agents and the descriptions name them explicitly.
Mostly consistent: mailbox tools are single verbs/nouns (send, ack, inbox, history) and query tools follow 'ask_<agent>' with '_async' suffix for background variants. Minor inconsistency is the mix of verb and noun forms for mailbox tools and the absence of 'ask_hermes_async' (which is a completeness gap, not naming), but the overall pattern is readable and predictable.
Nine tools is well-scoped for a messaging and agent-query server. Each tool covers a distinct function without redundancy, and the count is within the ideal 3-15 range.
The core lifecycle is covered: send, read, ack, and history for the mailbox; synchronous ask for all three agents; asynchronous for two of them. Missing async for Hermes and no delete/clear operations are minor gaps that don't severely hamper workflows, but a fully complete surface would include ask_hermes_async and maybe message deletion.