Connect Zentrik MCP

Start with the guide for the tool you are using:

• Codex setup guide
• Cursor setup guide
• Claude setup guide

Quick fit:

• Codex if you want the shortest hosted setup flow
• Cursor if you want Zentrik context available inside your editor and agent workflows
• Claude if you want product context while researching, synthesizing, or drafting

If you are in another MCP client, use the same server URL and OAuth flow. If the client only asks for a static bearer token or API key, it is not using the right auth flow for Zentrik MCP.

Start with small, evidence-seeking requests:

• ask what Zentrik already knows about a problem, request, or idea
• pull the relevant opportunity, idea, or context record before you plan or build
• add fresh notes from a call, interview, or demo without leaving your current tool
• run a Study learning loop: find or create a private plan, revise it, monitor de-identified evidence, and generate draft findings while keeping launch and participant distribution in Zentrik
• review and answer Idea planning questions, maintain Idea taxonomy and Initiative links, and regenerate generated Initiative documents after approved source changes
• ask what a person or agent changed, with confirmed, no-change, or unverifiable outcomes and explicit coverage

Keep in mind:

• access is tied to the workspace you approved
• your role in that workspace still matters
• if you want a different workspace, reconnect and choose it
• if newly released tools do not appear, reconnect and approve the current permissions; some clients keep the original grant until you do
• workspace API keys still work for /external/v1, but not for /mcp
• every MCP write creates a durable receipt; the same shared boundary covers product writes reused by Zentrik agents
• use system.get_change_history for product changes and system.get_activity for background jobs
• change history states whether the requested time and channels are complete, partial, or untracked and summarizes repeated attempts so retry noise does not hide other outcomes
• MCP and Slack-agent product mutations are fully tracked after receipt collection begins; workspace-agent history is partial; UI, External API, integration, background-job, and portal mutations are untracked

Next:

• Product management MCP servers compared for a dated, source-linked view of Zentrik, Productboard, Aha!, Linear, Atlassian, PostHog, and LaunchDarkly
• Product-to-spec use case for how signal becomes build-ready scope
• Codex handoff use case for implementation-ready context
• Claude Code handoff use case for clearer requirements prompts
• MCP use cases for practical first prompts
• MCP best practices for lighter prompting and realistic limits