Moka MCP Server
Related Servers
Alternatives to Moka MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceEnables read-only access to company data across PostgreSQL, MongoDB Atlas, and flat files through MCP tools, allowing AI assistants to query and retrieve information via natural language.-
- FlicenseNot gradedqualityBmaintenanceEnables read-only access to Workday HCM data such as workers, organizations, locations, job profiles, and cost centers through MCP tools an LLM can call.-
- FlicenseNot gradedqualityBmaintenanceEnables AI agents to evaluate candidates against job requirements and retrieve evaluation results through MCP tools.-
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants read-only access to Sprinklr data via MCP, allowing querying reports, searching cases, and calling Sprinklr API endpoints.10 npmISC
- AlicenseBqualityBmaintenanceEnables Claude, Cursor, and other MCP clients to query PeopleForce HRIS data (employees, time-off, recruitment) via 27 read-only tools.284MIT
- AlicenseNot gradedqualityCmaintenanceA hosted, OAuth-authenticated MCP endpoint exposing 176 tools that let AI assistants read and write jobs, candidates, applications, interviews, scorecards, prospects, talent pools, and imports within an organization's own applicant tracking data, scoped to the signed-in user's existing permissions.MIT
TDQS
Scored across 13 tools
Each tool has a clearly distinct purpose: candidate management (applications, detail, stage), job management (detail, custom fields), listing (departments, jobs, pipelines, stages, talent pools), and search. No overlapping functionality.
All tools follow a consistent verb_noun pattern in snake_case (e.g., get_candidate_detail, list_jobs, search_candidates). Verbs are uniformly 'get', 'list', or 'search', making the set predictable.
With 13 tools, the server covers the main entities of an HR platform (candidates, jobs, offers, departments, pipelines, stages, talent pools) without being excessive. The count feels well-scoped.
The server provides comprehensive read operations for all major entities but lacks any create, update, or delete tools. This means agents cannot perform full lifecycle management, leaving notable gaps for tasks requiring modifications.