Top
Request a demo Start a free trial

Connecting Workable to Claude

  • all plans

Connect Workable to Claude to find recruiting and HR information and take actions in your Workable account through conversation. The Workable Model Context Protocol (MCP) server provides tools for jobs, candidates, employees, requisitions, offers, time off and more.

 

Before you start

  • An active Workable account and a user with access to the information and actions you want to use.
  • A Claude account with access to the Workable connector.
  • For a managed workspace, permission to use the Workable connector under your organization’s connector policy.
  • A browser that allows the Workable sign-in window.

The MCP server is available on all Workable subscription tiers. HR tools require the corresponding Workable products to be enabled on your account.

The assistant’s access depends on the signed-in user’s Workable permissions. It can only access information and perform actions available to that user in Workable.

 

Setting up the connection

Workable is available in Claude’s official connector directory. Select the existing Workable connector to get started.

  1. Open Claude and go to Settings > Customize > Connectors.
  2. Locate the Workable connector by using the search bar and select Connect.
  3. Sign in to Workable, review permissions and authorize the connection.

Workable uses OAuth authentication. Sign in through the Workable authorization window; no separate API key is required.

 

Testing the connection

Start a new conversation and ask Claude to use Workable:

Use Workable to list the accounts I can access. Call get_accounts first, then use my chosen account’s subdomain as the account argument on subsequent calls. Show the open jobs in that account.

If you have access to multiple Workable accounts, specify which one to use. Check the tool activity for get_accounts, followed by get_jobs, and compare the results with Workable.

Once connected, you can also try:

  • “Which candidates applied for the Senior Backend Engineer role this week, and where are they in the pipeline?”
  • “Show me the requisitions waiting on my approval.”
  • “Who is out of office in the Berlin office next month?”

Results depend on your permissions, enabled products and available tools. Review the record and requested change before approving an action that updates Workable.

 

Troubleshooting the connection

I cannot add or enable the connector

Find Workable in Claude’s official connector directory and check your workspace’s connector policy. If access is restricted, ask your administrator to enable or approve the Workable connector, then connect with your own Workable login.

Claude does not use Workable

Check that Workable is connected in Claude’s connector settings, then ask Claude explicitly to use Workable. Confirm that you completed Workable authorization.

The expected account or information is missing

Ask the assistant to call get_accounts again and select the correct account subdomain. Check that the signed-in Workable user can see the same information directly in Workable and that the required product is enabled.

The connection fails or a Workable tool returns an error
  • 401 Unauthorized: Reconnect and sign in to Workable again.
  • 403 Forbidden: Check your Workable permissions and enabled products.
  • 404 Not found: Check the account subdomain and record.
  • 409 Conflict: Check the record’s current state before retrying.
  • 422 Unprocessable: Check the supplied values against the options in Workable.
  • 429 Rate limited: Wait briefly before trying again.

If an OAuth redirect URI mismatch appears, contact Workable Support with the error and redirect URI. Do not include passwords or access tokens.

 

For the full list of supported tasks, see Using the Workable MCP server to connect to AI assistant.

Related articles