Ashby

This MCP server enables a direct bridge between your LLM workflows and Ashby’s Applicant Tracking System data and operations. It supports managing candidates, jobs, applications, interviews, and provides analytics and batch operations to streamline recruiting tasks.

How to use

You connect your MCP client to the Ashby MCP server by configuring an MCP server entry and starting the local connector. Once running, your client can perform operations like creating or listing candidates and jobs, managing applications, scheduling interviews, and retrieving pipeline analytics. Use the standard MCP workflow you already rely on for other data sources to query Ashby data and trigger Ashby actions from your LLM prompts.

How to install

{
  "mcpServers": {
    "ashby": {
      "command": "uvx",
      "args": [
        "--from",
        "mcp-ashby-connector",
        "ashby"
      ],
      "env": {
        "ASHBY_API_KEY": "YOUR_ASHBY_API_KEY"
      }
    }
  }
}

Replace YOUR_ASHBY_API_KEY with your Ashby API key.

Prerequisites:

• Python (for the Ashby MCP server runtime and dependencies) — ensure Python 3.x is installed.
• uvx runtime available on your system (as shown in the command snippet).
• An Ashby API key with access to the required ATS data and operations.

Install steps:

• Prepare the MCP configuration by creating or editing your MCP configuration file to include the ashby entry exactly as shown above.
• Ensure your environment has the ASHBY_API_KEY variable set if you prefer environment variable injection, or embed it directly in the config as shown.
• Start the MCP server by running the installed uvx binary with the provided arguments from the config.

Run command (as shown in the configuration):

uvx --from mcp-ashby-connector ashby

If you use a shell script or a startup utility to apply the config, make sure the env var ASHBY_API_KEY is available to the process at startup.

## Additional notes and setup details

This connector is designed to be loaded via the standard MCP runtime. The supported operations mirror Ashby entities and actions: candidates, jobs, applications, interviews, analytics, and batch operations. When you start the connector, it will expose endpoints through the MCP interface that your client library can call in the same way you interact with other MCP servers.

## Available tools

### Candidate Management

Create, search, and list candidates within Ashby through the MCP interface.

### Job Management

Create, search, and list job postings within Ashby via MCP.

### Application Management

Create, list, and update candidate applications to jobs in Ashby.

### Interview Management

Create, list, and schedule interviews for candidates in Ashby.

### Analytics & Reporting

Retrieve pipeline metrics and analytics from Ashby to inform decisions.

### Batch Operations

Perform bulk create, update, or schedule operations to streamline recruiting workflows.