What you get
Tell Claude Code, in plain English:“Make a pull story explaining the auth flow in this repo.”It will:
- Identify the relevant files
- Read the meaningful line ranges
- Build a concise structured brief
- Call the pull/story MCP tool
- Paste the pull story URL back into your chat

Setup (2 minutes)
Get an API key
Visit pullstory.com/dashboard/api-keys → Create key.
Add the pull/story MCP server
Create or edit On native Windows, use
.mcp.json in your project root:.mcp.json
"command": "cmd" and "args": ["/c", "npx", "-y", "@pullstory/mcp@latest"].Available tools
Once the MCP is wired up, Claude Code has access to these tools:Generate a pull story from a structured code brief. Returns the story URL.
Check the generation status of an existing pull story.
Natural-language triggers
Any of these phrasings will typically trigger the tool:- “make a video explaining this feature”
- “create a pullstory for auth”
- “visualize this flow”
- “walk me through how this code works”
- “turn this branch into a pullstory”
Troubleshooting
Claude Code doesn't see the MCP server
Claude Code doesn't see the MCP server
Run
/mcp inside Claude Code to list active servers. If pullstory is missing, check .mcp.json for JSON errors and restart.'Unauthorized' error
'Unauthorized' error
'Brief failed schema validation'
'Brief failed schema validation'
The generated brief is missing required fields or includes oversized excerpts. Ask Claude Code to use fewer files and tighter excerpts.
Next
MCP setup details
Works with Cursor, Windsurf, Claude Desktop too.
Full workflow cookbook
Step-by-step example with real output.