@vitrion/zentria-mcp
Zentria MCP server — full Zentria public team API coverage for AI assistants via the .
Potencialize seu agente
O comando do próprio publicador. Não é um endpoint do PlugMCP.
Host a copy with our keys and logs.
npx -y @vitrion/[email protected]O Claude Code não tem link de instalação para um comando local. Copie o comando abaixo e execute-o em um terminal.
claude mcp add vitrion-zentria-mcp -- npx -y @vitrion/zentria-mcp@1.18.1Execute em um terminal.
{ "mcpServers": { "vitrion-zentria-mcp": { "command": "npx", "args": [ "-y", "@vitrion/[email protected]" ] } }}claude_desktop_config.json
URL remota ou um comando na sua máquina? Como as duas instalações diferem
Rodar no PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
AbrirDo publicador
Zentria MCP server — full Zentria public team API coverage for AI assistants via the .
Zentria MCP server — public team API for AI assistants via Model Context Protocol
Published as @vitrion/zentria-mcp.
This server uses the official public REST API at /api/public. Paths and request bodies match the OpenAPI docs; they are not invented.
Authorization: Bearer)Retry-After)https://app.zentria.nl/mcpThe client also sends Accept: application/json and User-Agent: @vitrion/zentria-mcp/<version>. The API key is never written to logs.
npx -y @vitrion/zentria-mcp
Add to your user config (~/.cursor/mcp.json) or project config (.cursor/mcp.json):
{
"mcpServers": {
"zentria": {
"command": "npx",
"args": ["-y", "@vitrion/zentria-mcp"],
"env": {
"ZENTRIA_API_KEY": "<team-pat>",
"ZENTRIA_BASE_URL": "https://app.zentria.nl"
}
}
}
}
macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%\Claude\claude_desktop_config.json
Use the same mcpServers block as Cursor.
claude mcp add zentria -- npx -y @vitrion/zentria-mcp
Set ZENTRIA_API_KEY in your shell environment or MCP host config.
Zentria hosts this server at https://app.zentria.nl/mcp. In Claude (web, Desktop, mobile) choose Settings → Connectors → Add custom connector, enter that URL and sign in with your Zentria account. On the consent screen you pick the team and the scopes. No API key is needed.
ZENTRIA_MCP_TRANSPORT=http node dist/index.js
# or
node dist/index.js --http
How it works:
/.well-known/oauth-protected-resource/mcp, /.well-known/oauth-authorization-server and dynamic client registration at /oauth/register.401 with WWW-Authenticate: Bearer resource_metadata="…", which starts the client's sign-in.GET /api/public/me (cached for 30 seconds) and forwarded unchanged to the public API. Team API keys work as bearer tokens too.GET /healthz answers {"ok":true}.Run it behind a TLS proxy that forwards the MCP path unchanged, for example nginx:
location = /mcp {
proxy_pass http://127.0.0.1:3333;
proxy_http_version 1.1;
proxy_set_header Host $host;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_buffering off;
proxy_read_timeout 300s;
}
get-me first to learn the bound team, enabled modules, and token scopes.sales:read, sales:write, etc.)./api/public/docs338 tools. They cover what you can do in the Zentria app, limited by the rights of the member behind the key and by the scopes of the key. In the hosted connector (HTTP mode) only the tools that fit the scopes of the token are listed, so a read-only connection sees about 110 tools.
git clone https://github.com/vitrionbv/zentria-mcp.git
cd zentria-mcp
npm install
npm run build
npm test
npm run dev
npm run build
npm run inspector
Releases go to npm with trusted publishing (OIDC). Push a v* tag to run .github/workflows/npm-publish.yml. The workflow uses id-token: write and does not use NODE_AUTH_TOKEN.
Configure the trusted publisher on npm: GitHub org vitrionbv, repo zentria-mcp, workflow npm-publish.yml.
MIT — see LICENSE.
Zentria MCP server — public team API for AI assistants via Model Context Protocol
{ "mcpServers": { "vitrion-zentria-mcp": { "command": "npx", "args": [ "-y", "@vitrion/[email protected]" ] } }}Ferramentas
Ainda não há lista de ferramentas. Servidores remotos recebem uma após a primeira verificação de saúde.
Perguntas frequentes
Copie nesta página a configuração stdio para Cursor, Claude Desktop, Claude Code ou VS Code. Ela usa a instalação do publicador, não um proxy do PlugMCP.
Este registro não lista nenhuma variável de ambiente obrigatória.
@vitrion/zentria roda localmente via stdio.
Última verificação: 2026-11-17. Zentria MCP server — public team API for AI assistants via Model Context Protocol