TDD-MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TDD_MCP_LOG_LEVEL | No | Logging verbosity - debug|info|warn|error | info |
| TDD_MCP_SESSION_DIR | No | Custom session storage directory | .tdd-mcp/sessions/ |
| TDD_MCP_USE_MEMORY_REPOSITORY | No | Use in-memory storage for testing | false |
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
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| start_sessionA | Start a new TDD session. Args: goal: High-level session objective and definition of done test_files: Files where agent can write tests (explicit paths) implementation_files: Files where agent can write implementation run_tests: Commands/instructions for running test suite custom_rules: Additional rules appended to global TDD rules Returns: Session ID of the created session |
| update_sessionC | Update an existing active session. Args: goal: Updated session objective (optional) test_files: Updated test files (optional) implementation_files: Updated implementation files (optional) run_tests: Updated test commands (optional) custom_rules: Updated custom rules (optional) Returns: True if update was successful |
| resume_sessionA | Resume an existing session by session ID. Args: session_id: Unique identifier for the session to resume Returns: Current state of the resumed session |
| pause_sessionB | Pause the current active session. Returns: Session ID of the paused session |
| end_sessionA | End the current active session and return summary. Returns: Summary of the completed session |
| next_phaseA | Move to the next phase in the TDD cycle. Args: evidence_description: Description of what was accomplished to justify transition Returns: New session state after phase transition |
| rollbackC | Rollback to the previous phase. Args: reason: Reason for rolling back Returns: New session state after rollback |
| get_current_stateA | Get current state of the active session. Returns: Current session state with all properties calculated |
| logA | Add a log entry to the current session without affecting workflow state. Args: message: Log message to add to session history Returns: True if log entry was successfully added |
| historyB | Get formatted session history for the current active session. Returns: List of formatted history entries |
| quick_helpA | Provide context-aware shortcuts and help based on current session state. Returns: Dictionary with context-aware help and shortcuts |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| initialize | Provide comprehensive TDD-MCP usage instructions for new agents. |
| start_session_wizard | Wizard to refine the goal and prepare parameters for start_session tool call. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 11 tools
Each tool has a clearly distinct purpose covering session lifecycle, state queries, phase transitions, and logging. No two tools overlap in functionality.
Most tools follow verb_noun pattern but 'history', 'log', 'rollback', 'next_phase', and 'quick_help' break the pattern. However, naming is still readable and generally predictable.
With 11 tools covering session management, phase control, and auxiliary helpers, the count is well-suited to the domain—neither sparse nor bloated.
Core session lifecycle (start, end, pause, resume, update, phase transitions) is fully covered. Missing a 'list_sessions' tool but this is a minor gap.