Ashby
Ashby delivers an applicant tracking system for modern teams, offering features like job postings, candidate management, and data-driven hiring insights to streamline the recruitment process
Verdict
Common use cases
- Check candidate status during hiring syncs
- Pull interview feedback for debrief meetings
- Generate time-to-hire reports for leadership
- Surface pipeline bottlenecks in weekly reviews
- Query open roles by department or location
Integration
- Vendor
- Ashby
- Category
- other
- Auth
- API_KEY
- Composio slug
ashby
Tools
Setup
Setup guide
- 11. In Switchy, open your workspace settings and navigate to the Integrations tab. 2. Find Ashby in the MCP directory and click Connect. 3. You'll be prompted to paste an API key — head to your Ashby account settings (usually under Developer or API Access) and generate a new key with read access to candidates, jobs, and interviews. 4. Copy the key and paste it into Switchy's prompt, then click Authorize. 5. Switchy will confirm the connection and show Ashby as active in your integrations list. 6. To test, open any Space and type '@Ashby list open roles' — if the MCP responds with job titles, you're connected. 7. From there, @mention Ashby anytime you need recruiting data pulled into a conversation.
What teammates see: by default, memories from Ashby are scoped to the Space (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Spaces have used this MCP together with a given model.
How Switchy teams use it
Starter prompts
List Open Roles
@Ashby show me all open roles, grouped by department, and include how many candidates are in each pipeline.Open in a Space →
Candidate Pipeline Check
@Ashby for the Senior Engineer role, show me how many candidates are at each stage and flag any that have been waiting more than a week.Open in a Space →
Interview Feedback Summary
@Ashby pull the latest interview feedback for candidates in final rounds this week and summarize the key themes.Open in a Space →
Time-to-Hire Report
@Ashby calculate average time-to-hire for all roles closed in the last quarter, broken down by department.Open in a Space →
Upcoming Interviews
@Ashby show me all interviews scheduled for this week, including candidate names, interviewers, and role titles.Open in a Space →
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@ashby show me all open engineering roles with more than 10 applicants in the pipeline
Based on your Ashby account, here are the open engineering roles meeting that criteria: Senior Backend Engineer (23 applicants, 4 in final round), Frontend Engineer - Platform (15 applicants, 2 in final round), Staff Engineer - Infrastructure (12 applicants, 1 offer extended). Each role includes current stage distribution and days since posting. This reflects a snapshot at query time.
This example demonstrates read access to job postings and candidate pipeline data. Requires an API key with permissions to view job and candidate information. Results depend on your account's active requisitions and may change frequently as candidates move through stages.
@ashby move candidate Sarah Chen from phone screen to technical interview stage for the Senior Backend Engineer role
Candidate Sarah Chen has been moved to the Technical Interview stage for Senior Backend Engineer (req ID: req_abc123). The stage change triggered an automated email to the hiring team and added her to the interview scheduling queue. Next step: a team member with calendar access should schedule the technical session within your defined SLA window.
This example shows a write action that modifies candidate state in your ATS. Requires API permissions for candidate management. Be aware this triggers downstream workflows (emails, notifications, scheduling prompts) that affect real people. Always verify candidate identity before moving stages.
@ashby summarize hiring velocity for Q1 — average time-to-hire by department and where our bottlenecks are
Q1 hiring velocity summary: Engineering averaged 32 days from application to offer (bottleneck: technical interview scheduling, avg 9-day delay). Product averaged 28 days (bottleneck: final executive approval, avg 6-day delay). Sales averaged 19 days with no significant bottleneck. Overall, 47 hires closed vs. 52 target. Interview-to-offer conversion rate was 68% across all departments.
This example pairs Ashby's reporting data with AI synthesis to surface patterns. Requires API access to analytics endpoints and historical candidate data. Accuracy depends on how consistently your team logs stage transitions and timestamps. Useful for identifying process improvements but should be cross-checked against Ashby's native reports.
Use-case deep-dives
When Ashby MCP helps a 3-person talent team spot pipeline gaps
A series-A startup with 40 open roles and three recruiters needs to audit their pipeline weekly. The Ashby MCP lets the team pull candidate stage distributions, time-in-stage metrics, and source breakdowns into a shared Switchy workspace without exporting CSVs. One recruiter prompts for all roles stuck in 'phone screen' over 10 days; another asks for offer-acceptance rates by referral source. The MCP works because Ashby's API is fast and the team already uses API keys for Zapier. The threshold: if you're only checking one or two metrics, the Ashby dashboard is faster. But if your weekly ops review involves cross-cutting questions across 15+ roles, the MCP saves 20 minutes of manual pivoting. Set it up once, reuse the prompts every Monday.
Pulling hiring velocity numbers into a board narrative
A VP of People at a 120-person company needs to write the talent section of the quarterly board deck. The Ashby MCP lets them ask for time-to-hire by department, offer-to-acceptance ratios, and candidate drop-off funnels in natural language, then paste the results into the deck narrative. The win is speed: instead of asking the recruiting ops lead to run five custom reports, the VP gets answers in two minutes. The MCP requires an API key with read access to analytics endpoints. The trade-off: if your board deck needs pixel-perfect charts, you'll still export from Ashby's native reporting. But for the written narrative and spot-checking numbers before the meeting, the MCP cuts prep time in half. Worth it if you write these decks monthly or quarterly.
When a hiring manager needs to trace one candidate's full journey
A hiring manager gets feedback that a candidate had a confusing interview process. The Ashby MCP lets the manager pull that candidate's full timeline—application date, every interview scheduled, feedback submitted, and final disposition—into a Switchy thread without asking the recruiting coordinator to screenshot everything. The manager shares the thread with the recruiter and they spot the gap: two interviewers gave conflicting 'next steps' messages. The MCP works here because it surfaces the raw event log that Ashby's UI buries under tabs. The limit: if you're doing this for 10+ candidates at once, you want a bulk export, not a conversational interface. But for one-off post-mortems after a candidate complains or a hire falls through, the MCP gets you the facts in 60 seconds.
Frequently asked
What does the Ashby MCP do in Switchy?
The Ashby MCP connects your recruiting data to Switchy's AI workspace. Your team can query candidate pipelines, interview feedback, and hiring metrics without switching tabs. Because Ashby uses API key auth, any team member with a key can connect it — no OAuth dance required.
Do I need admin access to connect Ashby?
You need an Ashby API key, which typically requires admin or developer permissions in your Ashby account. Standard recruiters won't have key generation rights by default. Check with your Ashby workspace owner if you don't see API settings in your account.
Can the Ashby MCP update candidate statuses or schedule interviews?
That depends on which tools Ashby exposes via their MCP server. Most recruiting MCPs start read-only — pulling candidate data, interview notes, pipeline stages. Write operations like moving candidates or booking slots usually come later. Check the tool list once Ashby publishes their server spec.
Why use the Ashby MCP instead of just logging into Ashby?
The MCP lets your AI assistant pull recruiting context into conversations with engineering, product, or finance data. Instead of copying candidate names between apps, you ask one question and get a synthesised answer. It's faster when you're triangulating hiring velocity against roadmap capacity.
Does connecting Ashby count against my Switchy seat limit?
No. MCP connections are workspace-level resources in Switchy, not per-seat. Once one person connects Ashby, everyone on the team can use it in their chats. You're only limited by Ashby's own API rate limits, not Switchy seats.