Your first application typically arrives within 3 hrs.

Solutions

For staffing agencies
Logistics & transport Warehousing & fulfillment Manufacturing Construction Skilled trades

Integrations

API platform
MCP server API reference
Pricing

Resources

Blog
Security & compliance Erika vs job portals Erika vs marketing agencies
Find a job
Book a demo Log in

Erika MCP server

Connect your AI assistant to Erika.

The Erika MCP server lets Claude Code or any other MCP client create hiring campaigns, prepare the ads and work with your jobs and candidates. A person reviews and launches every campaign in the Erika studio.

https://app.erikawork.com/api/v1/mcp

Connect

Set it up in three steps.

You need an Erika API key and an MCP client that can send a custom header.

  • Create an API key in Erika under Settings, API Keys. For campaigns, give it the Auto Campaign API permission at Manage level. Add Jobs and Candidates if the assistant should work with your ATS.
  • Add the server to your client and send the key in the X-Api-Key header. Bearer tokens are not supported.
  • Tell the assistant which role you are hiring for. It follows the recommended flow and gives you a studio link when the campaign is ready to launch.

Image generation takes 30 to 60 seconds inside one tool call. If your client times out, raise its tool timeout.

Add it to Claude Code
claude mcp add erika --transport http \
  https://app.erikawork.com/api/v1/mcp \
  --header "X-Api-Key: ek_live_YOUR_KEY"

# image generation can take up to a minute
MCP_TOOL_TIMEOUT=180000 claude
Other clients (mcp.json)
{
  "mcpServers": {
    "erika": {
      "url": "https://app.erikawork.com/api/v1/mcp",
      "headers": { "X-Api-Key": "ek_live_YOUR_KEY" }
    }
  }
}
Tools

What your assistant can do.

The tool list follows the permissions on your key. An assistant only sees the tools its key allows. View covers reading, Manage adds changes.

Campaigns and ads

Needs the Auto Campaign API permission.

ToolAccessWhat it does
createCampaignManageCreate a draft campaign; returns the campaign id and its studio link.
listCampaignsViewList your sourcing campaigns with status and linked job.
getCampaignViewFull campaign state: settings, creative plan and every creative's progress.
updateCampaignSettingsManageSet budget (credits), duration, location, language, screening questions, ad copy, linked job or title.
recommendBudgetViewBudget recommendation in credits from real cost-per-candidate benchmarks.
createCreativeManageCreate a creative; the ad script is generated server-side from the campaign and job.
updateCreativeScriptManageOverwrite a creative's script with exact user copy.
regenerateCreativeScriptManageAI rewrite of a creative's script, optionally steered by instructions.
updateCreativeAdCopyManageSet a creative's ad headline and primary text.
approveCreativeManageApprove a creative for launch, or set it aside.
generateReferenceImageManageGenerate or edit the video's first frame (30-60 s, charges image credits).
generateVideoManageStart async AI video generation (charges credits up front, refunded on failure).
getCreativeStatusViewOne creative's detail and video status with downloadable URLs; the polling endpoint.
checkLaunchReadinessViewRun every launch check and get the remaining issues plus the studio link.
getCreditBalanceViewYour organization's current credit balance.
startAutonomousCampaignBuildManageOne-shot: job description plus budget in, launched campaign out. Spends the budget.
getAutonomousCampaignBuildViewPoll an autonomous campaign build.

Jobs and pipelines

Needs the Jobs permission.

ToolAccessWhat it does
listJobsViewList your jobs with status and search filters.
getJobViewOne job's full details including pipeline stages.
listPipelineTemplatesViewList reusable pipeline stage presets; createJob copies stages from one.
createJobManageCreate a job with pipeline stages copied from a template (default template if omitted).
updateJobManageUpdate a job's title, description, reference code or job details.
changeJobStatusManageOpen, pause, close, archive or re-draft a job.

Candidates and applications

Needs the Candidates permission. There are no delete or bulk import tools.

ToolAccessWhat it does
listCandidatesViewList your candidates; filter by search, source, tag or sourcing campaign.
getCandidateViewOne candidate's full profile including their applications.
listApplicationsViewOne job's pipeline: applications with candidate, stage and latest activity.
getApplicationViewOne application's full detail including the activity timeline.
createCandidateManageAdd a candidate with contact details, source and tags.
updateCandidateManageUpdate a candidate's contact details or tags.
addCandidateNoteManageAdd a note to a candidate's profile.
createApplicationManagePlace a candidate on a job's pipeline.
moveApplicationStageManageMove an application to another pipeline stage.
changeApplicationStatusManageReject, withdraw or hire an application, with an optional reason and note.
addApplicationNoteManageAdd a note to an application's activity timeline.
Recommended flow

From a job to a campaign ready to launch.

The server explains this flow to the assistant when it connects. Each step returns what the next one needs.

createCampaign
→ updateCampaignSettings   (budget, duration, location, language,
                            screening questions)
→ recommendBudget
→ getCampaign              (read the slot plan)
→ createCreative           (one per slot)
→ generateReferenceImage
→ generateVideo            (async, about 3–6 min)
→ getCreativeStatus        (poll until ready)
→ approveCreative
→ checkLaunchReadiness
→ a person opens studioUrl and launches
Built in safeguards

A person stays in control.

You launch, not the assistant

Tools prepare drafts and return a studio link. Only startAutonomousCampaignBuild launches on its own: it uses the Campaign Build API and spends the budget, so the assistant should ask you first.

Spending has a limit

Images and videos use credits. Video credits are charged up front and refunded if a video fails. Erika won't make a video that the budget can't launch.

Limited to your company

Every call stays inside the key's organization. Changes appear in the activity timeline under the person who created the key.

Same checks as the studio

Before launch, Erika runs the same checks as in the web studio: budget, location, screening questions, approved ads and ad copy.

Errors in plain language

When Erika refuses a step, for example for lack of credits, it says why. The assistant can pass that on to you.

Standard protocol

Streamable HTTP without sessions, tools only. Supports protocol versions 2025-06-18, 2025-03-26 and 2024-11-05.

Developer questions

Which AI clients work with it?
Any MCP client that supports Streamable HTTP and can send a custom X-Api-Key header, such as Claude Code. Clients that only connect through an OAuth sign-in can't connect yet.
Does the MCP server launch campaigns?
Not by default. The tools prepare the campaign draft and the ads, then return a studio link where a person launches the campaign. Only one tool can launch on its own: startAutonomousCampaignBuild. It uses the Campaign Build API, which creates and launches the whole campaign in one step and spends the budget. The assistant should ask you before using it.
Do I need to install anything?
No. Erika hosts the server. You add the endpoint and your API key to your client.
Can my assistant work with candidates?
Yes, if the key has the Candidates permission. It can look up candidates and applications, add notes and move people between pipeline stages. There are no delete tools.
What does it cost?
The MCP server is part of API access on the paid plans. Campaign tools need the Growth plan or higher. Image and video generation spend credits from your plan. See pricing.

Connect your assistant to Erika today.

Create an API key, add the server and ask for your first campaign.