perfex-crm-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PERFEX_URL | Yes | Base URL of the Perfex CRM, e.g., https://crm.example.com | |
| PERFEX_FORM_KEY | No | Key of the web-to-lead form (last segment of forms/wtl/{key}) | |
| PERFEX_QUOTE_KEY | No | Key of the quote request form | |
| PERFEX_TIMEOUT_MS | No | Timeout in milliseconds (default: 15000) | 15000 |
| PERFEX_LEAD_SOURCE | No | Default source for leads (default: MCP) | MCP |
| PERFEX_TICKET_PRIORITY | No | Default priority for tickets | |
| PERFEX_TICKET_DEPARTMENT | No | Default department for tickets |
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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_leadA | Crea un lead (cliente potencial) en Perfex CRM vía el formulario web-to-lead. Requiere PERFEX_URL y PERFEX_FORM_KEY configurados. Devuelve success true/false. |
| create_ticketA | Crea un ticket de soporte en Perfex CRM vía el endpoint público /forms/ticket. Requiere PERFEX_URL. Requiere department (o PERFEX_TICKET_DEPARTMENT). |
| request_quoteA | Envía una solicitud de presupuesto (estimate request) vía el formulario público. Requiere PERFEX_URL y PERFEX_QUOTE_KEY. |
| perfex_healthA | Verifica que la URL de Perfex responde. Útil para diagnosticar si el CRM está accesible. |
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 4 tools
Each tool targets a distinct resource and action: lead creation, ticket creation, quote request, and health check. There is no overlap or ambiguity between them.
Two tools follow a 'create_<entity>' pattern, but 'request_quote' uses a different verb and 'perfex_health' is not verb-first. The naming is readable but not fully consistent.
Four tools is well within the ideal range for a focused CRM integration covering public form submissions and a health check. Each tool has a clear purpose and none are redundant.
The tool surface covers the main public-facing actions (lead, ticket, quote) and a health check. Minor gaps exist (e.g., no contact creation or read operations), but the scope of public forms is well covered.