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 MCP Integration for Vercel AI SDK

Connect Ashby to Vercel AI SDK through the local KosmoKrator MCP gateway with scoped tools, credentials, and write policy.

7 functions 7 read 0 write Bearer token auth

Submit Ashby feedback View package source

Connect Ashby to Vercel AI SDK

Use KosmoKrator as a local integration gateway for Vercel AI SDK agents and scripts.

Create an MCP client that starts or connects to the KosmoKrator gateway for the selected integration. The gateway is local, scoped to this integration, and starts with --write=deny so Vercel AI SDK can inspect read-capable tools without receiving write access by default.

Ashby MCP Config for Vercel AI SDK

Prefer CLI JSON calls when a workflow only needs one deterministic integration operation.

{
  "mcpServers": {
    "kosmokrator-ashby": {
      "type": "stdio",
      "command": "kosmo",
      "args": [
        "mcp:serve",
        "--integration=ashby",
        "--write=deny"
      ]
    }
  }
}

Run the Gateway Manually

kosmokrator mcp:serve --integration=ashby --write=deny

Why Use KosmoKrator Here

Scoped tools

Expose only Ashby instead of a broad multi-service tool list.

Local credentials

Reuse credentials already configured for the KosmoKrator CLI and Lua runtime.

Write policy

Start read-only, then opt into ask or allow for trusted workspaces.

Ashby Tools Visible to Vercel AI SDK

Vercel AI SDK sees stable MCP tool names generated from the Ashby integration catalog.

MCP tool	Source function	Type	Description
`integration__ashby__ashby_get_application`	`ashby.ashby_get_application`	Read	Get detailed information about a specific job application in Ashby, including candidate details, status, and evaluation data.
`integration__ashby__ashby_get_current_user`	`ashby.ashby_get_current_user`	Read	Get the profile of the currently authenticated Ashby user. Use this to verify API access and see user details.
`integration__ashby__ashby_get_interview`	`ashby.ashby_get_interview`	Read	Get detailed information about a specific interview in Ashby, including scheduled time, interviewers, feedback, and scorecards.
`integration__ashby__ashby_get_job`	`ashby.ashby_get_job`	Read	Get detailed information about a specific job in Ashby, including full description, requirements, compensation, and hiring team.
`integration__ashby__ashby_list_applications`	`ashby.ashby_list_applications`	Read	List job applications in Ashby. Returns applications with candidate info, status, and associated job. Use filters to narrow by job or status.
`integration__ashby__ashby_list_interviews`	`ashby.ashby_list_interviews`	Read	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.
`integration__ashby__ashby_list_jobs`	`ashby.ashby_list_jobs`	Read	List job postings in Ashby. Returns open and closed positions with department, location, and application count. Filter by status to find active openings.

Related Ashby Pages

Ashby CLIUse direct JSON commands instead of MCP discovery. Ashby MCPFull gateway reference and MCP tool names. KosmoKrator for Vercel AI SDKClient-level gateway setup.