No user-submitted related servers found.
Scored across 69 tools
Most tools have clearly distinct purposes and follow a consistent verb_noun pattern, making selection straightforward. However, a few sets (e.g., list_candidate_hiring_stages, list_job_statuses, list_contact_stages, list_pitch_stages) are functionally similar (resolving IDs/labels for different pipelines) and could be confused by an agent, and get_pitch_history versus get_pitched_records have overlapping-sounding names.
All tool names use lowercase snake_case and follow a consistent verb_noun pattern (search_candidates, create_job, update_meeting, get_company_details). Even longer names like get_candidate_job_assignment_hiring_stage_history maintain the convention. There are no camelCase or mixed style deviations.
With 69 tools, this server is well above the 25+ threshold that feels heavy. While the breadth might be justified for a full Recruit CRM integration, the count is excessive for a typical MCP server and carries significant selection overhead. The presence of many small lookup/list tools (list_currencies, list_qualifications, list_xml_jobboards, etc.) inflates the count beyond what is likely needed.
The server lacks any delete operations for any entity, which is a major gap in CRUD/lifecycle coverage. Additionally, some core entities (tasks, meetings, notes, call logs) have search tools but no corresponding list or get-details tools, and hotlists have no update or remove-record functionality. This leaves agents unable to fully manage the full lifecycle of many objects.
