
Zentrik
ai.zentrikPublished by zentrik.aiOfficial publisherv1.0.1Updated Oct 30, 2026
Product context for AI agents: evidence, opportunities, initiatives, and decisions.
Overview
Connects an AI assistant to Zentrik product context — customer evidence, opportunities, initiatives and decisions — for one selected workspace.
- What you can do
- Retrieve product context: evidence, opportunities, initiatives and decisions from a Zentrik workspace
- Brief planning, scoping, building and review work against existing workspace evidence
- Inspect a workspace and apply an approved, bounded setup change
- Import calls, tickets, reviews, feedback or research with an approval step before writes
- Plan, refine and review a private Study through evidence-grounded draft findings
- When to use it
- Useful when a team keeps product decisions, customer evidence and research in Zentrik and wants an assistant to ground planning, code changes or reviews in that material, or to import new feedback with an approval step.
- Requirements
- A remote Streamable HTTP endpoint at zentrik.ai/mcp; no local package or API key. Requires a Zentrik account and membership in at least one workspace, plus OAuth sign-in in a browser and selection of the workspace the connection may use.
Installation
In SourceWeft
- Open Zentrik in the dashboard and add it to a workspace.
- Connect the required credentials. They are stored privately and never shown on public pages.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/ai.zentrik%2Fmcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.
{
"mcpServers": {
"zentrik": {
"type": "http",
"url": "https://zentrik.ai/mcp"
}
}
}README
Zentrik Agent Plugin
Connect an AI agent to the product decisions, customer evidence, and product context your team keeps in Zentrik.
The repository root follows the Agent Plugins v1 format and bundles the production Zentrik Streamable HTTP MCP server with four reusable workflows:
brief-product-work: ground planning, scoping, building, and review in the workspace's existing evidence.set-up-product-workspace: inspect a workspace and apply only an approved, bounded setup delta.import-product-evidence: capture supplied calls, tickets, reviews, feedback, or research with an approval step before writes.manage-product-study: plan, refine, and review a private Study through evidence-grounded draft findings.
The plugin contains no credentials and no local executable code. The MCP server authenticates through Zentrik OAuth, binds each connection to one selected workspace, and enforces the connected user's role and granted scopes.
Choose the right surface
- Portable Agent Plugins clients load the repository root and connect to the broad
https://zentrik.ai/mcpendpoint. - Codex loads the OpenAI adapter at
com.openai/zentrik, which maps to the registered Zentrik app available to ChatGPT and Codex. Both packages include the four workflows above; the app uses the narrower ChatGPT tool profile. - MCP-only clients can connect directly to
https://zentrik.ai/mcpand complete Zentrik OAuth. - Server-to-server automation should use the versioned REST API at
/external/v1with a scoped API key. The REST API is documented separately and is not bundled in this plugin.
See SURFACES.md for the compatibility contract and the reason the available tools differ by surface.
GitHub Copilot and VS Code
The server is published in the Official MCP Registry as ai.zentrik/mcp. To add it by hand, put this in .vscode/mcp.json (or your user MCP configuration):
Start the server, sign in to Zentrik in the browser window that opens, and pick the workspace this connection may use. Then ask Copilot in agent mode things like:
- "What do customers say about bulk export? Cite the evidence."
- "Brief me on the initiative behind this branch before I change it."
- "Which open ideas have the most customer evidence this quarter?"
Writes, such as importing evidence or updating a record, are limited to your Zentrik role and the scopes you granted.
Codex CLI
This repository includes a Codex marketplace catalog for local, Git, and team distribution:
The repository root remains the portable artifact. The marketplace entry points Codex at the client adapter under com.openai/zentrik; this keeps OpenAI-specific metadata out of the portable manifest.
OpenAI directory publication
Run python3 scripts/package-openai-plugin.py --output zentrik-openai.zip to
package the adapter for the existing directory listing. The packager derives
its technical name from the registered app mapping. The ZIP includes the four
skills, assets, license files, and the existing ChatGPT MCP endpoint in the
portable manifest format. Keep that endpoint in every update; the existing
listing owns its OAuth configuration, so the ZIP must not override it.
The CLI marketplace keeps the zentrik name and registered app mapping.
Upload the ZIP as a new metadata and skills version in the existing listing;
server-only changes use continuous MCP review.
Requirements
A Zentrik account and membership in at least one Zentrik workspace. No API key is required.
Documentation and support
- Codex setup: https://zentrik.ai/docs/integrations/mcp-codex
- ChatGPT setup: https://zentrik.ai/docs/integrations/mcp-chatgpt
- MCP setup: https://zentrik.ai/docs/integrations/mcp
- MCP workflows: https://zentrik.ai/docs/integrations/mcp-workflows
- Support: [email protected]
License
Apache-2.0. See the LICENSE file in the distribution repository.
Source: README.md at commit d0623a0
Tools
0Version history
2- v1.0.1LatestOct 22, 2026
- v1.0.0Sep 16, 2026
Score
85% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts