Ashby MCP server

What the model can do

Recruiting in Ashby: jobs by status with department, location and hiring team, published job postings, applications by job or status with the candidate and current stage, one application or candidate in full, candidates by email or name, upcoming interviews, users, departments, tags, sources and archive reasons; can also add or edit a candidate, note or tag them, put them forward for a job, move an application between stages or archive it, open, close or archive a job, publish or unpublish a posting, and cancel an interview schedule when you ask. Never reads compensation.

Reads

• ashby_jobsJobs in Ashby (open by default): title, status (Open, Closed, Archived, Draft), employment type, department, location, hiring team with roles…
• ashby_job_postingsJob postings in Ashby (publicly listed ones by default): title, the job they advertise, department, team, location, employment type, published date…
• ashby_applicationsApplications in Ashby: by job, by status (Active, Hired, Archived, Lead), or created since a date; newest first.
• ashby_applicationOne Ashby application in full: candidate, job, status, current stage, source, hiring team, archive reason, dates — plus its interview schedules…
• ashby_candidatesFind Ashby candidates by email or name (at least one), or fetch one by candidate id: name, emails, current position and company, location, tags…
• ashby_interviewsInterview schedules in Ashby, upcoming by default: each with its interviews (title, start and end, location or meeting link, interviewers…
• ashby_usersUsers of the Ashby account (name, email, global role, enabled) or the departments (name, parent, archived).
• ashby_lookupsThe ids Ashby's actions take: candidate tags (for ashby_tag_candidate), sources (for ashby_create_candidate…

Acts, when you ask

These change something in Ashby. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.

• ashby_create_candidateAdds a new candidate to Ashby, visible to everyone in the account who can see candidates.
• ashby_update_candidateChanges a candidate's details in Ashby: name, primary email, an added alternate email, LinkedIn, GitHub or website link, source…
• ashby_add_candidate_noteLeaves a note on a candidate in Ashby, seen by everyone who can see the candidate (or, with private true, only by those allowed private fields).
• ashby_tag_candidateAdds a tag to a candidate in Ashby, or with remove true takes it off.
• ashby_create_applicationPuts a candidate forward for a job in Ashby, creating an application in the job's default interview plan at its first Lead stage unless a stage is…
• ashby_update_applicationChanges an Ashby application's source or the user it is credited to (null unsets either).
• ashby_change_application_stageMoves an Ashby application to another interview stage of its plan, which the hiring team see and which runs that stage's automations.
• ashby_set_job_statusSets an Ashby job's status to Open, Closed, Archived or Draft, which changes whether it takes applications.
• ashby_set_job_posting_statusPublishes an Ashby job posting on the public careers page, where anybody can read it and apply, or with Draft takes it down.
• ashby_cancel_interview_scheduleCancels an interview schedule in Ashby, which takes its interviews off the calendar for the interviewers and the candidate…

Connect it

First connect Ashby on Dashboard → Connections, then add Memtro to your client once. The Ashby tools appear alongside the tools of everything else you have connected; nothing is configured per connector.

claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...

{
  "mcpServers": {
    "memtro": {
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

{
  "mcp": {
    "memtro": {
      "type": "remote",
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Who may use it

The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared Ashby connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.

Ask it like this

• › Which applications for Staff Engineer are in the Technical Interview stage?
• › Who is interviewing this week, and has feedback been submitted?
• › Has Amara Osei applied before, and where did it end?
• › Which jobs are open in the Data department, and who is on each hiring team?
• › Move Amara Osei's Staff Engineer application to the onsite stage

Questions

Is this an official Ashby MCP server?

No. It is Memtro's MCP server with Memtro's Ashby connector behind it: the connector reads Ashby through its API with the credentials you connect on Dashboard → Connections, and Ashby publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.

What does it cost?

Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.

Can it change anything in Ashby?

Only when you ask, and only what it has been granted: add a candidate; edit a candidate's name, email, links, source, credited user or location; leave a note on a candidate; add a tag to a candidate, or take one off; put a candidate forward for a job, as a new application; change an application's source or credited user; move an application to another interview stage, or archive it with a reason, optionally emailing the candidate a rejection; open, close, archive or return a job to draft; publish a job posting on the careers page, or take it down; cancel an interview schedule. Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.

Which clients work?

Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.

Other MCP servers · People and HR

• BambooHR MCP server
• Personio MCP server
• Microsoft Entra ID MCP server
• Google Workspace MCP server
• HiBob MCP server
• Greenhouse MCP server