The Storydoc MCP (Model Context Protocol) integration allows you to connect Claude AI to your Storydoc workspace. This enables you to create, manage, and customize Storydoc presentations directly from Claude's chat interface using natural language commands.
How the Integration Works
Once connected, you can use Claude to perform various Storydoc actions including:
Generate new stories from scratch
Create versions from existing templates
Get analytics data
List available stories
Plan story versions with dynamic variables
Step 1: Add the Storydoc Connector in Claude
Navigate to the Customize section in Claude web or desktop application, then select Connectors.
Click the plus button to add a custom connector. In the dialog that appears, enter "Storydoc" as the name and add the Storydoc MCP URL in the Remote MCP server URL field - https://mcp.storydoc.com/mcp
Click Add to proceed to the connection setup.
Step 2: Generate Your Storydoc API Token
After adding the connector, you'll need to connect it using your Storydoc API token. Click Connect to open the authentication page.
If you don't have an API token yet, click Generate an API token here to create one in your Storydoc workspace. This will open a new dialog where you can create and name your API key.
Give your API key a descriptive name (such as "Claude Storydoc") and set the appropriate scope. Click Create to generate the token.
Copy the generated API key to your clipboard and return to the Claude connection page. Paste the token into the Storydoc API token field and click Connect.
Step 3: Verify the Connection
Once successfully connected, Claude will show the Storydoc connector with all available tools listed. You'll see options like:
storydoc_generate_story
storydoc_create_version
storydoc_get_analytics
storydoc_get_story
storydoc_list_stories
storydoc_plan_version
Step 4: Create Stories Using Natural Language
Return to Claude's main chat interface. You can now use natural language commands to create Storydoc presentations. For example, type "create a Storydoc proposal for Nike" to begin.
Claude will understand your request and begin the Storydoc creation process. It will first check your available templates and stories to suggest the best approach.
Claude will present you with template options and guide you through the creation process, asking for specific details like recipient information and content preferences.
Step 5: Provide Dynamic Variable Information
When creating personalized versions, Claude will ask for dynamic variable values such as:
Recipient's first name
Sender email address
Company information
Any other template-specific variables
You may need to approve Claude's actions the first time you use the integration. Click Always allow when prompted to enable seamless story creation.
View Your Created Story
Once the story is created, Claude will provide you with a direct link to view and edit your new Storydoc presentation. The story will include all the personalized elements you specified, with dynamic variables populated accordingly.
More Things You Can Do with Storydoc in Claude
Beyond creating decks from templates, the integration unlocks your full Storydoc workflow through natural conversation. Here are useful prompts to try.
Generate a Brand-New Deck from Scratch
When no template fits, ask Claude to generate one with Storydoc's AI wizard.
"Generate a Storydoc sales deck for an AI-powered customer support platform targeting mid-market SaaS companies. Bold, confident tone."
"Create a Storydoc investor update covering our Q2 revenue, team hires, and roadmap for SaaS investors."
"Make me a one-pager Storydoc introducing our consulting services to enterprise CTOs."
Claude will collect the key details (audience, message, tone) and call Storydoc's AI wizard to generate the deck from scratch.
Pull Analytics on Your Decks
Ask how a specific deck — or your whole account — is performing.
"How is the Nike proposal performing? Who viewed it and which slides got the most attention?"
"Show me analytics for all my decks in the last 30 days."
"Which of my templates got the most engagement this month?"
"Who viewed the Pfizer deck and from where?"
Claude returns viewer counts, unique visitors, time spent, top slides, device breakdowns, and locations — without you opening the Storydoc dashboard.
Browse Your Templates and Stories
Get a clear picture of what's in your Storydoc account before you create anything.
"List my Storydoc templates."
"Show me my proposal templates and what fields they need."
"What's the most recent template I created?"
"Find me a template for an investor update."
Claude lists your templates with their status, variable fields, and which are template-shaped vs. one-off finished stories.
Create Multiple Personalized Versions
Generate variations of the same template for different prospects in one conversation.
"Use my proposal template to create three decks: one for Nike with recipient Sarah, one for Adidas with recipient Marcus, and one for Puma with recipient Lin."
"Take the Carta proposal template and create versions for these five prospects: [list]."
Claude calls the template for each prospect, fills the variables, and returns a link for each one.
Combine Actions in One Conversation
The real power is chaining actions. Claude remembers what you're working on across turns.
"Create a sales deck for Acme Corp, then tell me how my last three decks have been performing."
"Show me my top-performing template from last month and create a new version of it for Pfizer, recipient Sarah Chen."
"Generate a Storydoc for Nike from scratch, then list my other Nike decks and pull their analytics."
Tips for Better Results
Be specific about audience and tone when generating from scratch — "bold pitch for enterprise CTOs" beats "sales deck."
Mention the recipient by name when personalizing a template — Claude maps it to the right variable automatically.
Use "always allow" the first time you run a tool so future actions don't pause for approval.
Set a default sender once and Claude will use it for every future deck (you'll only need to specify a different sender when generating for a teammate).
You can continue to edit the story directly in Storydoc or return to Claude to create additional versions or perform other Storydoc actions using simple chat commands.
Troubleshooting
Claude doesn't show Storydoc as a connector after I added it.
Quit and reopen Claude (use ⌘Q on Mac, not just close the window). Connectors load on app start.
The OAuth/token connection fails.
Make sure you've generated a fresh API token at Profile → Integrations → Automations. Older tokens may have been revoked. Generate a new one and paste it again.
Claude says it can't find my templates.
Try asking "List my Storydoc templates." If the response is empty, check in Storydoc that you have at least one story in Live status with dynamic variables. Stories in Draft or Archived status are filtered out by default.
Claude creates a deck, but variables aren't filled in.
Make sure the variable names you reference in the conversation match what's in your template (case-sensitive). You can ask Claude "Show me the variables for the [template name] template" to see the exact names.
Generated decks look generic — they don't match my brand.
When using "generate from scratch," include your company website URL in the prompt. Storydoc fetches brand colors, logos, and imagery from there. Example: "Generate a sales deck for Acme. Our website is https://acme.com."
I'm hitting rate limits.
Storydoc's API allows 150 requests per minute for version-creation endpoints. If you're chaining many creations, space them out. Your plan may also have a monthly request quota — see storydoc.com/pricing.