Skip to content

Connectors · Work & projects

Breezy HR MCP server for AI agents.

actionlake is an MCP gateway: one remote MCP server that connects Claude and other MCP clients to Breezy HR and the rest of your systems. It gives your agent 57 Breezy HR actions (33 reads, 22 writes and 2 that wait for a confirmation) and holds the Breezy HR credential itself, so the agent never does. It paces Breezy HR's limits and records every call.

100,000 free calls a month. No card, no email, no password: press Start a free sandbox on the next screen and keep the key it shows you.

claude mcp add --transport http actionlake https://connect.actionlake.com/mcp
the first call
do {  action: "breezy_hr.companies.list",  intent: "check which Breezy HR account is connected"}# Returns the companies the authenticated user belongs to, as an array of company summary objects (`_id`, `name`, `friendl · read · 1 upstream call
  • 57actionsin one signed file
  • 33readlook, never change
  • 22writecreate and update
  • 2wait for a yesdestructive, confirmed first

Set up

Connect Breezy HR in three steps.

  1. 01

    Add actionlake to Claude.

    Run the command once in Claude Code; its consent page can create a free sandbox: 100,000 calls a month, no card. In the Claude app, add a custom connector with the URL below and paste your key on the consent page. Creating a new sandbox from the Claude app is not yet tested by us.

    https://connect.actionlake.com/mcp
  2. 02

    Connect Breezy HR.

    Bearer token. No consent screen: your agent can connect it for you, but the key then passes through your chat. To keep it out of the model's context, paste it in the console instead. actionlake stores what you paste write-only, sealed under your tenant's key.

    • tokenBreezy Personal Access Token (breezy_pat_...), created in Breezy under your account settings
    account { op: "connections.requirements", service: "breezy_hr" }
    # free: exactly what to paste, and what is found for you
  3. 03

    Make the first call. Check before a write.

    Ask in plain words; Claude picks the action. Before anything changes, check validates the call and prices it, for free.

    do    { action: "breezy_hr.companies.list" }# returns the companies the authenticated user belongs to, as an array of company summary objects (`_id`, `name`, `friendl · read · 1 upstream callcheck { action: "breezy_hr.candidates.create", input: { … } }# free: inputs, permissions, cost and confirmations, nothing sent

Breezy HR at a glance

Sign-in
Bearer token. No consent screen: your agent can connect it for you, but the key then passes through your chat. To keep it out of the model's context, paste it in the console instead.
You provide
token
Limits we pace to
60 calls a minute, per connection
API covered
Breezy HR Public API v3 (OpenAPI 3.1 published per page on developer.breezy.hr)api.breezy.hr
Built from
Breezy HR's documentation, read 23 October 2026developer.breezy.hr
Service file
Version 1.0.0, signed (Ed25519)
Cached reads
31 of 33 reads, for up to 5 minutes; a write clears what it affects
Shared entities
3, so ask can line Breezy HR up with your other systems
Data
Processed and stored in Sydney, Australia. No US region yet

Capabilities

What an AI agent can do in Breezy HR.

57 actions in 32 areas. Every one carries its effect, so a key can allow the reads and hold the rest.

  • 33readlook, never change
  • 22writecreate and update
  • 2destructivewait for a confirmation
  1. Candidates

    7

    4 read · 3 write · 0 destructive

    Returns the candidates on a given position within a company, as an array of candidate summaries (id, name, contact info, · Creates a candidate on the specified position and returns the created candidate record · Retrieves a single candidate by ID, scoped to the given company and position, and returns the full candidate profile (co · Updates editable profile fields on an existing candidate within a position, and returns the full updated candidate objec

  2. Webhook endpoints

    7

    2 read · 4 write · 1 destructive

    Creates a new webhook endpoint for the company and subscribes it to the specified event types, so matching events are de · Lists the webhook endpoints configured for the company, along with quota usage · Retrieves a single webhook endpoint's configuration and delivery stats by its ID · Pauses a webhook endpoint, stopping event deliveries to it, and returns the updated webhook endpoint object

  3. Positions

    4

    2 read · 2 write · 0 destructive

    Returns the positions belonging to the specified company · Creates a new position (job requisition) for the company and returns the newly created position object · Retrieves a single position by ID, returning its full details (name, type, state, location, department, description, app · Updates an existing position and returns the full updated position object

  4. Candidate assessments

    3

    1 read · 1 write · 1 destructive

    Returns the candidate's assessment results from integrated pre-employment testing providers (currently HackerRank, Crite · Deletes an assessment by Breezy `_id` · Upserts an assessment keyed on `(provider_type, external_id)` for the candidate-position

  5. Candidate questionnaires

    3

    1 read · 2 write · 0 destructive

    Returns the questionnaires sent to this candidate for the given position, including each questionnaire's sections and qu · Sends an existing questionnaire template to the candidate, attaching it to the candidate's record on the given position · Submits a candidate's answers to a questionnaire that was sent to them, validates them against the questionnaire's quest

  6. Candidate custom fields

    2

    1 read · 1 write · 0 destructive

    Returns the custom field values recorded for a candidate on the specified position, as an array of custom field objects · Updates the value of one custom field on a candidate, identified by the company-level custom field ID, and returns the c

  7. Companies

    2

    2 read · 0 write · 0 destructive

    Returns the companies the authenticated user belongs to, as an array of company summary objects (`_id`, `name`, `friendl · Retrieves the company identified by `companyId` and returns its public profile: `_id`, `name`, `friendly_id`, `member_co

  8. Pipelines

    2

    2 read · 0 write · 0 destructive

    Returns the company's configured hiring pipelines as a JSON object keyed by pipeline name (e.g · Returns the ordered list of stages that make up the specified pipeline, as an array of stage objects (e.g

24 more areas · 27 actions
  • Position custom fields 2
  • Questionnaires 2
  • Templates 2
  • Candidate background checks 1
  • Candidate conversation 1
  • Candidate custom attributes 1
  • Candidate documents 1
  • Candidate education 1
  • Candidate messages 1
  • Candidate meta 1
  • Candidate notes 1
  • Candidate scorecards 1
  • Candidate stage 1
  • Candidate stream 1
  • Candidate work history 1
  • Categories 1
  • Company custom attributes 1
  • Company custom fields 1
  • Departments 1
  • Position state 1
  • Position stream 1
  • Position team 1
  • User 1
  • User details 1

Top actions

The Breezy HR API, shaped for agents.

The ids your agent types, what each does, and the one name it shares with other systems. 11 of Breezy HR's 13 action names are shared with at least one other connector, so an agent learns them once.

ActionWhat it doesEffectSame name in
breezy_hr.departments.listReturns the list of department definitions configured for the company, each with an `id` and `name`Returns the list of department definitions configured for the company, each with an `id` and `name`.readhr.department.list40 connectors
breezy_hr.candidates.listReturns the candidates on a given position within a company, as an array of candidate summaries (id, name, contact info,Returns the candidates on a given position within a company, as an array of candidate summaries (id, name, contact info,.readhr.candidate.list22 connectors
breezy_hr.candidates.createCreates a candidate on the specified position and returns the created candidate recordCreates a candidate on the specified position and returns the created candidate record.writehr.candidate.create20 connectors
breezy_hr.user.getReturns the profile of the currently authenticated userReturns the profile of the currently authenticated user.readidentity.current_user.get307 connectors
breezy_hr.candidates.updateUpdates editable profile fields on an existing candidate within a position, and returns the full updated candidate objecUpdates editable profile fields on an existing candidate within a position, and returns the full updated candidate objec.writehr.candidate.update18 connectors
breezy_hr.positions.listReturns the positions belonging to the specified companyReturns the positions belonging to the specified company.readhr.job_opening.list24 connectors
breezy_hr.positions.createCreates a new position (job requisition) for the company and returns the newly created position objectCreates a new position (job requisition) for the company and returns the newly created position object.writehr.job_opening.create15 connectors
breezy_hr.companies.listReturns the companies the authenticated user belongs to, as an array of company summary objects (`_id`, `name`, `friendlReturns the companies the authenticated user belongs to, as an array of company summary objects (`_id`, `name`, `friendl.readthis connector
breezy_hr.pipelines.listReturns the company's configured hiring pipelines as a JSON object keyed by pipeline name (e.gReturns the company's configured hiring pipelines as a JSON object keyed by pipeline name (e.g.readthis connector
breezy_hr.templates.listReturns the list of message templates configured for the company, each item including its `_id`, `name`, and `body`Returns the list of message templates configured for the company, each item including its `_id`, `name`, and `body`.readthis connector
breezy_hr.categories.listReturns the list of position category definitions available to the company, each with an `id` and `name`Returns the list of position category definitions available to the company, each with an `id` and `name`.readthis connector
breezy_hr.webhook_endpoints.deletePermanently deletes the specified webhook endpoint so it stops receiving any further event deliveriesPermanently deletes the specified webhook endpoint so it stops receiving any further event deliveries.destructivethis connector

Try it

Prompts to paste into Claude.

Each one names the Breezy HR actions it will call, so you know what it reads and what it changes before you send it.

  1. Readread

    Who has access in Breezy HR? List every user and their role.

    callsbreezy_hr.user.get

  2. Writewrite

    Creates a candidate on the specified position and returns the created candidate record in Breezy HR. Show me exactly what you will send before you save it.

    callsbreezy_hr.candidates.create

Governance for Breezy HR

Destructive actions wait for a yes.

2 Breezy HR actions are destructive. These are all of them:

  • Permanently deletes the specified webhook endpoint so it stops receiving any further event deliveriesbreezy_hr.webhook_endpoints.delete
  • Deletes an assessment by Breezy `_id`breezy_hr.candidate_assessments.delete

A destructive action runs only with confirm: true. Under the human policy the agent cannot confirm for itself: the run stops until a named person approves, in the console or from a signed link in an email. The cap on a key is refused before the call is sent, never after.

dobreezy_hr.webhook_endpoints.deleteconfirm_policy: human

Permanently deletes the specified webhook endpoint so it stops receiving any further event deliveries?

intent: the user asked me to permanently deletes the specified webhook endpoint so it stops receiving any further event deliveries

run suspended · waiting for a named person · key breezy-hr-agent cannot confirm itself
In the console, or from an emailed signed link.
a key for this connector
account {  op: "keys.create", name: "breezy-hr-agent",  allowed_actions: ["breezy_hr.*"], cap_calls: 2000,  confirm_policy: "human_for_writes",  approval_rules: [    { match: "breezy_hr.webhook_endpoints.delete", approver: "[email protected]" },    { match: "breezy_hr.candidate_assessments.delete", approver: "[email protected]" }  ]}
Illustrative. Scoped to Breezy HR only, capped at 2,000 upstream calls, every write confirmed, and the destructive ones approved by a named person.

Cost

What Breezy HR costs on actionlake.

Every Breezy HR action is one upstream call, the only thing actionlake bills. Searching, check, cost, account and any call Breezy HR refused with 401, 403, 429 or a 5xx are free. Paid plans start at US$49 a month for 250,000 calls, with overage from US$0.30 down to US$0.18 per 1,000.

  • 1upstream call per actionall 57 Breezy HR actions
  • 57actions pageeach page of a long list is one call
  • 31reads can be cacheda cache hit costs nothing
  • 100,000calls a month, freepaid plans from US$49 a month for 250,000

See pricing

Action index

Every Breezy HR action.

57 actions by area: the id your agent calls, what it does, and its effect.

Candidates7
  • breezy_hr.candidates.createCreates a candidate on the specified position and returns the created candidate recordwrite
  • breezy_hr.candidates.getRetrieves a single candidate by ID, scoped to the given company and position, and returns the full candidate profile (coread
  • breezy_hr.candidates.listReturns the candidates on a given position within a company, as an array of candidate summaries (id, name, contact info,read
  • breezy_hr.candidates.moveMoves a candidate to a target position and pipeline stage, and returns the updated candidatewrite
  • breezy_hr.candidates.queryFree-text search across every candidate in the company, served by the same search index that powers in-app candidate searead
  • breezy_hr.candidates.searchFinds candidates in the company whose email address matches `email_address`, searching company-wide across all positionsread
  • breezy_hr.candidates.updateUpdates editable profile fields on an existing candidate within a position, and returns the full updated candidate objecwrite
Webhook endpoints7
  • breezy_hr.webhook_endpoints.createCreates a new webhook endpoint for the company and subscribes it to the specified event types, so matching events are dewrite
  • breezy_hr.webhook_endpoints.deletePermanently deletes the specified webhook endpoint so it stops receiving any further event deliveriesdestructive
  • breezy_hr.webhook_endpoints.getRetrieves a single webhook endpoint's configuration and delivery stats by its IDread
  • breezy_hr.webhook_endpoints.listLists the webhook endpoints configured for the company, along with quota usageread
  • breezy_hr.webhook_endpoints.pausePauses a webhook endpoint, stopping event deliveries to it, and returns the updated webhook endpoint objectwrite
  • breezy_hr.webhook_endpoints.resumeResumes a paused (or auto-disabled) webhook endpoint, setting it back to active and re-enabling event deliverywrite
  • breezy_hr.webhook_endpoints.updateUpdates an existing webhook endpoint and returns the updated resourcewrite
Positions4
  • breezy_hr.positions.createCreates a new position (job requisition) for the company and returns the newly created position objectwrite
  • breezy_hr.positions.getRetrieves a single position by ID, returning its full details (name, type, state, location, department, description, appread
  • breezy_hr.positions.listReturns the positions belonging to the specified companyread
  • breezy_hr.positions.updateUpdates an existing position and returns the full updated position objectwrite
Candidate assessments3
  • breezy_hr.candidate_assessments.deleteDeletes an assessment by Breezy `_id`destructive
  • breezy_hr.candidate_assessments.listReturns the candidate's assessment results from integrated pre-employment testing providers (currently HackerRank, Criteread
  • breezy_hr.candidate_assessments.upsertUpserts an assessment keyed on `(provider_type, external_id)` for the candidate-positionwrite
Candidate questionnaires3
  • breezy_hr.candidate_questionnaires.listReturns the questionnaires sent to this candidate for the given position, including each questionnaire's sections and quread
  • breezy_hr.candidate_questionnaires.sendSends an existing questionnaire template to the candidate, attaching it to the candidate's record on the given position write
  • breezy_hr.candidate_questionnaires.submitSubmits a candidate's answers to a questionnaire that was sent to them, validates them against the questionnaire's questwrite
Candidate custom fields2
  • breezy_hr.candidate_custom_fields.listReturns the custom field values recorded for a candidate on the specified position, as an array of custom field objectsread
  • breezy_hr.candidate_custom_fields.updateUpdates the value of one custom field on a candidate, identified by the company-level custom field ID, and returns the cwrite
Companies2
  • breezy_hr.companies.getRetrieves the company identified by `companyId` and returns its public profile: `_id`, `name`, `friendly_id`, `member_coread
  • breezy_hr.companies.listReturns the companies the authenticated user belongs to, as an array of company summary objects (`_id`, `name`, `friendlread
Pipelines2
  • breezy_hr.pipelines.getReturns the ordered list of stages that make up the specified pipeline, as an array of stage objects (e.gread
  • breezy_hr.pipelines.listReturns the company's configured hiring pipelines as a JSON object keyed by pipeline name (e.gread
Position custom fields2
  • breezy_hr.position_custom_fields.listReturns the custom fields configured on the specified position as an array of field objects (`_id`, `name`, `type`, `datread
  • breezy_hr.position_custom_fields.updateSets the value of a single custom field on a position, identified by its custom field IDwrite
Questionnaires2
  • breezy_hr.questionnaires.getRetrieves a single questionnaire belonging to the company by its ID, including its sections and questions (each with itsread
  • breezy_hr.questionnaires.listReturns the list of questionnaires configured for the companyread
Templates2
  • breezy_hr.templates.getRetrieves a single saved message template for the company by its `templateId`, returning the template's `_id`, `name`, aread
  • breezy_hr.templates.listReturns the list of message templates configured for the company, each item including its `_id`, `name`, and `body`read
Candidate background checks1
  • breezy_hr.candidate_background_checks.listReturns the list of background check results requested for the candidate on this positionread
Candidate conversation1
  • breezy_hr.candidate_conversation.listReturns the candidate's message and activity thread — messages sent to or from the candidate (including messages posted read
Candidate custom attributes1
  • breezy_hr.candidate_custom_attributes.updateSets a custom attribute on a candidate and returns the updated candidate objectwrite
Candidate documents1
  • breezy_hr.candidate_documents.listReturns the files stored for the candidate on this position — resumes and other documents uploaded by the candidate or aread
Candidate education1
  • breezy_hr.candidate_education.createAdds a new education entry to the candidate's profile and returns the updated Candidate objectwrite
Candidate messages1
  • breezy_hr.candidate_messages.createSends a message to the candidate within their conversation for this position, delivering it directly to the candidate (ewrite
Candidate meta1
  • breezy_hr.candidate_meta.getReturns a single aggregated bundle of activity and content for a candidate on a given position: tasks, notes (notepad anread
Candidate notes1
  • breezy_hr.candidate_notes.createAdds an internal note to the candidate's activity stream and returns the created stream activity, including the note bodwrite
Candidate scorecards1
  • breezy_hr.candidate_scorecards.createRecords a scorecard rating for the candidate on the specified position, attributed to the authenticated API userwrite
Candidate stage1
  • breezy_hr.candidate_stage.updateMoves the candidate to a different stage in the position's pipeline, identified by `stage_id`write
Candidate stream1
  • breezy_hr.candidate_stream.listReturns the candidate's activity stream on the position — a chronological array of `StreamActivity` events (e.gread
Candidate work history1
  • breezy_hr.candidate_work_history.createAppends a new entry to the candidate's work history and returns the full updated [Candidate](#schema/candidate) objectwrite
Categories1
  • breezy_hr.categories.listReturns the list of position category definitions available to the company, each with an `id` and `name`read
Company custom attributes1
  • breezy_hr.company_custom_attributes.listReturns the custom attribute definitions configured for the company, filtered by entity `type` (`candidate` or `positionread
Company custom fields1
  • breezy_hr.company_custom_fields.listReturns the company's custom field definitions for the given `type` (`candidate` or `position`) — the field metadata (naread
Departments1
  • breezy_hr.departments.listReturns the list of department definitions configured for the company, each with an `id` and `name`read
Position state1
  • breezy_hr.position_state.updateUpdates the state (lifecycle status) of a position, moving it between `published`, `draft`, `archived`, and `closed`write
Position stream1
  • breezy_hr.position_stream.listReturns the position's activity stream: a list of state-change events recorded against the position (e.gread
Position team1
  • breezy_hr.position_team.listReturns the list of team members assigned to the specified position, including each member's user profile and the role(sread
User1
  • breezy_hr.user.getReturns the profile of the currently authenticated userread
User details1
  • breezy_hr.user_details.getReturns a snapshot of every company the authenticated user belongs to, keyed by each company's `friendly_id`read

Questions

The Breezy HR MCP server, answered.

Is there a Breezy HR MCP server for Claude?

Yes. actionlake is an MCP gateway: a remote MCP server that gives Claude, or another MCP client, 57 Breezy HR actions across candidates, webhook endpoints, positions and candidate assessments, through the same eight tools it uses for every other connector. actionlake is independent; it is not made or endorsed by Breezy HR.

What do I need to connect Breezy HR?

Breezy Personal Access Token (breezy_pat_...), created in Breezy under your account settings. The free call account { op: "connections.requirements", service: "breezy_hr" } lists exactly what to paste.

Can an AI agent delete or change things in Breezy HR?

Only if its key allows it, and only with an explicit confirmation. 2 Breezy HR actions are destructive, including permanently deletes the specified webhook endpoint so it stops receiving any further event deliveries and deletes an assessment by Breezy `_id`. Each runs only with confirm: true. Under the human confirm policy, or an approval rule on the key, the run waits until a named person approves it.

Will an AI agent use up my Breezy HR API limit?

actionlake paces every call to the limits in the Breezy HR service file: 60 calls a minute per connection. Repeated reads are answered from cache (31 Breezy HR actions can be), which never reaches Breezy HR.

What does a Breezy HR action cost?

One upstream call, the only unit actionlake bills. A list that pages bills one call per page (57 Breezy HR actions page). Cache hits, searches, dry runs and calls Breezy HR refused with 401, 403, 429 or a 5xx are free. The Free plan includes 100,000 calls a month with no card. Paid plans start at US$49 a month for 250,000 calls, with overage from US$0.30 down to US$0.18 per 1,000.

Which Breezy HR API does it cover?

The Breezy HR Public API v3 (OpenAPI 3.1 published per page on developer.breezy.hr) at api.breezy.hr. It is built from Breezy HR's documentation as read on 23 October 2026. 57 actions in 32 areas, each one in the signed service file (version 1.0.0).

Does actionlake keep my Breezy HR data, and where?

actionlake processes and stores data in Sydney, Australia; there is no US region yet. Reads may be cached for up to 5 minutes, and a write clears the reads it affects. Each run's request and response is kept, sealed, for your plan's trace window: 1 day on Free, 3 days on Starter, 7 days on Pro, 14 days on Team, 30 days on Business and 30 days on Enterprise. Your Breezy HR credential is sealed under your tenant's key, never logged and never returned. Your traffic is not used to train models.

Which AI clients can use it?

Claude Code, tested by us end to end, and the Claude app as a custom connector, tested by us with an existing key. Other MCP clients that support remote servers over Streamable HTTP (MCP revisions 2025-06-18 and 2025-11-25) and OAuth dynamic client registration, or a bearer header, should connect the same way; we have not tested them. Or plain REST, under the same action names.

Give your agent Breezy HR today.

Start free - 100,000 calls/month, no card. No signup. Hard caps on every key. Cached answers are free.