Skip to main content

​
The workflow

You’ve written some code on a branch. You want a PR with a narrated video walkthrough. With the pull/story MCP server installed, this is one sentence to Claude Code.
1

Make sure the MCP is installed

See the Claude Code setup guide if you haven’t yet.
2

In Claude Code, type

Turn my current branch into a PR and give me a pull story
3

Claude Code will

  1. Confirm your branch and the target repo
  2. Run git push -u origin your-branch-name
  3. Run gh pr create --title "..." --body "..."
  4. Call the pull/story MCP tool create_pull_story with the new PR number
  5. Poll get_pull_story every 5 seconds until ready
  6. Paste the URL back into the chat
4

You get

A clickable pull story URL in the chat, ready to share with reviewers or embed in Slack.

​
Example conversation

You: Turn this branch into a PR and give me a pull story. Claude Code: I’ll push your branch feat/payment-retries and create a PR against main in acme/billing. [runs git push, then gh pr create] PR #482 created. Generating pull story… [calls create_pull_story({owner: "acme", repo: "billing", number: 482})] Generating… this usually takes about 90 seconds. Polling… ✅ Pull story ready: https://pullstory.com/pr/acme/billing/482 Duration: 2m 18s · 7 scenes · blast radius: medium

​
Variations

You: Walk me through vercel/next.js PR 56789 Claude Code skips the push/create steps and jumps straight to create_pull_story.
You: Regenerate the pull story for PR 482 Claude Code calls create_pull_story({..., force: true}) to bypass cache.
You: How many pull/story minutes do I have left this month? Claude Code calls get_usage and shows you 73 of 120 minutes remaining.

​
Why this beats copy-pasting diffs

Traditional flow: write code → push → create PR → paste the PR URL into the team Slack → hope someone reviews it → answer 3 rounds of clarifying questions. Pull/story flow: say one sentence → 90 seconds later paste a video link. Reviewers watch 2 minutes and actually understand the change before leaving feedback.

​
Next

GitHub App auto-gen

Install once — skip the “ask Claude Code” step entirely.

Embed pull stories

Drop a pull story inline in docs, changelogs, blog posts.