From cb8577866afc6bace19043c1dea561dec3a7b348 Mon Sep 17 00:00:00 2001 From: Dave Date: Tue, 24 Feb 2026 11:21:05 +0000 Subject: [PATCH] Noted the existence of the mcp server. --- .story_kit/README.md | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/.story_kit/README.md b/.story_kit/README.md index 4621ced..362252d 100644 --- a/.story_kit/README.md +++ b/.story_kit/README.md @@ -9,7 +9,13 @@ When you start a new session with this project: -1. **Check for MCP Tools:** Read `.mcp.json` to discover available programmatic tools. If it exists, you have direct access to workflow automation tools (create stories, spawn agents, record tests, etc.) via the MCP server. +1. **Check for MCP Tools:** Read `.mcp.json` to discover the MCP server endpoint. Then list available tools by calling: + ```bash + curl -s "$(jq -r '.mcpServers["story-kit"].url' .mcp.json)" \ + -H 'Content-Type: application/json' \ + -d '{"jsonrpc":"2.0","id":1,"method":"tools/list","params":{}}' + ``` + This returns the full tool catalog (create stories, spawn agents, record tests, manage worktrees, etc.). Familiarize yourself with the available tools before proceeding. 2. **Read Context:** Check `.story_kit/specs/00_CONTEXT.md` for high-level project goals. 3. **Read Stack:** Check `.story_kit/specs/tech/STACK.md` for technical constraints and patterns. 4. **Check Work Items:** Look at `.story_kit/work/1_upcoming/` and `.story_kit/work/2_current/` to see what work is pending.