MCP Tools

Kodebase provides MCP (Model Context Protocol) tools that enable AI assistants to interact with your project artifacts.

Scout Tools

Scout tools handle project planning and specification.

scout_start_session

Start a new planning session to transform an idea into a spec.

Parameters:

• idea (required) - The raw idea in natural language
• domain (required) - Domain slug for the spec directory
• projectContext (optional) - Project context for smarter questions
• workspacePath (optional) - Path for writing draft files

Example:

{
  "idea": "Add user authentication with email/password",
  "domain": "user-auth"
}

scout_submit_answers

Submit answers to clarifying questions.

Parameters:

• sessionId (required) - Session ID from scout_start_session
• answers (required) - Array of question-answer pairs

scout_validate_spec

Validate spec completeness before approval.

Parameters:

• sessionId (required) - Session ID
• sections (optional) - Specific sections to validate

scout_generate_artifacts

Generate artifact templates from the approved spec.

Parameters:

• sessionId (required) - Session ID
• artifactTypes (optional) - Which artifacts to generate
• format (optional) - Output format (yaml, markdown, both)

scout_get_guidance

Get phase-appropriate guidance for the current session.

Parameters:

• sessionId (required) - Session ID
• topic (optional) - Specific guidance topic

scout_update_draft

Update draft content and manage phase transitions.

Parameters:

• sessionId (required) - Session ID
• content (optional) - Updated draft content
• phase (optional) - Target phase to transition to

Sherpa Tools

Sherpa tools handle implementation guidance and workflow.

sherpa_get_status

Get work status including ready issues and in-progress work.

Parameters:

• initiative_id (optional) - Filter by initiative

Returns:

• ready_issues - Issues ready to start
• in_progress - Current active work
• completable - Artifacts ready to complete

sherpa_get_context

Get full context for implementing an issue.

Parameters:

• issue_id (required) - Issue ID (e.g., A.1.1)

Returns:

• Issue details with acceptance criteria
• Parent milestone and initiative context
• Spec references
• Implementation guidance

sherpa_get_guidance

Get general implementation guidance.

Parameters:

• topic (required) - Guidance topic
• artifact_id (optional) - Artifact for context

Topics:

• quality_gates - Quality gate commands
• completion_flow - How to complete artifacts
• pr_template - PR description template
• implementation_notes - implementation_notes format
• delivery_summary - delivery_summary format
• impact_summary - impact_summary format

sherpa_start_issue

Get detailed instructions for starting work on an issue.

Parameters:

• issue_id (required) - Issue ID to start

Returns:

• Issue details
• Step-by-step instructions
• Command to run (kb start)
• Next steps checklist

sherpa_pre_submit_checklist

Get pre-submit checklist for an artifact.

Parameters:

• artifact_id (required) - Artifact ID

Returns:

• Structured todos ready for TodoWrite tool
• Completion field format (implementation_notes, etc.)
• Whether completion field exists

Kodebase Config Tools

kodebase_get_config

Read Kodebase configuration.

Parameters:

• project_root (optional) - Project root path

Returns:

• Current preset
• Settings
• Effective configuration
• Quality gates

kodebase_update_config

Update Kodebase configuration.

Parameters:

• path (required) - Config path to update
• config (required) - Configuration object
• project_root (optional) - Project root path