Connect Zentrik MCP in Claude

Claude supports reviewed directory connectors and admin-added custom connectors. Both use the same Zentrik MCP server, OAuth flow, workspace permissions, and tools.

After authorization, ask Claude a product question naturally. Claude can select Zentrik when the question needs workspace evidence; you do not need to name individual tools.

Start with one of these:

What evidence does Zentrik have about onboarding this quarter? Summarize recurring
themes, cite the relevant records, and note important gaps.

What evidence supports [opportunity or idea]? Separate stored facts from your
inference and note what is missing.

For batch imports or unclear metadata, ask Claude to preview the proposed records before creating them. The MCP use cases page includes a complete starter.

Next:

• Customer feedback to build-ready specs for an end-to-end example
• MCP use cases
• MCP best practices

When Claude Code is signed into the same Claude account, the connected Zentrik server can also appear in /mcp.

Full MCP clients can expose Zentrik's guided workflows directly:

• for a new or incomplete workspace, look for /mcp__zentrik__set_up_product_workspace
• for recurring evidence capture, look for /mcp__zentrik__import_product_evidence
• ask naturally when you do not need a shortcut; the same Zentrik tools remain available

Prompt presentation depends on the MCP client. The connector tools are the reliable cross-client surface.

Zentrik publishes a Claude Code plugin that bundles this same connector with three named workflows, so a new machine gets the connection and the workflows in one step.

claude plugin marketplace add Zentrik-AI/claude-plugins

claude plugin install zentrik@zentrik

Run /reload-plugins to activate it in a session that is already open. The interactive equivalents inside Claude Code are /plugin marketplace add Zentrik-AI/claude-plugins and /plugin.

The plugin adds three skills:

• /zentrik:brief-product-work briefs whatever you are about to build with the decisions, customer evidence, and open questions the workspace already holds, each one attributed to a record ID. It only reads, so it needs no approval step and works for Viewer roles. If the workspace holds nothing on the subject it says so rather than filling the gap.
• /zentrik:set-up-product-workspace and /zentrik:import-product-evidence are the skill form of the two guided workflows below.

Claude also runs them on its own when the task matches, so you do not have to remember the names.

The connector works without the plugin. If you connected Zentrik above, you already have every tool the plugin uses. The plugin adds the named workflows and ships the connection with them, and Claude may reuse your existing connection to the same endpoint instead of opening a second one.

Source and license: Zentrik-AI/claude-plugins, Apache-2.0.

The connector ships two guided workflows. They need no separate install: once Zentrik is connected, Claude can run them, and full MCP clients also list them as prompts.

• Set up a product workspace reads the current state, routes first-party material to the correct product, context, evidence, and decision surfaces, applies supported changes with approval, and returns a setup receipt. Use it on a new or incomplete workspace.
• Import product evidence handles recurring source-by-source evidence capture without turning ingestion into a product decision.

Both respect your Zentrik role. A Viewer can run the read portions; applying changes needs Editor, Admin, or Owner.