Ashby MCP integration for AI agents.
Connect AI agents to Ashby through 4 structured actions, including list candidates, api key info, and list jobs. Review authentication, inputs, workflows, an…
- ACTION CONTRACTS
- 4
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Ashby integration exposes
The Ashby Agent App exposes 4 provider-backed actions for productivity and data work. Its current contract lets an authorized agent list ashby candidates with optional pagination and incremental sync filters, retrieve information about the ashby api key used for this connection, and list ashby jobs with optional status, timestamp, expansion, pagination, and sync filters. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected Ashby account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Ashby capabilities.
Showing 4 of 4 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
list_candidatesREADList Ashby candidates with optional pagination and incremental sync filters.
INPUTS: createdAfter / cursor / syncToken / limit
api_key_infoREVIEWRetrieve information about the Ashby API key used for this connection.
list_jobsREADList Ashby jobs with optional status, timestamp, expansion, pagination, and sync filters.
INPUTS: createdAfter / cursor / syncToken / limit / status
search_candidatesREADSearch Ashby candidates by email and/or name for small result sets such as autocomplete.
INPUTS: email / name
INPUT CONTRACTS
Know what the action needs before it runs.
list_candidates
createdAfterOPTIONAL- A timestamp in milliseconds since the Unix epoch.
cursorOPTIONAL- Opaque cursor indicating which page of Ashby results to fetch.
syncTokenOPTIONAL- Opaque token representing the last successful Ashby incremental sync.
limitOPTIONAL- The maximum number of items to return. The maximum is 100.
list_jobs
createdAfterOPTIONAL- A timestamp in milliseconds since the Unix epoch.
cursorOPTIONAL- Opaque cursor indicating which page of Ashby results to fetch.
syncTokenOPTIONAL- Opaque token representing the last successful Ashby incremental sync.
limitOPTIONAL- The maximum number of items to return. The maximum is 100.
statusOPTIONAL- When supplied, only jobs with the provided status values are returned.
search_candidates
emailOPTIONAL- The candidate email address to search for.
nameOPTIONAL- The candidate name to search for.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect List Candidates
List Ashby candidates with optional pagination and incremental sync filters. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
list_candidatesVerify with List Jobs
List Ashby jobs with optional status, timestamp, expansion, pagination, and sync filters. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
list_jobsSAFETY BOUNDARY
Operate Ashby with explicit limits
- Authorize Ashby with API key and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned Ashby data may still be sensitive and should be minimized before it enters model context.
- Do not infer permission from catalog visibility. Workspace policy, connection identity, and upstream authorization still govern execution.
- The sampled contract declares provider scopes including `candidatesRead` and `jobsRead`; verify the complete action contract before execution.
- After a call, inspect the structured result and execution record before reporting that the Ashby task completed successfully.
CONNECTION MODEL
API key
Ashby API key used as the Basic Auth username. Create or manage API keys in Ashby Admin > Integrations > API Keys: https://app.ashbyhq.com/admin/api/keys.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 3
- WRITE SIGNALS
- 0
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 1
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Ashby.