Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@ashby find candidates who applied for the backend role"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Ashby MCP Pack — wraps the Ashby ATS API
Part of Pipeworx — an MCP gateway connecting AI agents to 1476+ live data sources.
Tool | Description |
| Search candidates in your ATS. Returns names, emails, and application metadata. Use ashby_get_candidate with ID for full profile details. |
| Get full candidate profile by ID. Returns contact info, resume, interview history, and current application status. |
| Search open positions. Filter by status (open, closed, draft, archived). Returns job title, department, and posting details. |
| Get full job posting by ID. Returns description, requirements, hiring stage, and applicant count. |
| Search job applications across positions. Returns candidate name, applied job, application stage, and submission date. |
Related MCP server: MCP Ashby Connector
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"ashby": {
"url": "https://gateway.pipeworx.io/ashby/mcp"
}
}
}tools/list at https://gateway.pipeworx.io/ashby/mcp returns the tools in the table
above plus the shared Pipeworx meta-tools — ask_pipeworx,
discover_tools, search_within, remember/recall and the rest of the
gateway-wide set. So the tool count you see is larger than this table: a
single-pack endpoint currently lists roughly 30 shared tools alongside the
pack's own. The connection's initialize response states its exact scope, and
is the authoritative answer for a given day.
This is deliberate, not multiplexing by accident. The meta-tools are what let a
scoped connection answer a question this pack does not cover — via
ask_pipeworx, which routes across the whole catalog — without you adding a
second MCP server. There is currently no way to mount a pack endpoint without
them; if the extra schemas cost you more context than the routing is worth,
connect to the full gateway once rather than to several pack endpoints.
Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:
{
"mcpServers": {
"pipeworx": {
"url": "https://gateway.pipeworx.io/mcp"
}
}
}Both URLs reach the same gateway and the same 1476+ data sources. The
only difference is which pack's tools are listed directly; ask_pipeworx
reaches all of them from either one.
Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:
ask_pipeworx({ question: "your question about Ashby data" })The gateway picks the right tool and fills the arguments automatically.
MIT
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
No tool schema history has been recorded yet.
This server cannot be installed
Unclaimed servers have limited discoverability.
If you are the server author, to access and configure the admin panel.
Ashby ATS job scraper pulls live postings via API with team filtering.
Manage job applications — jobs, companies, boards, notes, and profile — from your AI client.
Query professional profiles, search candidates, and get AI-powered summaries and job fit analysis.
Ashby job boards with employer-published salary data, via an Apify Actor, hosted MCP.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/pipeworx-io/mcp-ashby'
If you have feedback or need assistance with the MCP directory API, please join our Discord server
