Volkern MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| VOLKERN_API_KEY | Yes | Tu API key de Volkern. | |
| VOLKERN_API_URL | No | La URL de la API de Volkern. | https://volkern.app/api |
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
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| volkern_list_leadsB | List leads with optional filters. Returns paginated results. |
| volkern_get_leadB | Get detailed information about a specific lead by ID |
| volkern_create_leadA | Create a new lead in the CRM. If email already exists, updates the existing lead. |
| volkern_update_leadC | Update an existing lead's information |
| volkern_check_disponibilidadA | Check available time slots for a specific date. Always call this before booking. |
| volkern_list_citasC | List appointments with optional filters |
| volkern_create_citaA | Create a new appointment. Check availability first with volkern_check_disponibilidad. |
| volkern_update_citaC | Update an existing appointment |
| volkern_cita_accionC | Perform an action on an appointment (confirm, cancel, or reschedule) |
| volkern_list_serviciosB | List available services from the catalog |
| volkern_get_servicioB | Get detailed information about a specific service |
| volkern_create_taskC | Create a follow-up task for a lead |
| volkern_list_tasksC | List tasks for a specific lead |
| volkern_complete_taskC | Mark a task as completed |
| volkern_send_whatsappB | Send a WhatsApp message to a lead. Requires active WhatsApp integration. |
| volkern_list_conversacionesB | List WhatsApp conversations, optionally filtered by lead |
| volkern_list_interactionsC | List all interactions for a specific lead |
| volkern_create_interactionC | Log an interaction (call, email, meeting) with a lead |
| volkern_list_notesC | List all notes for a specific lead |
| volkern_create_noteC | Create a note for a lead |
| volkern_list_contactsB | List contacts (people or companies) with optional filters |
| volkern_get_contactC | Get detailed information about a specific contact by ID |
| volkern_create_contactC | Create a new contact (person or company) |
| volkern_update_contactC | Update an existing contact's information |
| volkern_list_dealsC | List deals/opportunities in the sales pipeline with optional filters |
| volkern_get_dealC | Get detailed information about a specific deal |
| volkern_create_dealC | Create a new deal/opportunity in the sales pipeline |
| volkern_update_dealC | Update an existing deal (change stage, value, status, etc.) |
| volkern_list_pipeline_stagesB | List all pipeline stages configured for the tenant |
| volkern_get_sales_forecastC | Get sales forecast and pipeline analytics |
| volkern_list_cotizacionesC | List quotations/quotes with optional filters |
| volkern_get_cotizacionB | Get detailed information about a specific quotation |
| volkern_create_cotizacionC | Create a new quotation/quote |
| volkern_update_cotizacionB | Update a quotation (only if status is 'borrador') |
| volkern_send_cotizacionC | Send a quotation to the client via email |
| volkern_list_contratosC | List contracts with optional filters |
| volkern_get_contratoB | Get detailed information about a specific contract |
| volkern_create_contratoC | Create a new contract |
| volkern_create_contrato_from_cotizacionC | Create a contract from an accepted quotation |
| volkern_send_contratoC | Send a contract to the client for signature |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 40 tools
Most tools have distinct purposes targeting specific CRM/ERP resources and actions, with clear boundaries like create_contact vs. update_contact. However, some overlap exists: volkern_create_cita and volkern_update_cita could be confused with volkern_cita_accion (which handles confirm/cancel/reschedule), and volkern_create_lead's update behavior on duplicate email might blur with volkern_update_lead. Descriptions help clarify, but minor ambiguity remains.
All tools follow a consistent verb_noun pattern with snake_case, using clear action verbs like create, get, list, update, send, and complete. The naming is highly predictable and readable across all 40 tools, with no deviations in style or convention, making it easy for agents to infer functionality.
With 40 tools, the count feels excessive for a CRM/ERP server, likely leading to cognitive overload and reduced usability. While the domain is broad, many tools could be consolidated (e.g., separate list tools for each resource) or parameterized. This heavy toolset may overwhelm agents and slow down decision-making.
The toolset provides comprehensive coverage for CRM/ERP workflows, including full CRUD operations for leads, contacts, appointments, deals, contracts, and quotations, plus lifecycle actions like sending documents and logging interactions. No obvious gaps exist; agents can handle end-to-end processes from lead creation to contract signing and task management.