mcp-ashby

Ashby is recruiting software, and every company using it gets a public job board that comes with it. Each board carries that company's open positions with their title, their department and team, the employment type, the locations and whether the work is remote, the full advert, and, where the company chose to publish it, the pay: a salary range, an equity share, a commission or a bonus, each with the period it is quoted over. Ashby holds one board per company and publishes no index across them.

This server connects a chat client to those boards. You name the companies you are interested in, and it turns each name into the token that addresses its board, searches their postings, filters them by department, team, location, country, employment type, remoteness, recency or pay, reads one posting in full, lists the words each board actually uses, and puts the pay of several postings side by side. It needs no API key and no account.

Version française

Install

One-click install

Claude Code

claude mcp add ashby -- npx -y mcp-ashby

Claude Desktop, Cursor, and any client using the standard config format

{
  "mcpServers": {
    "ashby": {
      "command": "npx",
      "args": ["-y", "mcp-ashby"]
    }
  }
}

Node 24 or later is required, and no environment variable has to be set.

With Docker

{
  "mcpServers": {
    "ashby": {
      "command": "docker",
      "args": ["run", "-i", "--rm", "ghcr.io/smeet666/mcp-ashby:2.0.1"]
    }
  }
}

-i keeps stdin open, which is where the protocol travels, and -t is left out because a TTY rewrites the stream. The container needs outbound HTTPS to api.ashbyhq.com, and nothing else: no volume, no port, no credential.

Bundle, without npm

Download mcp-ashby-2.0.1.mcpb from the latest release and open it. A client that supports MCP bundles installs it on its own, with no npm and no configuration file to edit. The bundle carries its dependencies, so nothing is fetched at install time.

What you can ask

• "Is Ramp hiring on Ashby?"
• "Find me remote design roles at Ramp and Linear."
• "Read me that posting in full."
• "What departments does that board file its jobs under?"
• "Put the salaries of those engineering postings side by side."

Every question starts from a company, since Ashby offers no search across boards. search_jobs resolves the names you give it, so no preparation is needed:

resolve_board(["Ramp"])          ->  ramp, publishing
search_jobs(["Ramp"], query: "designer", is_remote: true)
get_job("ramp", "b0c8…")

Tools

Every board keeps its own departments and teams, so a filter written from another board's vocabulary narrows to nothing. list_filter_values publishes the words a board actually uses.

resolve_board

Turns a company name into the token that addresses its Ashby board.

In return: found, the boards that answered, and tried, the forms actually sent in order. Four forms are tried per name, so nothing found is never proof that a company is absent from Ashby.

search_jobs

Searches the postings of the companies named. Ashby serves a whole board at once, and every restriction below is applied to what was read.