mcp-vtenext
Related Servers
Alternatives to mcp-vtenext
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityNot gradedmaintenanceEnables users to manage CRM leads, opportunities, projects, tasks, and sales records within ERPNext directly through MCP-compatible clients. It supports global searches, timesheet entries, and access to dashboard KPIs using natural language.-
- AlicenseNot gradedqualityCmaintenanceMCP server for the Nimble CRM API, enabling management of contacts, deals, notes, tasks, and tags through natural language.MIT
- AlicenseNot gradedqualityAmaintenanceMCP server for vtiger CRM that enables AI agents to log timesheets and create/update records in any module via natural language.20 npm1MIT
- AlicenseAqualityCmaintenanceNon-official MCP server for the Corymbus CRM, enabling natural language querying and modification of CRM data via MCP clients like Claude.13MIT
- AlicenseAqualityCmaintenanceMCP server that connects to a sales CRM database, enabling AI agents to search prospects, view pipeline status, manage follow-ups, and update records using natural language commands.5135 npmISC
- AlicenseNot gradedqualityBmaintenanceRemote MCP server for operating a LocalTry CRM with plain-language instructions, enforcing tenant isolation via OAuth-bound connections. Enables searching and managing customers, companies, contacts, leads, jobs, estimates, invoices, and workspace customizations.MIT
TDQS
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.