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 200,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.

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 and the waitlist.

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 > Apps > Advanced settings > turn on Developer mode. Then Plugins > plus button, 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 --oauth-client-registration dcr, 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.

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.

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. Only whoami for now.
  • 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

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.

  • getCandidateProfile

    Full profile of anyone already visible to you: experience, education, skills, summaries. No contact details, salary or visa status.

  • 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. 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.

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.

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.