Connect Ashby ATS to OpenCode
Give OpenCode governed access to Ashby ATS’s 16 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Ashby ATS to OpenCode in four steps
Admins approve the server once. Everyone in OpenCode then gets it through the same governed connection.
- 1
Approve Ashby ATS in Runlayer
Add Ashby ATS from the catalog and choose who can use it and which of its tools are allowed.
- 2
Connect OpenCode to Runlayer
Users add the Runlayer Plugin to OpenCode by hand using Runlayer’s generic MCP steps. OpenCode reaches Ashby ATS’s 16 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.
OpenCode setup guide - 3
Sign in to Ashby ATS
Each user signs in to Ashby ATS with OAuth. Runlayer keeps the tokens out of the client’s configuration.
- 4
Use Ashby ATS from OpenCode
Ashby ATS’s approved tools appear in OpenCode. Every call is checked against policy and recorded.
Tools
16 Ashby ATS tools in OpenCode
Runlayer policy decides which of these OpenCode users can call.
Add note to candidate
Add a note to a candidate's profile.
Change application stage
Move an application to a different interview stage.
Consider candidate for job
Create a new application for a candidate on a specific job.
Create candidate
Create a new candidate record in Ashby with a name and optional contact information.
Describe object fields
Look up filterable fields for a given object type.
Filter records
Filter records of a given object type using a structured JSON filter.
Get candidate
Fetch details about one or more candidates.
Get interview details
Get a detailed interview briefing for a specific Ashby interview event.
Control
What Runlayer can see and stop in OpenCode
Some controls apply to every client at the gateway. Others depend on what OpenCode exposes to Runlayer.
Gateway policy (available)
Every Ashby ATS call from OpenCode passes through Runlayer, where your policies can allow, alert, mask, or block it.
Audit trail (available)
Each call is recorded with the user, OpenCode as the client, the tool, and the policy and scanner decisions.
Native enforcement adapter (not available)
Runlayer has no device-side adapter for OpenCode yet, so control happens at the gateway.
Frequently asked questions
Connect more
