Ashby MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| COTLET_API_KEY | Yes | Your Cotlet.dev API key. Required for Codex, Claude Code, and the optional local stdio bridge to execute tools. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
Ashby through Cotlet.dev. Call ashby_guide first. Set COTLET_API_KEY (https://cotlet.dev/app).
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| ashby_guideA | How to work in Ashby (jobs, candidates, interviews and offers): its screens and the sign-in link. Call this first. |
| ashby_statusA | Check that your Cotlet.dev account and Ashby are ready: account, credits and Ashby connection. |
| ashby_openA | Open a Ashby page in your signed-in Cloud Browser (default https://app.ashbyhq.com) to work with jobs, candidates, interviews and offers. |
| ashby_readB | Read the current Ashby page: its text and numbered buttons, links and fields. |
| ashby_clickB | Click a numbered element on the current Ashby page. |
| ashby_typeC | Type text into a numbered field on the current Ashby page. |
| ashby_closeA | Close the Ashby browser session when the work is done, so credits stop running. |
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 7 tools
Each tool maps to a clearly distinct step in a browser session lifecycle: guide (instructions), status (readiness), open (navigate), read (inspect), click (interact), type (input), close (teardown). The two informational tools (guide vs status) are the closest pair, but their descriptions clearly separate onboarding guidance from account/connection verification.
All tools use the same ashby_ prefix followed by a single verb in snake_case (open, read, click, type, close, guide, status). No mixed conventions or vague multi-word names; the pattern is immediately predictable.
Seven tools is well-scoped for a single-site browser automation server: one tool per primitive action plus setup/teardown and help. Nothing feels redundant or padded, and nothing essential to the loop is missing at this count.
The core loop (open → read → click/type → close) plus session management and help covers the stated purpose. Minor gaps exist, such as scrolling/navigation back, waiting for page loads, or keyboard submit (Enter), which agents may need on long or dynamically loading Ashby pages, but these are workable through read+click.