Skip to content

ATS

Workable MCP connector

Connect Workable to Elaichi and Claude, ChatGPT, Cursor, Microsoft Copilot or any MCP client can search jobs, review candidates, add new ones, move them through stages and update records, all within the signed-in person's own Workable access.

  • Connects over OAuth
  • Free 14-day trial
  • No credit card
Claude Elaichi connected

Which candidates moved to the offer stage this week?

Working in Workable with Elaichi

  • Get accounts
  • Get jobs
  • Search jobs
Ask anything…
Governance / Audit log Last 24 hours
Workable Search jobs Emily Carter · Claude · 9:41 AM Done
Workable Get jobs Emily Carter · Claude · 9:41 AM Done
Workable Get accounts Emily Carter · Claude · 9:41 AM Done
Workable Get job Megan Brooks · ChatGPT · 9:38 AM Done
Workable Get job activities Ryan Hayes · Cursor · 9:35 AM Done

How to connect Workable to Claude, ChatGPT, Cursor or Microsoft Copilot

Step by step, for each AI app

Workable MCP connector for Claude

  1. 1

    Open Customize, then Connectors.

  2. 2

    Press Add.

  3. 3

    Name it, paste the MCP server URL, then Continue.

    https://api.elaichi.ai/mcp
  4. 4

    Sign in and approve.

On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.

Workable MCP connector for Claude Code

  1. 1

    In a terminal, run claude mcp add with the endpoint.

    https://api.elaichi.ai/mcp
  2. 2

    Start Claude Code and run /mcp.

  3. 3

    Pick elaichi, then sign in and approve in the browser.

Terminal

$ claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp

Use --scope project instead to share it with the repository through .mcp.json.

Workable MCP connector for ChatGPT

  1. 1

    Open Plugins, then press the + button.

  2. 2

    Name it and paste the endpoint into Server URL.

    https://api.elaichi.ai/mcp
  3. 3

    Leave Authentication on OAuth, then tick the risk acknowledgement.

  4. 4

    Press Create, then sign in and approve.

Works on the web. The plugin directory lives at chatgpt.com/plugins.

Workable MCP connector for Cursor

  1. 1

    Open ~/.cursor/mcp.json.

  2. 2

    Add the endpoint under mcpServers.

    https://api.elaichi.ai/mcp
  3. 3

    Reload Cursor, then sign in and approve.

~/.cursor/mcp.json

{
  "mcpServers": {
    "elaichi": {
      "url": "https://api.elaichi.ai/mcp"
    }
  }
}

Set up per machine, so repeat it on each computer you work from.

Workable MCP connector for Microsoft Copilot

  1. 1

    In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.

  2. 2

    Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.

    https://api.elaichi.ai/mcp
  3. 3

    Create a new connection, sign in and approve, then press Add to agent.

  4. 4

    Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.

Server URL
https://api.elaichi.ai/mcp
Authentication
OAuth 2.0
Type
Dynamic discovery

Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.

Connect Workable to any MCP client

  1. 1

    Add the endpoint as a remote MCP server.

    https://api.elaichi.ai/mcp
  2. 2

    Sign in and approve.

{
  "mcpServers": {
    "elaichi": {
      "url": "https://api.elaichi.ai/mcp"
    }
  }
}

The Elaichi Agent already has these tools, with nothing to set up.

What teams do with Workable through Elaichi

Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Workable is logged.

  • Recruiting

    Catch a candidate up after a screen

    Finish a phone screen, say what you learned, and the candidate's record in Workable is updated and moved to the next stage while it is still fresh.

  • Recruiting

    Give a strong runner-up another job

    When a good candidate loses out on one role, copy or relocate them to a better matching open job in Workable instead of letting them go cold.

  • Hiring managers

    See where a job's pipeline stands

    Ask how many candidates sit at each stage of your open role, who has been waiting longest, and what happened on it this week, without opening Workable.

  • Sourcing

    Add found profiles to the talent pool

    Paste the details of someone promising and they land in the Workable talent pool or on a specific job, ready for the recruiter to pick up.

  • Recruiting coordinators

    Clear the queue of pending decisions

    Advance the candidates the panel approved, disqualify the rest with a reason, and reverse a disqualification when a manager changes their mind.

  • People Ops

    Check an offer before the start date

    Pull up a candidate's offer, their files and the activity on their application so onboarding begins with the right title, salary and start date.

Try asking

  • “Which candidates moved to the offer stage this week?”
  • “Show open jobs with nobody past the phone screen stage.”
  • “Move Priya Shah to the interview stage for Account Executive.”

See all 94 Workable tools →

What connecting Workable gets you

6 screens from Elaichi, each doing one job for your Workable account.

Elaichi Agent

Ask Elaichi to work across your apps.

Which candidates moved to the offer stage this week?

Show open jobs with nobody past the phone screen stage.

Move Priya Shah to the interview stage for Account Executive.

Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot

The agent

Ask about candidates, get answers from Workable.

Type a question about a job or candidate and the agent reads live Workable records.

ElaichiAI apps
Claude ChatGPT Cursor Microsoft Copilot

Copy the endpoint

https://api.elaichi.ai/mcp
Client Connected by Status Last used
Claude
E

Emily Carter

• Connected 4 minutes ago
Cursor
M

Megan Brooks

• Connected 2 hours ago
ChatGPT
R

Ryan Hayes

• Connected Yesterday

AI apps

Workable in Claude, ChatGPT, Cursor and Microsoft Copilot at once.

One governed endpoint, every MCP client, no SDK and no shared API key.

ElaichiTools
Tool Action Description
Get accounts Get List all Workable accounts accessible to the authenticated user. **Call this first** — use the returned `subdomain` as the `account` parameter on every other tool
Get jobs Get List jobs filtered by state (`published`, `draft`, `archived`, `closed`)
Search jobs Search Find jobs by a full or partial job title and get back each match's shortcode, title, state, and id. Use this when you have a job name but not its shortcode — the returned shortcode can be passed to other job-scoped tools (`get_candidates`, `get_job_stages`, `get_job_members`).…
Get job Get Get full details for a specific job by shortcode
Get job activities Get Get the activity log for a specific job

Tool catalog

94 Workable tools, no code to write.

Jobs, candidates, stages, offers and files, covered without building a line of custom code.

ElaichiToolboxes
Name Source template Tools Created

Recruiting toolbox

Workable · jobs, pipelines and candidates

Workable starter 18 Mar 4, 2026

Hiring managers toolbox

Workable · candidates on their own jobs

— 9 Mar 2, 2026

Sourcing toolbox

Workable · talent pool candidates

— 24 Feb 27, 2026

Coordinators toolbox

Workable · stage moves and disqualifications

Workable starter 6 Feb 19, 2026

People Ops toolbox

Workable · offers and candidate files

— 31 Jan 30, 2026

Talent leadership toolbox

Workable · job activity and pipeline health

— 12 Jan 22, 2026

Toolboxes

Each team gets its own Workable toolbox.

Recruiters, hiring managers and sourcers each see the Workable tools their work needs.

ElaichiConnections
Connection Scope Status Access
WO

Workable (Recruiting)

Connected by Emily Carter

Personal • Active 1 team · 6 members
WO

Workable (Engineering hiring)

Connected by Jake Morgan

Organization • Active 3 teams · 24 members
WO

Workable (Sales hiring)

Connected by Megan Brooks

Organization • Active 2 teams · 11 members
WO

Workable (Sourcing)

Connected by Tyler Reed

Personal • Needs re-auth 1 team · 3 members
WO

Workable (People Ops)

Connected by Ryan Hayes

Personal • Active Not shared
WO

Workable (Agency partners)

Connected by Ashley Parker

Personal • Active 2 teams · 9 members

Shared connections

One Workable connection, shared without sharing passwords.

See who connected each Workable account and which teams and members work through it.

ElaichiAudit log
When Who What happened Type

2 minutes ago

Mar 6, 2026, 3:10 PM

E

Emily Carter

[email protected]

Restriction Created Access

8 minutes ago

Mar 6, 2026, 3:04 PM

J

Jake Morgan

[email protected]

Restriction Updated Access

14 minutes ago

Mar 6, 2026, 2:58 PM

M

Megan Brooks

[email protected]

Role Assigned Access

20 minutes ago

Mar 6, 2026, 2:52 PM

T

Tyler Reed

[email protected]

Workable Users Updated MCP

26 minutes ago

Mar 6, 2026, 2:46 PM

R

Ryan Hayes

[email protected]

Workable Jobs Created MCP

32 minutes ago

Mar 6, 2026, 2:40 PM

A

Ashley Parker

[email protected]

Workable Jobs List Toolbox

Audit log

Every Workable action has a name on it.

When, who, what happened and which candidate or job, in an append-only log.

From answering questions to doing the work

A trigger starts the work, inside the same permissions and the same audit log as everything else. Workflows, collections and live dashboards come with the Black plan.

Workable digest

Run 418 · started 2 minutes ago · on behalf of Emily Carter

  1. ✓

    Schedule

    Every weekday at 8:00 AM

    0.2s
  2. ✓

    Fetch jobs

    Workable

    1.4s
  3. ✓

    Group by owner

    Transform

    0.1s
  4. ✓

    Draft the digest

    Agent step

    Ran with 4 tools, returned a structured summary

    6.2s
  5. Approve the digest

    Needs approval

    Assigned to Jake Morgan

    Approve
  6. Post the digest

    Workable

    Queued

Workflows

The pipeline digest writes itself each morning.

New Workable candidates are fetched, grouped by job, drafted, approved by a person, then posted back.

Workable health

Refreshed 4 minutes ago · every 15 minutes · from the jobs collection

Live

Jobs

1,284 ↓ 12%

Candidates

96 ↓ 8%

Needs attention

3 ↑ 2

Updated this week

412 ↑ 9%

Jobs created

Last 14 days

By team

Share of activity

Recruiting 34%

Engineering hiring 27%

Sales hiring 21%

Sourcing 18%

Collections and dashboards

Hiring numbers from Workable, computed without a model.

Four metrics, 14 days of candidates created and a split by team, refreshed on schedule.

Why connect Workable's MCP server through Elaichi

Workable builds and runs this MCP server. Elaichi sits in front of it, so Workable's tools follow the same sign-in, access rules and audit log as every other connector your organization uses. Calls an AI client makes to Workable's server directly, outside Elaichi, get none of this.

  • One address for every AI client

    Claude, ChatGPT, Cursor and Microsoft Copilot reach Workable's tools at the same Elaichi address as every other connected app. Nobody adds Workable's server to each client one by one.

  • Each person signs in as themselves

    Each person signs in to Elaichi as themselves. Members connect with their own Workable sign-in, and a connection someone shares runs on its owner's account. The credential stays in Elaichi's separate credential service, and the AI client holds only its Elaichi sign-in.

  • Rules checked before a call leaves

    Restrictions on a role or a person, for the whole connector or a single tool, are checked before a call reaches Workable's server. By default, a tool Workable does not mark read-only or non-destructive counts as destructive, and over MCP it still runs under the "Use your connected apps" consent.

  • One audit log for every app

    Each call that runs is recorded with the person, the tool, the connection and the AI client that made it, in the same audit log as every other app.

  • Tool issues go to Workable

    Workable builds and runs these tools, and Elaichi staff do not curate them, so a report about how a tool behaves goes to the Workable team.

    help.workable.com/hc/en-us/requests/new

Why run a vendor's MCP server through Elaichi →

For IT and engineering

Elaichi vs Zapier MCP vs Composio for Workable

All three can connect Workable to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.

Elaichi compared with Zapier MCP and Composio for Workable, by what to check
What to check Elaichi Zapier MCP Composio
Where the AI connects One address for the whole organization. https://api.elaichi.ai/mcp A server per member, created at sign-in. An MCP endpoint per team, or an SDK.
Control over Workable tools Allow or restrict single Workable tools, per role or user. App and action restrictions on the account. Role permissions, down to the action.
Record of calls One audit entry per Workable call. A History tab of tool calls. A log of every tool call.
Single sign-on SAML or OIDC, plus SCIM, on Gold. SAML on Enterprise. SAML and OIDC on Enterprise.
Price Free for one person; $15 per user per month on Gold. 2 tasks per successful call. Billed per tool call.

Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.

Longer take: Zapier MCP alternative and when you don't need an MCP gateway.

Workable tools for your AI agents

94 tools are ready to call through Elaichi's MCP endpoint the moment you connect Workable, governed by the same roles, restrictions, and audit log as everything else in Elaichi. Workable builds and runs these tools.

Questions, answered

How do I connect Workable to Claude?

Connect Workable in Elaichi first: Workable opens its own sign-in window, you log in as yourself and approve, and that is the whole step. There is no OAuth application to register and no client ID or secret to generate. Then in Claude go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Claude signs you in through Elaichi and your Workable jobs and candidates are available.

Does Workable work with ChatGPT and Cursor as well as Claude?

Yes. Once Workable is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, Microsoft Copilot, any other MCP client and the Elaichi Agent. You connect Workable once and every client you use picks it up.

What can an AI agent actually do with my Workable data?

With Workable connected, an agent can find open jobs, read a job's stages, recruiters and application form, list the candidates in a pipeline and read their activity, files and offer. It can also add a candidate to a job or the talent pool, update a candidate, move them to another stage or job, and disqualify them or reverse that. Short, concrete asks such as "move Dana to the interview stage on the Account Executive job" work better than long instructions.

Does connecting Workable give the AI access to every job and candidate?

No. Every request runs as the person who signed in, so an agent only sees the Workable jobs and candidates that person can already see, with Workable's own member and recruiter rules still applying. Elaichi can narrow that further, by team or by action, but it can never widen it beyond what Workable already allows.

Can my team share one Workable connection?

Yes. One person connects Workable in Elaichi and shares it with a team, and nobody else ever handles a credential or sign-in detail. Each teammate still signs in to Elaichi as themselves, so the audit log names the actual person who moved or disqualified a candidate.

Can I stop an agent from deleting or changing things in Workable?

Yes. Restrictions in Elaichi apply per action, so you can allow reading Workable jobs and candidates while restricting moves, disqualifications or updates. A restricted action still appears in Elaichi's tool search, flagged as restricted, but Claude, ChatGPT or any other client cannot run it, whatever the prompt says.

What happens to a Workable connection when someone leaves?

Offboarding a person in Elaichi ends their access to Workable through every client at once. If they shared a Workable connection with the team, it keeps working for everyone else. Disconnecting Workable once in Elaichi removes it from Claude, ChatGPT, Cursor, Microsoft Copilot and every other client at the same time.

Does the Workable MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. Workable is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.

Is Elaichi an alternative to Zapier MCP for Workable?

Yes. Both let Claude, ChatGPT or Cursor use Workable. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Workable call.

How is Elaichi different from Composio for Workable?

Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Workable: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.

Put Workable in front of your team

14 days of Black, no credit card. Connect it once and pick what each team can call.

When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.

Add one link to your AI app

The same link for everyone on your team.

https://api.elaichi.ai/mcp
  • ChatGPT
  • Claude
  • Cursor
  • Microsoft Copilot