Skip to content
Custom Connectors
SolutionsConnectorsPricingResourcesBlog
Build my connector

Connect Workable to Claude Code

Let Claude advance candidates and add evaluations in Workable. From the terminal, inside the sessions where you already work.

Build my connectorTalk to us

How do you connect Workable to Claude Code?

Claude Code reaches outside tools through MCP servers. To connect Workable, you add a Workable MCP server: a small hosted service that exposes Workable's data and actions over the Model Context Protocol. With a custom connector we build for you, that is one command in the terminal, then an OAuth sign-in with your own Workable account. No API keys pasted into config files.

claude mcp add --transport http workable https://your-connector-url/mcp

Then run /mcp inside a Claude Code session to sign in. Add it with --scope project and the connector is checked into the repo for your whole team.

What can Claude Code do in Workable once connected?

Full read-write Workable access lets Claude move a candidate to the next stage, add evaluation scorecards and comments, tag candidates, disqualify with a reason, and copy or relocate a candidate to another job, all once you approve. The pipeline hygiene that used to mean clicking through each profile happens where the hiring data already lives.

  • Move a candidate to the next stage in a job pipeline
  • Add an evaluation comment or scorecard to a candidate profile
  • Tag or label candidates so a shortlist is easy to filter
  • Disqualify a candidate with a documented reason after you approve
  • Create a candidate record from a sourced profile
  • Copy or relocate a candidate to another job pipeline

One connector, every Claude surface

The connector we build is a remote MCP server, which is the same standard claude.ai and Claude Desktop use. Add it once and the same Workable access works in Claude Code for you, in claude.ai for the rest of the team, and in Claude Desktop. One build, one set of permissions, one monthly plan covering all of them.

Build it yourself, or have it built?

If you live in the terminal, you can absolutely write your own MCP server against the Workable API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when Workable changes its API and when the MCP spec itself moves, and scoping write actions so an agent can never do more than you intended. We build Workable connectors with separated read and write tools and approval gates on destructive actions, then host and maintain them so they keep working while you work.

Frequently asked questions

Does the same Workable connector work in claude.ai and Claude Code?
Yes. It is one remote MCP server. Claude Code adds it with a single "claude mcp add" command; claude.ai and Claude Desktop add it as a custom connector in Settings. Each person signs in with their own Workable account, so access always matches what that person can already see and do.
Do I need to host or maintain anything myself?
No. The connector runs as a hosted service we operate: we handle uptime, token health, API changes on Workable's side, and MCP spec migrations under the monthly plan. Your side is one command in the terminal and an OAuth sign-in.
Is it safe to give a coding agent write access to Workable?
Write access is scoped, not blanket. Read tools and write tools are separated, destructive actions like deleting or sending are gated behind your explicit approval, and the connector can never exceed the permissions of the Workable account it signs in with. Revoking access is one click in Workable.

More on the Workable connector

Workable connector for claude.aiDeel + Claude CodeJustworks + Claude CodePaychex + Claude Code

Tell us what you run. We'll build the connector.

Pick your tool, choose what Claude should do, and get an instant scope and price. No call required.

Build my connectorTalk to us