Product Manager Loadout
5 MCP servers for synthesising feedback into roadmap
Last verified:
Read raw customer feedback in Slack, file structured tickets in Linear, sketch flows from Figma comments, and check whether anything moved the needle in PostHog. The synthesis loop a PM does every week.
Install Product Manager Loadout
Paste into~/Library/Application Support/Claude/claude_desktop_config.json{
"mcpServers": {
"linear": {
"command": "npx",
"args": ["-y", "@modelcontextprotocol/server-linear"],
"env": { "LINEAR_API_KEY": "lin_api_..." }
},
"notion": {
"command": "npx",
"args": ["-y", "@modelcontextprotocol/server-notion"],
"env": { "NOTION_TOKEN": "secret_..." }
},
"slack": {
"command": "npx",
"args": ["-y", "@modelcontextprotocol/server-slack"],
"env": { "SLACK_BOT_TOKEN": "xoxb-...", "SLACK_TEAM_ID": "T..." }
},
"figma": {
"command": "npx",
"args": ["-y", "@modelcontextprotocol/server-figma"],
"env": { "FIGMA_ACCESS_TOKEN": "figd_..." }
},
"posthog": {
"command": "npx",
"args": ["-y", "posthog-mcp"],
"env": { "POSTHOG_API_KEY": "phc_..." }
}
}
}After pasting, fully restart your MCP client. Replace placeholders (paths, API keys) with your own values.
What's in this loadout
- Linear MCP Servercoremcp
Create epics, file bugs, update sprint scope based on what comes out of synthesis.
- Notion MCP Servercoremcp
PRDs, decision logs, sprint reviews — your durable memory.
- Slack MCP Servercoremcp
Pull customer conversations from #feedback and competitor mentions from #intel.
- Figma MCP Serveroptionalmcp
Read design comments and proposed flows when scoping work.
- PostHog MCPoptionalmcp
Check whether the last release moved any of the metrics you care about.
What you can do with it
Weekly synthesis
Read the last 7 days of #customer-feedback on slack, group by theme, and for the top 3 themes file linear epics under "Discovery". Save the full synthesis as a notion page in "Weekly Reviews".Did the release work?
Pull posthog data for the "checkout v2" feature flag — conversion rate before/after rollout. If the rate dropped, file a linear bug under "Regression" with the data attached.PRD draft
Read the design comments on the "Onboarding Redesign" frame in figma, combine with feedback notes in notion under "Onboarding pain", and draft a PRD as a new notion page.
Client compatibility
- Claude Desktop 0.7.4Tested ✓
- Cursor 0.42+Tested ✓
- Windsurf 1.4Tested ✓
- Continue 0.9Untested
Variants
Heavy version
Adds Intercom for direct customer conversations and Mixpanel for teams that don't use PostHog.
Adds: intercom-mcp, mixpanel-mcp
Lite version
Linear + Notion + Slack. The PM core loop.
Removes: mcp-server-figma, posthog-mcp
FAQ — Product Manager Loadout
What is the Product Manager Loadout?
Read raw customer feedback in Slack, file structured tickets in Linear, sketch flows from Figma comments, and check whether anything moved the needle in PostHog. The synthesis loop a PM does every week. It includes 5 MCP servers: Linear MCP Server, Notion MCP Server, Slack MCP Server, Figma MCP Server, PostHog MCP.
Does this loadout work with Cursor and Windsurf?
Yes. The config block above is one JSON object that drops into Claude Desktop's, Cursor's, or Windsurf's MCP config. Each client uses the same mcpServers schema; only the file path differs.
How long does setup take?
About 3 minutes the first time: copy the config, paste it into your client's MCP configuration file, replace placeholder API keys with your own, and restart the client.
Can I customise this loadout?
Yes. Use the Lite version if you want fewer servers, or the Heavy version to add 2 more for advanced workflows. You can also remove any individual server by deleting its entry from the JSON.
How much does it cost?
Loadout itself is free. Most listed servers are open-source and free to run. Servers that talk to paid SaaS (Stripe, SendGrid, Linear, etc.) follow that vendor's pricing.
When was this loadout last verified?
Last verified on 2026-04-24. We re-test featured loadouts at least monthly and update the config when MCP servers ship breaking changes.