Zentrik MCP
Connect Zentrik MCP in Claude
Follow these screens to connect Zentrik MCP in Claude.
Use the Zentrik connector from Claude's Connectors Directory when it is available. Until then, an organization admin can add Zentrik as a custom connector with https://zentrik.ai/mcp.
Steps
Claude supports reviewed directory connectors and admin-added custom connectors. Both use the same Zentrik MCP server, OAuth flow, workspace permissions, and tools.
1. Open Connectors
Open Customize → Connectors, select +, then browse connectors. Organization admins can also add a custom connector for their team from the organization connector settings.

Claude Connectors settings.
2. Add the connector
If Zentrik appears in the Connectors Directory, choose Connect. Otherwise choose Add custom connector, enter Zentrik, use https://zentrik.ai/mcp, then save it.

Claude custom connector form with the Zentrik MCP URL.
3. Authenticate
Use the connector's Authenticate flow.
4. Approve in Zentrik
In Zentrik, choose the workspace for this connection and approve access.
If Claude does not redirect into OAuth right away, wait a few seconds or restart Claude, then try the connector again.

Zentrik approval screen during MCP authentication.
Use Zentrik in Claude
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

Claude connected to Zentrik MCP with tools available.
Claude Code shortcuts
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 plugin
The Zentrik Claude plugin adds two focused skills and bundles the same remote connector:
- 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.
- Import product evidence handles recurring source-by-source evidence capture without turning ingestion into a product decision.
Once the plugin is available to your organization or in Claude's plugin directory, install it from Customize → Plugins. Claude can invoke a skill when relevant, or you can choose it from the / menu. Existing connections to the same Zentrik endpoint can be reused; the plugin does not contain credentials.
The connector works without the plugin. Install the plugin when you want named setup and import workflows in addition to automatic tool use.
Troubleshooting
Check these steps against what you see in your workspace. If something differs, note your workspace name and the screen, then contact us.
I cannot add a custom connector
Your Claude organization may restrict custom connectors. Ask an organization admin to add Zentrik, or use the directory listing once it is available.
Claude did not redirect into auth
Wait a few seconds, then try again. If it still does not trigger the OAuth flow, restart Claude and re-open the connector.
Claude shows the connector but not the tools
Finish the browser OAuth flow first. The tools appear after the connector is authenticated into a workspace.
I chose the wrong workspace
Run the auth flow again and choose the correct workspace. Each MCP connection is bound to one workspace at a time.