harness-homies
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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_sessionsA | List coding-agent sessions on this machine across Claude Code, OpenCode, Cursor, and Codex — what's running, its topic, and its status. Read-only. |
| get_sessionA | Get a single session's title, cwd, status, todos, and message count. Use the agent and id fields from a list_sessions/search_sessions result. Read-only. |
| get_transcriptA | Fetch a session's transcript, paginated (most recent messages by default). Secrets are redacted unless raw is set. Use the agent and id fields from a list_sessions/search_sessions result. Read-only. |
| search_sessionsA | Search session titles (and recent transcript content) for a substring across one or all agents. Read-only, case-insensitive. |
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 4 tools
Each tool targets a distinct concern: listing all sessions, retrieving one session's metadata, fetching a transcript, and searching across sessions. The overlap between list_sessions and search_sessions is minimal and clearly differentiated by behavior.
All tool names follow a consistent verb_noun snake_case pattern: list_sessions, get_session, get_transcript, search_sessions. The naming is predictable and instantly readable.
Four tools is well-scoped for a read-only session inspection server. Each tool covers a distinct aspect of the domain without redundancy or missing essentials.
For a read-only monitoring tool, the surface is complete: discover sessions, inspect one session, read its transcript, and search across sessions. No obvious lifecycle operations are expected here, so there are no meaningful gaps.