mcp-ashby
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| resolve_boardA | Turn a company name into the token that addresses its Ashby job board, and report every form that answered. search_jobs does this on its own, so call this when a name returns nothing and you want to see the spellings that were tried. |
| search_jobsA | Search the open postings of named companies on Ashby. Ashby publishes no index across its customers, so companies are required. Every filter runs here rather than at the source, and the answer reports how many postings declared nothing about a field it filtered on. Rows carry no description: read one posting with get_job. |
| get_jobA | Read one Ashby posting in full: its locations, its description and the pay ranges its company published. Ashby addresses a posting by board and identifier, both of which search_jobs returns. |
| list_filter_valuesA | List the words one Ashby board actually uses, with how many postings carry each, and how many declare nothing. Every board keeps its own departments and teams, so a filter written from another board's vocabulary narrows to nothing. |
| compare_compensationA | Put the pay ranges of one Ashby board side by side, one component at a time and one period at a time. Nothing is converted between currencies, summed across components or averaged: a third of the postings publish no range at all, and they are named rather than dropped. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool has a mostly distinct role: search, resolve board, read one posting, compare compensation, and list filter vocabulary. The main overlap is resolve_board versus search_jobs' internal board resolution, but the description explicitly frames resolve_board as a diagnostic fallback when a name fails. get_job and compare_compensation also both involve pay data, though one is per-posting detail and the other is board-level comparison.
All five tools follow a clean snake_case verb_noun pattern: search_jobs, resolve_board, get_job, compare_compensation, list_filter_values. There are no mixed conventions or vague standalone verbs.
Five tools is well-scoped for an Ashby job-search server, with each tool covering a clear part of the workflow. Search, board resolution, detail retrieval, compensation comparison, and filter vocabulary all earn their place without redundancy.
The surface covers the core read-only job research workflow: finding postings, resolving company boards, reading full postings, comparing compensation, and discovering valid filters. Minor gaps remain around direct posting lookup by URL or broader company discovery, but Ashby's lack of a cross-customer index makes the current shape reasonable.