Skip to main content
Glama
vitrionbv

@vitrion/zentria-mcp

Official
by vitrionbv
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
ZENTRIA_API_KEYYesTeam Personal Access Token
ZENTRIA_BASE_URLNoZentria origin (default https://app.zentria.nl). Do not append /api/public.https://app.zentria.nl

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
get-meA

Return the signed-in user, PAT-bound team, enabled modules, and token scopes (GET /api/public/me). Call this first to learn team id and available modules.

list-teamsA

List teams visible to this PAT (GET /api/public/teams). A team-bound PAT returns exactly one team.

get-teamA

Fetch a team by id (GET /api/public/teams/{id}).

list-tenantsA

List tenants for this PAT (GET /api/public/tenants).

get-tenantA

Fetch a tenant by id (GET /api/public/tenants/{id}).

list-todosA

List to-dos for the PAT-bound team (GET /api/public/teams/{teamId}/todos). Scope: todos:read.

create-todoA

Create a to-do on the PAT-bound team (POST /api/public/teams/{teamId}/todos). Scope: todos:write.

get-todoA

Fetch a to-do by id (GET /api/public/todos/{id}). Scope: todos:read.

update-todoA

Update a to-do (PUT /api/public/todos/{id}). Scope: todos:write.

delete-todoA

Delete a to-do (DELETE /api/public/todos/{id}). Scope: todos:write.

list-peopleB

List sales people/contacts (GET /api/public/sales/people). Scope: sales:read.

create-personA

Create a sales person (POST /api/public/sales/people). Scope: sales:write.

get-personA

Fetch a sales person (GET /api/public/sales/people/{id}). Scope: sales:read.

update-personB

Update a sales person (PUT /api/public/sales/people/{id}). Scope: sales:write.

list-dealsA

List sales deals (GET /api/public/sales/deals). Optional pipelineId filter. Scope: sales:read.

create-dealA

Create a sales deal (POST /api/public/sales/deals). pipelineId is required. Scope: sales:write.

get-dealA

Fetch a sales deal (GET /api/public/sales/deals/{id}). Scope: sales:read.

update-dealB

Update a sales deal (PUT /api/public/sales/deals/{id}). Scope: sales:write.

move-deal-stageA

Move a deal to another pipeline stage (PATCH /api/public/sales/deals/{id}/stage). Scope: sales:write.

list-notesA

List sales notes (GET /api/public/sales/notes). Scope: sales:read.

create-noteB

Create a sales note (POST /api/public/sales/notes). Scope: sales:write.

get-noteA

Fetch a sales note (GET /api/public/sales/notes/{id}). Scope: sales:read.

update-noteC

Update a sales note (PATCH /api/public/sales/notes/{id}). Scope: sales:write.

delete-noteA

Delete a sales note (DELETE /api/public/sales/notes/{id}). Scope: sales:write.

list-activitiesA

List sales activities (GET /api/public/sales/activities). Scope: sales:read.

create-activityB

Create a sales activity (POST /api/public/sales/activities). Scope: sales:write.

get-activityA

Fetch a sales activity (GET /api/public/sales/activities/{id}). Scope: sales:read.

update-activityB

Update or complete/cancel a sales activity (PATCH /api/public/sales/activities/{id}). Set status to done or cancelled. Scope: sales:write.

list-organizationsA

List sales organizations (GET /api/public/sales/organizations). Scope: sales:read.

create-organizationA

Create a sales organization (POST /api/public/sales/organizations). Scope: sales:write.

get-organizationA

Fetch a sales organization (GET /api/public/sales/organizations/{id}). Scope: sales:read.

update-organizationB

Update a sales organization (PUT /api/public/sales/organizations/{id}). Scope: sales:write.

list-pipelinesA

List sales pipelines (GET /api/public/sales/pipelines). Scope: sales:read.

get-pipelineA

Fetch a sales pipeline with stages (GET /api/public/sales/pipelines/{id}). Scope: sales:read.

get-default-pipelineA

Fetch the team default sales pipeline (GET /api/public/sales/pipeline). Scope: sales:read.

list-formsA

List sales forms (GET /api/public/sales/forms). Scope: sales:read.

create-formB

Create a sales form (POST /api/public/sales/forms). Scope: sales:write.

get-formA

Fetch a sales form (GET /api/public/sales/forms/{id}). Scope: sales:read.

update-formA

Update a sales form (PUT /api/public/sales/forms/{id}). Scope: sales:write.

list-form-submissionsA

List sales form submissions (GET /api/public/sales/submissions). Scope: sales:read.

get-form-submissionA

Fetch a sales form submission (GET /api/public/sales/submissions/{id}). Scope: sales:read.

list-customersA

List customers (GET /api/public/customers). Scope: customers:read.

create-customerB

Create a customer (POST /api/public/customers). Scope: customers:write.

get-customerA

Fetch a customer (GET /api/public/customers/{id}). Scope: customers:read.

update-customerC

Update a customer (PUT /api/public/customers/{id}). Scope: customers:write.

archive-customerA

Archive a customer (PATCH /api/public/customers/{id}/archive). Scope: customers:write.

list-customer-contactsA

List contacts for a customer (GET /api/public/customers/{customerId}/contacts). Scope: customers:read.

create-customer-contactA

Create a contact on a customer (POST /api/public/customers/{customerId}/contacts). Scope: customers:write.

get-contactA

Fetch a customer contact (GET /api/public/contacts/{id}). Scope: customers:read.

update-contactC

Update a customer contact (PUT /api/public/contacts/{id}). Scope: customers:write.

list-crm-leadsA

List CRM leads (GET /api/public/crm/leads). Scope: crm:read.

get-crm-leadA

Fetch a CRM lead (GET /api/public/crm/leads/{id}). Scope: crm:read.

approve-crm-leadB

Approve a CRM lead (POST /api/public/crm/leads/{id}/approve). Scope: crm:write.

reject-crm-leadA

Reject a CRM lead (POST /api/public/crm/leads/{id}/reject). Scope: crm:write.

list-crm-submissionsB

List CRM lead submissions (GET /api/public/crm/submissions). Scope: crm:read.

get-crm-submissionA

Fetch a CRM lead submission (GET /api/public/crm/submissions/{id}). Scope: crm:read.

list-stl-flowsA

List Speed to Lead flows (GET /api/public/stl/flows). Scope: stl:read.

create-stl-flowB

Create a Speed to Lead flow (POST /api/public/stl/flows). Scope: stl:write.

get-stl-flowA

Fetch a Speed to Lead flow (GET /api/public/stl/flows/{id}). Scope: stl:read.

update-stl-flowB

Update a Speed to Lead flow (PUT /api/public/stl/flows/{id}). Scope: stl:write.

delete-stl-flowA

Delete a Speed to Lead flow (DELETE /api/public/stl/flows/{id}). Scope: stl:write.

list-stl-sms-templatesA

List STL SMS templates (GET /api/public/stl/sms-templates). Scope: stl:read.

create-stl-sms-templateA

Create an STL SMS template (POST /api/public/stl/sms-templates). Scope: stl:write.

get-stl-sms-templateA

Fetch an STL SMS template (GET /api/public/stl/sms-templates/{id}). Scope: stl:read.

update-stl-sms-templateB

Update an STL SMS template (PUT /api/public/stl/sms-templates/{id}). Scope: stl:write.

delete-stl-sms-templateA

Delete an STL SMS template (DELETE /api/public/stl/sms-templates/{id}). Scope: stl:write.

list-stl-leadsA

List Speed to Lead leads (GET /api/public/stl/leads). Scope: stl:read.

get-stl-leadA

Fetch an STL lead (GET /api/public/stl/leads/{id}). Scope: stl:read.

delete-stl-leadA

Delete an STL lead (DELETE /api/public/stl/leads/{id}). Scope: stl:write.

list-webhooksA

List outbound webhook endpoints (GET /api/public/webhooks). Scope: webhooks:read.

create-webhookB

Create a webhook endpoint. Signing secret returned once (POST /api/public/webhooks). Scope: webhooks:write.

get-webhookA

Fetch a webhook endpoint (GET /api/public/webhooks/{id}). Scope: webhooks:read.

update-webhookB

Update a webhook endpoint (PATCH /api/public/webhooks/{id}). Scope: webhooks:write.

delete-webhookA

Delete a webhook endpoint (DELETE /api/public/webhooks/{id}). Scope: webhooks:write.

list-membersB

List team members (GET /api/public/members). Scope: members:read.

get-memberA

Fetch a team member (GET /api/public/members/{id}). Scope: members:read.

invite-memberA

Invite a member by email (POST /api/public/members). Scope: members:write.

change-member-roleA

Change a member role (PATCH /api/public/members/{id}/role). Scope: members:write.

get-settingsA

Fetch non-secret team settings (GET /api/public/settings). Scope: settings:read.

get-integrationsA

List connected integrations without secrets (GET /api/public/integrations). Scope: integrations:read.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

B3.2/5.0

Scored across 80 tools

Disambiguation3/5

Most tools are partitioned clearly by domain prefixes, but there are overlapping concepts such as sales people/contacts versus customer contacts, and STL leads versus CRM leads versus submissions. Descriptions and API paths help, but an agent could still easily select the wrong tool in those contact/lead/submission clusters.

Naming Consistency5/5

All tool names follow a consistent snake_case verb_noun pattern with domain prefixes for sub-resources. Special actions like move-deal-stage, change-member-role, and archive-customer still obey the same action-object convention, making the set highly predictable.

Tool Count1/5

80 tools is far beyond the recommended 3-15 range and even beyond the 25+ threshold, placing it in the 50+ extreme category. Even if each endpoint is legitimate for the underlying API, this is an overwhelming surface for an agent to navigate.

Completeness3/5

Several resources have full CRUD-like coverage, and the server spans many real domains. However, many entities lack delete operations, members have no removal tool, and STL/CRM leads and submissions have notable read-only or partial workflows, which creates lifecycle gaps.

Maintenance

ActivityMaintained
ResponsivenessNo issues

Resources