Clera MCP docs

Setup, access, every tool and prompt, and what to do when something breaks.

Overview

Clera MCP is a remote Model Context Protocol server that puts your Clera company account inside Claude, ChatGPT, Cursor, Claude Code and any other MCP client. It covers the whole hiring loop: searching 225,000+ vetted candidates, reviewing the ones Clera picked for you, requesting intros, managing roles and reading the pipeline. Everything you do here shows up in your dashboard, and the other way around. Looking for a job instead? Candidates get their own set of tools.

Server URL
https://mcp.getclera.com
Transport
Streamable HTTP, stateless
Authentication
OAuth 2.1 with dynamic client registration. You sign in with your Clera account.
Pricing
Free during the beta.

Not set up yet? The Clera MCP page has the short version.

Setup

Add the server URL wherever your client keeps remote MCP servers. The first tool call opens a browser window, you sign in with your Clera account and approve the consent screen, and you are connected. A good first ask is whoami.

Claude (web and desktop)

One click above pre-fills the connector. Or by hand: Settings > Connectors > Add custom connector, paste https://mcp.getclera.com. Either way, sign in with your Clera company account and approve the consent screen.

ChatGPT

Settings → Plugins → Advanced settings → turn on Developer mode. Then the plus button at the top of Plugins, paste https://mcp.getclera.com, and sign in with your Clera company account.

Claude Code

$claude mcp add --transport http clera https://mcp.getclera.com

Codex

$codex mcp add clera --url https://mcp.getclera.com
Then run codex mcp login clera, sign in with your Clera company account and approve the consent screen.

Cursor

.cursor/mcp.json
{
  "mcpServers": {
    "clera": {
      "url": "https://mcp.getclera.com"
    }
  }
}
Settings > MCP > Add new global MCP server

Grok

New Connector → Custom, paste https://mcp.getclera.com, then sign in with your Clera company account and approve the consent screen.

Claude Desktop

claude_desktop_config.json
{
  "mcpServers": {
    "clera": {
      "command": "npx",
      "args": ["mcp-remote", "https://mcp.getclera.com"]
    }
  }
}
Settings > Developer > Edit Config. Desktop reaches a remote server through the mcp-remote bridge, so this one runs a command instead of taking the URL directly.

Any MCP client

Add a remote MCP server with URL: https://mcp.getclera.com

Accounts and access

Sign-in is your Clera account, the same one you use for the dashboard. The server never sees your password: your client registers itself with Clera's identity provider, you approve it once, and the token is refreshed automatically. Remove the connector in your client to revoke it.

What you can do follows what your account is on Clera. whoami tells you which of these you are:

  • company member: You are on a company's team. Every company tool applies, scoped to that company.
  • admin: A Clera team member. Every tool, any company.
  • candidate: A Clera candidate login. Their own matches, interviews, job search, preferences and resumes.
  • none: A Clera login that belongs to neither. Ask an owner on your team to invite you.

Inside a company, roles are owner, editor and viewer. Viewers can read everything but cannot request intros, pass on candidates or edit roles. Candidate search is switched on per company. The tool list your client shows is filtered to what you can do, and clients cache that list, so remove and re-add the connector after your role changes.

Tools marked writes change something on Clera. Claude and ChatGPT ask you before running them. Read tools run right away.

Tools for companies

Refer to candidates and roles by name. The ids the tools pass around never need to reach you, and tools marked writes change something on Clera.

Account

The one tool every signed-in user gets, company or not.

  • whoami

    Your email, the companies you belong to with your role in each, and your account kind: admin, company member, candidate, or none.

Find candidates

Search the network. Profiles stay anonymized until Clera has introduced someone to your company.

  • searchCandidates

    Filter candidates who are open to opportunities and recently active. Newest first, or by relevance when a search term is set. No lookup by name, email or LinkedIn URL.

  • similarCandidates

    Start from one candidate you have been shown and get the profiles closest to theirs. Run it on a result to walk further from the original.

  • suggestFilterValues

    Resolve a company or school name to the exact indexed value the employer and education filters need.

  • listFilterOptions

    Valid values with candidate counts for role names, skills, job types, work preferences, countries and languages.

Review and decide

The Review tab of your dashboard, as tools.

  • listRecommendedCandidates

    Candidates Clera picked for your roles that are waiting on your review, each with a fit summary.

  • listPendingIntroRequests

    Candidates who asked to meet your company and are waiting on a decision.

  • readShortlist

    Open one shortlist Clera sent you from its link and see who on it is still waiting on your review.

  • getCandidateProfile

    Full profile of any candidate a tool showed you: experience, education, skills. Anonymized until you request an intro. No contact details, salary, visa status or summaries.

  • requestIntrowrites

    Ask Clera to introduce a candidate for one of your open roles. Name the role, or pick it in an interactive form. Owners and editors only.

  • passCandidatewrites

    Decline a candidate for a role with a reason, from your review list or anywhere in your pipeline. The reason feeds back into how Clera matches for you.

  • undoPasswrites

    Put a passed candidate back into your review list.

  • listPassed

    Everyone you have passed on, with the role and the date.

  • addGoodFitExamplewrites

    Mark a candidate you liked as a reference profile for a role so future picks look more like them.

Pipeline

Where every candidate stands.

  • listPipeline

    Your hiring board by stage: review, intro requested, introduced, interviewing, offer, hired. Interviewing candidates show their stage and next interview date.

  • setInterviewwrites

    Schedule or move an interview, open the next round, mark one done, or move a candidate to offer. Same picker as the Pipeline page.

Roles

Everything about the positions you are hiring for.

  • readJob

    List your roles or read one in full: description, requirements, locations and screening questions.

  • editJobwrites

    Create a role from a title, a job posting URL or pasted text. Then set its brief, requirements, interview stages, locations, questions and notes.

Company and team

The profile candidates see and the people behind it.

  • readCompanyProfile

    The company profile candidates see.

  • editCompanyProfilewrites

    Update the company profile.

  • readCompanyContacts

    Your company contacts, hiring managers included.

  • editCompanyContactwrites

    Create, update or deactivate a contact, or make one primary. The calendar link decides where interviews get booked.

  • listTeamMembers

    Who on your team has a Clera login, with their role, plus pending email invitations.

Dashboard and feedback

Getting out of the chat, and getting word to us.

  • getDashboardLink

    The exact dashboard URL for one section: review, pipeline, a role, settings. The only source of Clera links your assistant should hand you.

  • sendFeedbackwrites

    Send a note to the Clera team: a bug, a confusing tool, something Clera cannot do yet.

Tools for candidates

Looking for a job? Connect the same server and sign in with the account you use on Clera. You get your own matches, interviews, applications and resumes, and nothing from any company account. Ask for what you want in plain words, like “find me backend roles in Berlin and show me the best two”.

Find roles

Roles at startups Clera works with first, then the wider job board.

  • searchCleraRoles

    Open roles at the startups Clera works with. Every result is a role Clera can introduce you to.

  • searchJobs

    The wide external job board, for when the Clera roles come up short.

  • readJobListing

    One job in full, from any search, match or saved list.

  • saveJobwrites

    Bookmark a job board listing for later.

  • listSavedJobs

    Your saved job board listings, newest first.

  • unsaveJobwrites

    Remove a listing from your saved list.

Matches

Your Matches page, as tools.

  • listMatches

    The roles Clera matched you to, in the order your Matches page shows them.

  • readMatch

    One match in full: the role, tech stack, interview stages, the company and its questions for you.

  • likeMatchwrites

    Tell Clera you want a role, the same as the like button on a Matches card. If it fits, Clera puts you in front of the company, and that cannot be taken back.

  • declineMatchwrites

    Pass on a role. It leaves your Matches and Clera stops working on it.

  • undoMatchDecisionwrites

    Reset a like or a pass so the role is back in your Matches as new. A role already in process with the company stays there.

  • answerRoleQuestionwrites

    Answer a company's screening question. Answers stay drafts until you submit them, and submitted ones go to the company with your intro.

Interviews

Where every role stands, and the invitations waiting on you.

  • listMyPipeline

    Every opportunity Clera has for you, in every state, with interview dates where one is booked.

  • listInterviewRequests

    Interview invitations waiting for a yes or no, plus the ones you already answered.

  • acceptInterviewwrites

    Say yes to an interview. Clera tells the company and handles the scheduling.

  • declineInterviewwrites

    Say no to an interview, with the reason you want passed on.

Apply anywhere

Applications outside Clera, and a tracker for all of them.

  • applyToJobwrites

    Fill in an employer's own application form from your Clera profile and primary resume. It stops before the submit button unless you tell it to send.

  • getApplicationRun

    How an application run went: submitted, ready to submit, or what it still needs from you.

  • listApplications

    Your application tracker, newest first, with each one's stage.

  • trackApplicationwrites

    Add a job to your tracker from a job board listing, a posting link or typed details.

  • updateApplicationwrites

    Move a tracked application to another stage, or edit its notes and details.

  • deleteApplicationwrites

    Remove a job from your tracker. Nothing is withdrawn with the company.

  • generateApplicationDocumentswrites

    Write a cover letter or resume tailored to one tracked application and attach the PDFs.

Resumes and writing

The resume Clera sends with your intros, and everything written from it.

  • listResumes

    Your uploaded resumes, which one is primary, and the AI feedback on it: a score out of 100 and fixes.

  • setPrimaryResumewrites

    Pick the resume Clera sends with every intro from now on.

  • deleteResumewrites

    Delete a resume for good. The primary one stays.

  • refreshResumeFeedbackwrites

    Get fresh AI feedback on your primary resume. Takes about a minute.

  • readResumeDraft

    Your resume-builder draft: profile, experience, education, skills and design settings.

  • editResumeDraftwrites

    Rewrite one section of your resume draft.

  • seedResumeDraftwrites

    Fill your resume draft from what Clera already has: LinkedIn, uploaded resumes and GitHub.

  • generateResumePdfwrites

    Turn your resume draft into a PDF, and optionally make it your primary resume.

  • generateCoverLetterwrites

    A cover letter for one job, in your voice, using only facts from your resume draft.

  • draftOutreachwrites

    A LinkedIn note and a short email from you to a hiring manager.

Profile and dashboard

What Clera matches you on, and getting back to your dashboard.

  • readPreferences

    Your job preferences: salary, remote or in person, relocation, roles, company stage, visa needs.

  • editPreferenceswrites

    Change your job preferences. Preferred cities, contact details and resumes are edited on the dashboard.

  • getProfileStrength

    Your profile strength from 0 to 100, and the next steps ranked by how many points each adds.

  • getReferralStats

    Your referral link, who you invited, and who signed up.

  • getTalentDashboardLink

    The exact link to one section of your Clera dashboard.

Prompts

The server ships three guided workflows. Your client lists them under the Clera connector; pick one, fill in the optional argument, and your assistant follows the playbook step by step.

  • find_candidates

    Find candidates

    Guided search-and-intro workflow for your open roles, from filter discovery to the shortlist.

    requirements: role, must-have skills, location, seniority, budget. Optional.

  • configure_role

    Configure a role for matching

    Audit a role's spec, ask for what is missing, and fill it in so Clera's matching has something to key on.

    role: a title or name, or leave blank to pick from your open roles. Optional.

  • write_job_description

    Write a job description

    Create a new role with a natural-sounding description and complete metadata, in two or three rounds of questions.

    position, jobUrl or jobText: a title to start from, a posting to import, or text to parse. All optional.

Example prompts

Things people type on day one. Say it the way you would to a colleague.

  • Search

    “Find senior backend engineers in Berlin with Go and Postgres who would take 90 to 110k.”

  • Similar profiles

    “More people like the second candidate, but based in the Netherlands.”

  • Review

    “Who is waiting on a decision from us? Compare each one against the role and tell me who to meet.”

  • Pipeline

    “How many candidates are interviewing right now, and who has a next interview this week?”

  • Roles

    “Set up our Head of Product role so matching works. Ask me whatever you need.”

  • Team

    “Who on my team has access? Add Maria as the hiring manager for the frontend role.”

  • Feedback

    “Tell Clera the pipeline tool showed the wrong stage for the candidate we hired last week.”

Privacy and data

Clera sees only the arguments of the tools your assistant calls: search filters, a role, a reason for a pass, a note you asked it to send. Never the rest of your conversation. Each tool call is logged with your account and company so we can run and improve the service.

Candidate profiles come back anonymized until Clera has introduced the person to your company. Names, avatars and LinkedIn URLs are hidden; the fit is not. Full profiles never include contact details, salary or visa status.

The rest is in the privacy policy.

Troubleshooting

Sign-in fails, loops, or times out

  • Sign in with the email that is on your company's team on Clera. A personal login that is not a team member connects, but sees no company tools.
  • Clear cookies for getclera.com and connect again. Browser extensions that block redirects break the consent step.
  • Check that your client supports OAuth for remote MCP servers. Claude, ChatGPT, Claude Code, Cursor and mcp-remote all do.

Only whoami shows up

  • Ask whoami. If the account kind is candidate or none, your login is not on any company team. Ask an owner on your team to invite you from Settings, then reconnect.
  • Clients cache the tool list. After your access changes, remove the Clera connector and add it again.

A tool is refused

  • Viewers cannot request intros, pass on candidates, or edit roles. Ask an owner or editor on your team.
  • Candidate search is enabled per company. If searchCandidates says it is off for you, write to us and we will switch it on.
  • Searching for a person by name returns nothing on purpose. Profiles are anonymized, so search by role, skills and location instead.

A tool returns an error

  • Try once more. If it fails again, send us the tool name and roughly when it happened, or ask your assistant to use sendFeedback.

Revoking access

  • Remove the Clera connector in your client's settings. The token stops working immediately. Nothing about your company changes.

Support

Write to [email protected] with the tool that failed and roughly when. Or stay in the chat: sendFeedback lands on the same desk, and a person reads every note.