Compatible with every major AI agent and IDE
What is the Ashby MCP Server?
Connect your Ashby account to any AI agent and take full control of your recruiting pipeline and candidate experience through natural conversation.
What you can do
- Candidate Orchestration — List and manage candidate profiles programmatically, including creating new records and retrieving high-fidelity profile metadata
- Application Lifecycle Management — Monitor job applications and retrieve detailed status metrics for specific candidates to coordinate your hiring funnel in real-time
- Interview Intelligence — Access scheduled interviews and retrieve submitted high-fidelity feedback reports to summarize performance and sentiment
- Job & Department Visibility — Retrieve complete directories of open jobs, departments, and hiring managers to maintain a perfectly coordinated organizational view
- User & Location Monitoring — Access your internal recruiter directory and physical office locations directly through your agent for instant operational reporting
How it works
- Subscribe to this server
- Retrieve your API Key from the Ashby dashboard (Admin > API Keys)
- Start managing your talent pipeline from Claude, Cursor, or any MCP client
No more manual toggling between browser tabs to check a candidate's status or feedback. Your AI acts as your dedicated talent coordinator and recruiting architect.
Who is this for?
- Recruiters & Sourcers — instantly retrieve candidate summaries and update application stages using natural language commands
- Hiring Managers — check interview feedback and pipeline health across departments without leaving your creative workspace
- HR Operations — automate the oversight of job postings and user permissions through simple AI queries
Built-in capabilities (10)
Create candidate
Get application details
Get candidate details
Get job details
List applications
List candidates
List feedback
List interviews
List jobs
List users
Why Claude Desktop?
Claude Desktop is the definitive way to connect Ashby to your AI workflow. Add Vinkius Edge URL to your config, restart the app, and Claude immediately exposes all 10 tools in the chat interface. ask a question, Claude calls the right tool, and you see the answer. Zero code, zero context switching.
- —
Claude Desktop is the reference MCP client. it was designed alongside the protocol itself, ensuring the most complete and stable MCP implementation available
- —
Zero-code configuration: add a server URL to a JSON file and Claude instantly discovers and exposes all available tools in the chat interface
- —
Claude's extended thinking capability lets it reason through multi-step tool usage, chaining multiple API calls to answer complex questions
- —
Enterprise-grade security with local config storage. your tokens never leave your machine, and connections go directly to Vinkius Edge network
Ashby in Claude Desktop
Ashby and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect Ashby to Claude Desktop through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 4,000+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for Ashby in Claude Desktop
The Ashby MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 10 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in Claude Desktop only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
How Vinkius secures
Ashby for Claude Desktop
Every tool call from Claude Desktop to the Ashby MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
How do I find my Ashby API Key?
Log in as an Admin, navigate to Admin > API Keys, and generate a new key for your integration.
Can I retrieve interview feedback via AI?
Yes! The list_ashby_feedback tool allows your agent to retrieve high-fidelity feedback reports submitted by interviewers.
How do I create a new candidate record?
Use the create_ashby_candidate tool and provide a JSON object with the candidate's name and contact details programmatically.
How does Claude Desktop discover MCP tools?
When Claude Desktop starts, it reads the claude_desktop_config.json file and connects to each configured MCP server. It calls the tools/list endpoint to fetch the schema for every available tool, then surfaces them as clickable options in the chat interface via the 🔌 icon.
What happens if the MCP server is temporarily unavailable?
Claude Desktop handles disconnections gracefully. if the server is unreachable at startup, the tools simply won't appear. Once the server becomes available again, restarting Claude Desktop will re-establish the connection. There is no timeout penalty or error loop.
Can I connect multiple MCP servers simultaneously?
Yes. You can add as many servers as you need in the mcpServers section of the config file. Each server appears as a separate tool provider, and Claude can use tools from multiple servers in a single conversation turn.
Is there a limit on the number of tools per server?
Claude Desktop can handle hundreds of tools per server. However, for optimal LLM performance, Vinkius servers are designed to expose focused, well-documented tool sets rather than overwhelming the model with too many options.
Does Claude Desktop support Streamable HTTP transport?
Yes. Claude Desktop supports both SSE (Server-Sent Events) and the newer Streamable HTTP transport that Vinkius uses. Simply provide the server URL. Claude auto-negotiates the transport protocol.
Server not appearing after restart
Ensure the JSON is valid (no trailing commas). Check the file path: ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\\Claude\\ (Windows).
Authentication error
Verify your Vinkius token is correct. Go to cloud.vinkius.com to regenerate it if needed.
Tools not showing in chat
Click the 🔌 icon at the bottom of the chat input. If it shows 0 tools, the server may still be connecting. wait a few seconds.
Explore More MCP Servers
View all →
leadtributor.cloud
12 toolsDistribute leads to your sales team and partner network with routing rules, SLA tracking, and performance analytics.

HubSpot Analytics
5 toolsView web analytics, track events, list reports, and get email campaign statistics through natural conversation.
Everhour Time Tracking
10 toolsEquip your AI agent to track time, manage projects, and monitor budgets via the Everhour API.

D2L Brightspace
33 toolsManage your D2L Brightspace LMS — administer courses, track student grades, and manage enrollments directly through your AI agent.
