Can I use Ashby as a CLI?

Yes. KosmoKrator exposes a Ashby CLI through kosmo integrations:call and the provider shortcut command. Commands can return JSON for scripts, CI, and coding agents.

Can I expose Ashby through MCP?

Yes. The KosmoKrator MCP gateway can expose selected Ashby tools to clients such as Claude Code, Cursor, Codex, and other MCP-compatible tools.

Where are Ashby credentials stored?

Ashby credentials are configured in KosmoKrator's local integration settings and reused by CLI, Lua, and MCP gateway surfaces.

Can I deny write access for Ashby MCP tools?

Yes. Start the gateway with --write=deny for read-only clients, or use ask/allow only for trusted workspaces.

Ashby CLI for Shell Scripts

Use the Ashby CLI for shell scripts with headless JSON commands, schema discovery, credentials, and permission controls.

7 functions 7 read 0 write Bearer token auth

Submit Ashby feedback View package source

Ashby CLI for Shell Scripts

Call integration functions from shell scripts with stable JSON input and output.

Use shell scripts for small local automations that need one or more integration calls. The Ashby CLI uses the same integration registry as the TUI, Lua runtime, and MCP gateway, but returns predictable command output for automation.

Command Shape

# Ashby CLI for Shell Scripts
kosmokrator integrations:configure ashby --set access_token="$ASHBY_ACCESS_TOKEN" --enable --read allow --write ask --json
kosmo integrations:call ashby.ashby_get_application '{"id":"example_id"}' --json

Discovery Before Execution

Agents and scripts can inspect Ashby docs and schemas before choosing a function.

kosmo integrations:docs ashby --json
kosmo integrations:docs ashby.ashby_get_application --json
kosmo integrations:schema ashby.ashby_get_application --json
kosmo integrations:search "Ashby" --json
kosmo integrations:list --json

Useful Ashby CLI Functions

Function	Type	Parameters	Description
`ashby.ashby_get_application`	Read	id	Get detailed information about a specific job application in Ashby, including candidate details, status, and evaluation data.
`ashby.ashby_get_current_user`	Read	none	Get the profile of the currently authenticated Ashby user. Use this to verify API access and see user details.
`ashby.ashby_get_interview`	Read	id	Get detailed information about a specific interview in Ashby, including scheduled time, interviewers, feedback, and scorecards.
`ashby.ashby_get_job`	Read	id	Get detailed information about a specific job in Ashby, including full description, requirements, compensation, and hiring team.
`ashby.ashby_list_applications`	Read	limit, offset, job_id, status	List job applications in Ashby. Returns applications with candidate info, status, and associated job. Use filters to narrow by job or status.
`ashby.ashby_list_interviews`	Read	limit, offset, application_id	List scheduled interviews in Ashby. Returns interview details with date, time, interviewers, and associated application. Filter by application to see interviews for a specific candidate.
`ashby.ashby_list_jobs`	Read	limit, offset, status	List job postings in Ashby. Returns open and closed positions with department, location, and application count. Filter by status to find active openings.

Automation Notes

Use --json for machine-readable output.
Keep credentials out of argv by using environment variables or stored KosmoKrator configuration.
Configure read/write policy before unattended runs; use --force only for trusted automation.
Use the MCP gateway instead when the agent needs dynamic tool discovery inside a conversation.

Related Ashby CLI Pages

CI Ashby CLI for CI. Cron Jobs Ashby CLI for cron jobs. Headless Automation Ashby CLI for headless automation. Coding Agents Ashby CLI for coding agents.