MCP server for VTENext CRM: exposes the WebService API as tools for Claude and other MCP-compatible clients.
Node.js 18+
A running VTENext instance (self-hosted or Docker, see ../docker)
Related MCP server: nimble-crm-mcp
cd mcp/vtenext/server
npm install
cp .env.example .envEdit .env:
VTENEXT_URL=http://your-vtenext-instance
VTENEXT_USERNAME=admin
VTENEXT_ACCESS_KEY=your_access_key
READ_ONLY=falseThe access key is in VTENext under Admin → Users → [user] → Access Key.
Set READ_ONLY=true to prevent any write operation on VTENext. When enabled, the tools create_opportunita, update_opportunita and add_nota_opportunita return an error instead of writing data.
This is useful when the server is used by AI bots or automated agents that should only read CRM data. To run a read-only instance alongside a full-access one, pass the variable via the MCP config:
{
"mcpServers": {
"vtenext-bot": {
"type": "stdio",
"command": "node",
"args": ["/absolute/path/to/mcp/vtenext/server/index.js"],
"env": {
"VTENEXT_URL": "http://your-vtenext-instance",
"VTENEXT_USERNAME": "admin",
"VTENEXT_ACCESS_KEY": "your_access_key",
"READ_ONLY": "true"
}
}
}
}Add to .mcp.json in your project root:
{
"mcpServers": {
"vtenext": {
"type": "stdio",
"command": "node",
"args": ["/absolute/path/to/mcp/vtenext/server/index.js"]
}
}
}Tool | Description |
| List opportunities with optional filters (status, search, limit) |
| Get full details of an opportunity by ID |
| Search opportunities by name |
| Create a new opportunity (write, blocked in read-only mode) |
| Update status, amount or notes on an existing opportunity (write, blocked in read-only mode) |
Tool | Description |
| Search contacts by name, email or company |
Tool | Description |
| Add a comment/note to an opportunity (write, blocked in read-only mode) |
| List activities linked to an opportunity |
Tool | Description |
| Show available fields for any VTENext module |
| Run a raw VTQL SELECT query |
VTENext uses the vtiger WebService protocol:
GET /webservice.php?operation=getchallenge → token
MD5(token + accessKey) → hashed key
POST /webservice.php with operation=login (form-encoded) → sessionName
Sessions are cached for 4 minutes (token lifetime is 5 minutes).
# Unit tests (no VTENext required)
npm test
# Integration tests (requires live VTENext at VTENEXT_URL)
npm run test:integrationMIT
Maintained by Castaldo Solutions, enterprise-grade technology built for SMEs.
Why we built an MCP server for a CRM instead of an integration: Connecting VTENext to Claude with MCP.
Aggiunge una nota/commento a un'opportunità
Inputs: opportunita_id (required), testo (required).
Crea una nuova opportunità in VTENext
Inputs: nome (required), stato, importo, data_chiusura, +1 more.
Mostra i campi disponibili per un modulo VTENext
Inputs: modulo (required).
Recupera i dettagli completi di un'opportunità tramite ID
Inputs: id (required).
Elenca le attività associate a un'opportunità
Inputs: opportunita_id (required), limit.
Elenca le opportunità con filtri opzionali
Inputs: limit, stato, search.
Esegue una query VTQL grezza su VTENext (solo lettura)
Inputs: query (required).
Cerca contatti per nome, email o azienda
Inputs: q (required), limit.
Cerca opportunità per nome
Inputs: q (required), limit.
Aggiorna i dati di un'opportunità esistente
Inputs: id (required), stato, importo, descrizione.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Scored across 10 tools
Each tool has a clearly distinct purpose with no ambiguity. For example, list_opportunita retrieves multiple records with filters, get_opportunita fetches a single record by ID, and search_opportunita finds records by name. The tools target different resources (opportunità, contatti, modulo) and actions (create, update, list, search, describe, query).
All tool names follow a consistent verb_noun pattern in snake_case. Verbs like add, create, describe, get, list, query, search, and update are used predictably with corresponding nouns (e.g., add_nota_opportunita, create_opportunita, describe_modulo). There are no deviations in naming conventions.
With 10 tools, the count is well-scoped for managing opportunities and related data in VTENext. Each tool serves a clear purpose, such as CRUD operations for opportunities, searching contacts, listing activities, and raw queries. No tool feels redundant or unnecessary for the server's domain.
The tool set provides complete coverage for the VTENext opportunity management domain. It includes full CRUD (create, get, update, list/search) for opportunities, plus related operations like adding notes, listing activities, searching contacts, describing modules, and raw queries. There are no obvious gaps, and agents can handle typical workflows without dead ends.
API-first CRM for LLMs - contacts, companies, deals and activities over a native MCP server.
Vtiger MCP server for ChatGPT, Claude and any AI agent: list contacts, convert contact to deal, list deals, update deal stage, list cases, create case, update case and create contact in your own Vtiger account. Cotlet works in the account through your Cloud Browser, a real Chrome where you sign in to Vtiger yourself; Cotlet does not store your password and you need no Vtiger API key. About the official Vtiger API: Yes, Vtiger has a REST API, but its limits table lists 0 requests for One Pilot and 24,000 a day (30 a minute) for One Growth, and Vtiger has no official MCP server (checked 22 Oct 2026). Setup and FAQ: https://cotlet.dev/integrations/vtiger-api-mcp-server
MCP server unifying ERPs, CRMs, APIs and knowledge base for Claude, ChatGPT and Gemini.
MCP server for Getfly CRM — customers, opportunities, orders, tickets and tasks.
