JobAdder MCP Integration

Connect JobAdder to AI

Prepare for meetings, log activities and add candidates to jobs from Claude, with every action recorded against the consultant who made it.

Already running for a specialist recruitment agency's consultants. We host the connection and build the workflows around how your desks work.

Discuss Your Workflows

What We Build

Built Around How Your Consultants Work

We build workflows like these with your team, because they don't come with the MCP connection alone.

  1. Meeting Preparation

    A briefing before each client or candidate meeting, drawn from the JobAdder record: the contact, their history, open jobs and recent activity.

  2. Meeting Notes Into JobAdder

    After the meeting, notes, actions and follow-ups are drafted and logged on the right contact, once the consultant has checked them.

  3. Activity That Reports Correctly

    Client meetings are logged as activities on your own JobAdder templates, not loose notes, so your team's KPI reporting stays accurate.

  4. Candidates Added to Jobs

    Add a candidate to a job from the conversation, with the consultant approving the change before anything is written to JobAdder.

  5. Summaries From the Record

    Candidate summaries, shortlists and client updates drafted from the JobAdder record and your templates, for the consultant to finish.

How It Fits Together

Connection, Skills and Workflows

We build around what your team knows: which activity to log, what a good briefing looks like and how client updates should read.

The MCP Connects

Your AI tool reaches JobAdder through its API, with each consultant signed in as themselves. We host the connection and maintain it.

The Skills Guide

Your activity templates, logging rules and house style are written into skills, so every consultant logs the same way.

The Workflows Coordinate

One conversation runs from meeting preparation to the logged activity, and the consultant approves each change.

The Connection

What the MCP Supports

What's available depends on your JobAdder setup, region and permissions, and the actions we agree to switch on.

Explore AI for Recruitment
Candidates and Jobs: search and read the record

Search and read candidates, jobs, applications and placements, so a briefing or summary starts from what JobAdder already holds.

Companies and Contacts: client history in one place

Read companies and contacts with their recent activity and notes, so a consultant walks into each client meeting prepared.

Activities and Notes: logged to your own templates

Log activities and notes against the right record, using your JobAdder activity templates and the rules your team agrees.

Job Applications: add a candidate to a job

Add a candidate to a job from the conversation. Your JobAdder permissions apply, and the consultant approves the change first.

Per-consultant Sign-In: actions attributed to the person

Each consultant connects with their own JobAdder login, so every action is recorded against the person who made it, not a shared account.

Hosted and Controlled: approval before any write

We host the connection. Write actions ask the consultant to approve them, and we agree with you which actions are switched on.

Claude, ChatGPT and Copilot

JobAdder in the AI Your Team Already Uses

We set up the hosted connection and confirm the requirements with your team.

Claude

Built and running in Claude at a specialist recruitment agency, where consultants prepare meetings and log activities.

ChatGPT

ChatGPT supports MCP connections in business workspaces. We confirm the setup and actions your team needs in scoping.

Microsoft 365 Copilot

Copilot Studio agents can use MCP connections. We confirm the licences and the setup with your IT team during scoping.

How It Works

An Implementation Your Team Can Use

Each implementation is scoped up front and tested on real meetings and records before anyone relies on the output.

  1. Agree Your Workflows

    We agree with your team which meetings, records and tasks are in scope.

    • Workflows and desks agreed
    • Your activity templates mapped
    • Acceptance checks set
  2. Connect and Configure

    We set up JobAdder access for each consultant, configure your rules and build the agreed skills.

    • JobAdder sign-in set up
    • Logging rules and templates
    • A skill for each task
  3. Test With Your Team

    We test on real meetings and records with the consultants who will use it.

    • Outputs checked in JobAdder
    • Template issues resolved
    • Handover to your team
  4. Support and Improve

    We agree support and service levels, then scope improvements as your needs change.

    • Connection support
    • Template and workflow changes
    • New requirements scoped

Who It's For

Built for Recruitment on JobAdder

For agencies that run their desks in JobAdder.

  1. Specialist Recruitment

    Consultants who run their week in JobAdder and want the admin around each client and candidate meeting done once, properly.

  2. Executive Search

    Research-heavy briefs, long candidate lists and detailed client updates, drafted from the record for a consultant to review.

  3. Growing Agencies

    More consultants logging the same way, so handovers hold up and nobody has to chase missing notes after a meeting.

  4. Agency Leaders

    Activity logged consistently on your own templates, so the KPI reporting you run the business on can be trusted.

Implementation Options

Scoped to Your Team and Desks

We agree the consultants, workflows, integrations and support with you, then confirm the scope, fee and JobAdder permissions.

Discuss Your Requirements
One Desk or Team: your first connected workflows

We connect JobAdder for a team, build meeting preparation and logging around your templates, then test and hand over.

Whole Agency: every consultant on the same rules

We set up sign-in for every consultant, agree logging rules across desks and support your team through the first months.

JobAdder and More: other systems in the same workflow

We scope extra connections with you, such as email, calendars or document stores, and build workflows across them.

Practical Questions

Connecting JobAdder, Workflows and Support

JobAdder is a trademark of its owner, and ELab AI is an independent provider not affiliated with, endorsed by or certified by JobAdder.

What is a JobAdder MCP?

MCP (Model Context Protocol) is an open standard that lets AI tools use data and tools from other systems. A JobAdder MCP gives an AI tool such as Claude access to JobAdder records and actions, within the permissions you set.

Is this an official JobAdder product?

No. It's ELab AI's independently built and hosted integration, which reads and writes through the JobAdder API. It already runs in production for a specialist recruitment agency.

Does each consultant sign in separately?

Yes. Each consultant connects with their own JobAdder login, so every action is recorded against the person who made it rather than a shared account.

Can the AI change JobAdder without anyone checking?

Write actions, such as logging an activity or adding a candidate to a job, ask the consultant to approve them first. We agree with you which actions are switched on.

Does it work with our own activity templates?

Yes. We configure the logging rules around your templates. For one agency we work with, client meetings are always logged as activities, not notes, so their KPI reporting stays accurate.

Which AI tools does it work with?

It is built and running in Claude. ChatGPT and Microsoft 365 Copilot also support MCP connections, and we confirm the setup for your workspace during scoping.

How is candidate and client information handled?

The connection uses the JobAdder API with each consultant's authorised access. We agree storage, access, retention and AI provider settings with you before connecting any data, in line with your privacy obligations.

What does it cost?

Each implementation has a fixed fee for the agreed scope, rather than a published subscription. The fee depends on your team size, workflows and support. We confirm hosting and other ongoing costs before you commit.

A Good Place to Start

Build Around Your Consultants

Tell us how your desks run and the meeting admin or reporting you'd like to fix. A short description is enough, and there's no need to send candidate records.

Discuss Your Workflows hello@elab.co.nz