Integration

Dropboard integration

Dropboard is a hiring platform and applicant tracking system with a white-labeled job board for companies and recruiting agencies. List, read, create, update and delete jobs, list, read, create and update candidates, move them through hiring workflow stages (which can email the candidate), read and add candidate notes and attributes, list and create clients and client members (Recruiter plan, may incur charges), and list team members, job types, job categories, field collections, client plans and workflows. Candidate records hold personal data (names, emails, cover letters, resume links). Left out: webhook subscriptions and the deprecated candidate custom-fields listing. Authentication is an organization API token sent in the X-API-TOKEN header, generated by an admin under Settings > API tokens.

Connect Dropboard How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Dropboard.Built from the 29 Dropboard tools below, on the connection you add once.

What you can do with Dropboard

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Job, 5 operations

create_jobCreate jobPOSTCreates a job (open by default) and returns it with its id and public application link. The hiring manager defaults to the token's user; set hiringManagerMemberId from list_team_members or list_client_members.
delete_jobDelete jobDELETEPermanently deletes a job and its statistics. Its candidates are detached and kept unless deleteCandidates is true, which deletes them too. Closing the job with update_job (status closed) is the reversible alternative.
get_jobGet jobGETReturns one job by its id or job code: title, plain-text and rich-text description, status, open dates, locations, hiring manager, notification settings, workflow, type, categories and public application link.
list_jobsList jobsGETLists jobs, 100 per page at most, filtered by text search, client, status (open or closed) or hiring manager. Each job has its title, plain-text description, status, public application link, locations, type and categories.
update_jobUpdate jobPATCHUpdates only the job fields you pass and leaves the others unchanged, then returns the updated job. Set status to closed to stop applications; categories can be added, removed or replaced.

Candidate, 4 operations

create_candidateCreate candidatePOSTCreates a candidate for a job (jobId or jobCode), optionally with a resume fetched from a public URL and attributes, and returns it. Non-PDF resumes are converted to PDF, which can take several seconds.
get_candidateGet candidateGETReturns one candidate: name, email, cover letter, resume link, the job and client applied to, and the current workflow and stage.
list_candidatesList candidatesGETLists candidates (applications), 100 per page at most, filtered by text search, client, job id or code, workflow, workflow stage, or attribute values. Each record carries the person's name, email, cover letter, resume link and stage.
update_candidateUpdate candidatePATCHUpdates a candidate's name, email, cover letter, external id or resume, or moves the candidate to another job; fields left out keep their value. Returns the updated candidate. Use move_candidate_stage to change the stage.

Client, 3 operations

create_clientCreate clientPOSTCreates a client company (Recruiter plan) on a client plan (the first plan when none is given) and returns it. Creating clients may incur charges on your Dropboard subscription.
get_clientGet clientGETReturns one client (Recruiter plan): its id, name, creation date and assigned client plan.
list_clientsList clientsGETLists clients (Recruiter plan sub-organizations), 100 per page at most, optionally filtered by text search. Each client has its id, name, creation date and plan.

Attribute, 2 operations

get_candidate_attributesGet candidate attributesGETLists a candidate's attributes (text values or file attachments with a download link), including those shared from other records of the same person.
set_candidate_attributesSet candidate attributesPOSTSets attributes on a candidate: each one given replaces the attribute of that name, others are left as they are. Attributes are shared across records of the same person.

Field collection, 2 operations

get_field_collectionGet field collectionGETReturns one field collection (a set of custom application questions for jobs): its id, name, creation date and client.
list_field_collectionsList field collectionsGETLists field collections (sets of custom application questions that can be attached to jobs), optionally for one client.

Member, 2 operations

create_client_memberCreate client memberPOSTAdds a person to a client (Recruiter plan) and returns the member. With sendInvite true, Dropboard emails them an invitation link to the portal. Adding members may incur charges on your subscription.
list_client_membersList client membersGETLists members of clients (people with access to a client portal), optionally for one client or matching a search. Each member has a name and email.

Note, 2 operations

add_candidate_notesAdd candidate notesPOSTAdds note blocks to a candidate (append, the default) or replaces the whole note (replace), for example assessment results. Notes are shared across records of the same person.
get_candidate_notesGet candidate notesGETReturns the notes stored for a candidate as ordered blocks (paragraphs, headings, bulleted, numbered and checked lists, images). Notes are shared across records of the same person (same email).

Workflow, 2 operations

get_workflowGet workflowGETReturns one hiring workflow with its ordered stage names, client and whether it is the default workflow.
list_workflowsList workflowsGETLists hiring workflows (series of stages candidates move through, Business plans and up), optionally for one client or matching a search, with their stage names.

Candidate attribute, 1 operation

list_attribute_namesList attribute namesGETLists the attribute names in use on candidates, optionally for one client. Use them as attributeName filters in list_candidates.

Job category, 1 operation

list_job_categoriesList job categoriesGETLists the job categories set up for the organization (for example Engineering, Sales), for create_job and update_job.

Job type, 1 operation

list_job_typesList job typesGETLists the employment types set up for the organization (for example Full-time, Part-time, Contract), for create_job and update_job.

Me, 1 operation

get_meGet meGETReturns the user the API token belongs to and which account features are enabled (Recruiter plan, open dates). A cheap way to check that the connection works.

Move stage, 1 operation

move_candidate_stageMove candidate stagePOSTMoves a candidate to a workflow stage (Business plans and up). If the stage has an email template, Dropboard emails the candidate unless sendTemplatedEmailOption is skip-send; sendCustomEmail sends your own email instead.

Plan, 1 operation

list_client_plansList client plansGETLists the client plans (Recruiter plan) with their job limits and approval rules; all plans are returned at once.

Team member, 1 operation

list_team_membersList team membersGETLists the team members of the top-level organization with their id, name and email; use an id as a job's hiringManagerMemberId.

Use Dropboard from Claude Code, Cursor or Codex

Connect Dropboard in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Dropboard operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Dropboard

Create your workspace
Sign up free. Nothing to install.
Connect Dropboard once
Add your Dropboard connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.