F
licenseNot graded
qualityC
maintenanceExposes CRM operations as MCP tools, enabling agents to search contacts, retrieve contact records, list appointments, log notes, and create new leads.
-
wealthbox-mcp
by rhyeal
Related Servers
Alternatives to wealthbox-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityAmaintenanceEnables MCP-capable clients to browse, search, and manage projects, todos, messages, card tables, documents, uploads, comments, events, and webhooks through OAuth-authenticated API calls.-
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to list customer accounts, retrieve event timelines, get next-action recommendations, and push tasks to a CRM.MIT
- AlicenseNot gradedqualityAmaintenanceEnables MCP clients to search, create, and update Yacrum CRM records, log activities, manage tasks, read pipelines and forecasts, and summarize deals through the Yacrum REST API using an API key.1,045 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables MCP-compatible AI clients to search and view CRM customers, deals, contracts, tasks, calendars, and outbound jobs, and to propose opt-in write actions that require human approval in the CRM.Apache 2.0
Ridian MCP Serviceofficial
AlicenseNot gradedqualityCmaintenanceEnables authorized users to manage calendars, availability, tasks, contacts, sync operations, and Agent Mailbox email tools through an OAuth-scoped MCP connection.MIT
TDQS
B3/5.0
Scored across 51 tools
Disambiguation5/5
Each tool targets a distinct resource-action pair, with standard CRUD verbs and clear resource prefixes. The only potential overlap is between health and getMe, but their descriptions clearly differentiate a connectivity check from profile retrieval. The generic request tool does not create ambiguity as it serves as a catch-all.
Naming Consistency4/5
The vast majority of tools follow the wealthbox.<resource>.<action> pattern with consistent snake_case CRUD verbs. Minor deviations include wealthbox.getMe, listUsers, listTeams, and request, plus camelCase actions like addMember/deleteMember, which break the pattern slightly but remain predictable.
Tool Count3/5
With 51 tools, this server is clearly on the heavy side, but the count is justified by the broad CRM domain covering over 10 entities with full CRUD operations. It may be overwhelming for agents, yet each tool serves a distinct purpose and no redundant tools exist.
Completeness4/5
Core entities (contacts, tasks, events, opportunities, projects) have complete CRUD coverage. Minor gaps exist, such as missing delete for notes, missing update for workflows, and limited operations for comments and templates, but these can be worked around with the generic request tool and do not severely hinder common workflows.
Maintenance
ActivityInactive
ResponsivenessNo issues