Skip to content
Workable logo

Workable MCP server

Give your AI assistant 21 tools it can call in Workable, over one server URL.

Workable is not a separate install. One Activepieces MCP server exposes it alongside 770+ other apps, behind a single URL.

Tools
21
Works with
Any MCP client
Auth
API key
License
MIT, open source
Updated
November 2026

About the Workable MCP server

Connect Workable once in Activepieces and every action it ships becomes a tool your assistant can call, behind the same server URL as the rest of your apps. Your agent reaches Workable and 770+ other apps over a single connection, on our cloud or a self-hosted install.

Tools

Workable tools your AI can run

Once connected, your assistant can call any of these Workable actions by asking in plain language.

  • Get Candidate

    Gets a candidate's full profile.

    2 fields

  • Get Members

    Lists members of the hiring team, one page at a time.

    7 fields

  • Get Job

    Gets the details of a job.

    3 fields

  • Get Stages

    Lists the pipeline stages of a job, or of the account when no job is given.

    2 fields

  • Move Candidate

    Moves a candidate to another stage of their job pipeline.

    5 fields

  • Rate Candidate

    Adds a rating with a comment to a candidate.

    6 fields

  • List Candidates

    Finds candidates by email, job, stage or date, one page at a time.

    8 fields

  • List Jobs

    Lists jobs, optionally by state or date, one page at a time.

    6 fields

  • Create Candidate

    Adds a candidate to a job, or to the talent pool when no job is selected.

    15 fields

  • Update Candidate

    Updates a candidate's profile. Empty fields are left unchanged.

    12 fields

  • Add Comment

    Adds a comment to a candidate's timeline.

    5 fields

  • Disqualify Candidate

    Disqualifies a candidate, with an optional reason and note.

    6 fields

  • Revert Disqualification

    Brings a disqualified candidate back into the pipeline.

    3 fields

  • Add Candidate Tags

    Adds tags to a candidate and keeps the tags they already have.

    3 fields

  • List Disqualification Reasons

    Lists the disqualification reasons set up in the account.

    1 field

  • List Recruiters

    Lists external recruiters of the account or of one job.

    2 fields

  • List Job Questions

    Lists the application form questions of a job.

    2 fields

  • Get Candidate Activities

    Gets a candidate's timeline: comments, stage moves, ratings and more.

    2 fields

  • Copy Candidate to Job

    Copies a candidate to another job. The original stays where it is.

    5 fields

  • List Accounts

    Lists the Workable accounts this token can use, with their subdomains.

  • Custom API Call

    Make a custom API call to your Workable account (https://{subdomain}.workable.com/spi/v3).

    11 fields

Triggers

Workable events your agent can watch

These start a run the moment something happens in Workable, so work gets picked up on its own.

  • New Candidate

    Triggers when a new candidate is added. Can be filtered by job and pipeline stage.

    4 fields

  • Candidate Stage Changed

    Triggers when a candidate is moved to another stage. Can be filtered by job and target stage.

    4 fields

Give your assistant Workable

Connect Workable once and every tool above is callable from Claude, Cursor or any MCP client, behind the same server URL as 770+ other apps. Free to start.

Workable MCP, answered.

No. That is the point of it. One Activepieces server exposes Workable alongside every other piece you connect, so your client keeps a single connection.

Yes. Activepieces is open source and free to start, and the MCP server is included on every plan, from the free cloud tier to any self-hosted deployment.

Connect Workable in Activepieces, enable the server under Settings → MCP Server, then paste your server URL into your client config. It authenticates over OAuth on first use.

It can call 21 tools, including Get Candidate, Get Members, Get Job, and chain them with steps in other apps inside the same run.

Connections use OAuth2 with limited scopes and are stored under 256-bit encryption, with no API to read them back, so an agent gets scoped access rather than your keys.