Ashby MCP Server
Related Servers
Alternatives to Ashby MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables Claude to connect securely to a recruiter workspace to track candidate interviews, generate AI interview invitation links, review assessment scorecards, list job descriptions, search resumes semantically, and check interview quotas.MIT

hirly MCP serverofficial
AlicenseNot gradedqualityCmaintenanceConnects an AI assistant to a job-matching account so it can read roles matched to your resume, pull full job details and hiring contacts, and save tailored resume versions. With explicit opt-in and per-job confirmation in the chat, it can also start applications, relay questions only you can answer, and report each application's status.MIT- AlicenseAqualityFmaintenanceEnables AI tools like Claude and Codex to access and manage Recruit CRM data including candidates, jobs, companies, tasks, meetings, notes, and call logs through natural language.699 npmMIT
- FlicenseAqualityDmaintenanceConnects Claude to the Pandapé recruitment API, enabling natural language management of vacancies, structured candidate review against custom criteria, pipeline stage updates, and CV downloads.14-
- FlicenseNot gradedqualityDmaintenanceEnables Claude to securely search, read, and update your ATS data — candidates, mandates, pipelines, tasks, and interviews — through natural language, with configurable write permissions and confirmation for actions like scheduling and emailing.-
- AlicenseNot gradedqualityCmaintenanceGives MCP clients such as Claude, ChatGPT and Cursor access to a recruitment firm's database — candidates, contacts, companies, jobs, pipelines, notes and outreach — so assistants can search, match, draft and update records. Every request runs under the signed-in user's own account, workspace and role permissions, with sensitive actions confirmed as a preview first.MIT
TDQS
Scored across 7 tools
Each tool maps to a clearly distinct step in a browser session lifecycle: guide (instructions), status (readiness), open (navigate), read (inspect), click (interact), type (input), close (teardown). The two informational tools (guide vs status) are the closest pair, but their descriptions clearly separate onboarding guidance from account/connection verification.
All tools use the same ashby_ prefix followed by a single verb in snake_case (open, read, click, type, close, guide, status). No mixed conventions or vague multi-word names; the pattern is immediately predictable.
Seven tools is well-scoped for a single-site browser automation server: one tool per primitive action plus setup/teardown and help. Nothing feels redundant or padded, and nothing essential to the loop is missing at this count.
The core loop (open → read → click/type → close) plus session management and help covers the stated purpose. Minor gaps exist, such as scrolling/navigation back, waiting for page loads, or keyboard submit (Enter), which agents may need on long or dynamically loading Ashby pages, but these are workable through read+click.