MCP: your team’s assistant, on your own records.

Connect the assistant your agency approved. It signs in as the consultant, reads the records they can open, and leaves the work waiting for a check.

Book a demoSee what it costs
Illustration
an assistant, connected to Talisman
An assistant chat window. Somebody asks for qualified accountants in Leeds who are open to a permanent move on up to 55k. A Talisman tool call runs, and three candidate records come back with reference codes, qualifications, towns, availability dates and match scores, above a button reading Add all three to the shortlist.

An illustration of the kind of request. The assistant asks Talisman, and that consultant’s own candidate records come back.

The week this is about

Your team already works this way

Somebody on your desk is using ChatGPT today.

They paste in the CV. They paste in the job spec. The answer lands in a chat window and stops there.

Connect that assistant and every action a consultant takes becomes one it can call. Talisman publishes those actions as MCP tools, the open protocol assistants speak.

So the same CV goes in, and a candidate record comes back with the job linked and the compliance check already running.

IllustrationAn assistant chat window. Somebody attaches a CV and asks for the candidate to be added to Talisman for a Quantity Surveyor role in Bristol with a four week notice period. A Talisman tool call runs, and the new candidate record comes back with a reference code, the role sought, location, notice, mobile number, source, who added it, salary sought and qualification, plus chips reading CV on file, Linked to job and Compliance check started.
An illustration of the kind of request. A CV goes in; the record comes back with the job linked and the compliance check started.
On a perm, contract or temp desk

Ask in your own words, against your own records

What somebody asksWhat comes back
Three drivers free on Thursday, cleared for that siteA shortlist with availability and the checks on each worker, waiting for the consultant’s yes
What has happened on this client since MarchA summary with the dates, the jobs and the people named in it
Draft the message to every worker whose DBS expires next monthA draft per worker, in the wording you approved, each one waiting for a send
Which of my perm roles is sitting at offer, and for how longThe candidate, the client and the day it reached offer, in one list
Which of my jobs still has a shift open for tomorrowThe open shifts, the client and the hours, in one list
How it actually works

One question, from the chat window to the record

Your consultant

Their assistant

Talisman

  1. Your consultantAsks for the shortlistIn the assistant they already use
  2. Their assistantCalls Talisman as that consultantStraight to the live recordsChatGPT or Claude
  3. TalismanThe sign-in behind itChecked on every call
  4. TalismanAnswers with what they may openThat desk’s candidates, jobs and bookings
  5. TalismanAnything that changes a recordComes back as a draft
  6. Your consultantSays yes, and it landsOn the record, in their name
Talisman answers as the consultant who asked, and the draft waits for their yes.
How far one ask goes

One ask, 100 candidates

That diagram is one shortlist. Here is the ceiling.

A consultant asks for an email to all 100 candidates on a job. In their voice. Asking each one whether the role interests them, and asking for an updated CV.

A hundred drafts come back, one per candidate, each written from what Talisman already holds on that person — the last conversation, the ticket that expires in April, the town they live in. The consultant reads them, says yes, and the hundred go out in their name.

Every reply lands on the candidate’s record. Every fresh CV lands with it.

IllustrationAn assistant chat window. Somebody asks for an email to all 100 candidates on a job, written in their voice, asking whether they are interested and asking for an updated CV. A Talisman tool call runs and reports 100 drafted, and two example drafts come back, each personalised from the candidate's own record — one citing a conversation in March, the other a forklift ticket valid to April 2027 — above a line reading 100 drafts waiting for you to check.
An illustration of the kind of request. One ask, 100 drafts, each one written from that candidate’s own record.
Connecting it

How you connect it

One sign-in, in the assistant your agency already uses.

You add Talisman as a connector and authorise it once, in your browser. From then on it runs as you, with your permissions.

Connecting is one sign-in. Agreeing what it may draft takes longer.

  • ChatGPT, Microsoft Copilot and Claude, where your agency has approved them.
  • Any client that speaks MCP, including the agent frameworks your team tries.
  • The same Talisman records behind whichever assistant you settle on.

What the connection carries

  • The person who authorised it, by name
  • That person’s permissions, on every call
  • The records that person may open
  • A run history a manager can read back

MCP access is included in the Talisman Platform, across the modules you have switched on.

How Talisman handles permissions, audit, consent and GDPR

Questions we get asked

MCP FAQ

What can the assistant see?

Exactly what the person who authorised the connection sees. Every call carries that user’s permissions. A consultant’s assistant reaches that consultant’s candidates, jobs, bookings and documents.

Where do the records live?

In Talisman. The assistant works the live candidate, contact, client, job and booking records your team already keeps. So the answer comes back with the job number, the worker and the date on it.

Can we write our own agents against it?

Yes. The tools your team’s assistant calls are open to code you write, in Python, TypeScript or any language with an MCP library. Your agent authorises as a real user and leaves the same run history.

How do we know what it did?

The run history. Every request, the records it read and how far it got are written under the name of the person behind the connection. Anything that would change a record waits there as a draft for them to approve.

Compliance
Business Development
Sourcing
Daily Briefings
Timesheets

Point an assistant at your own records

The session runs on your own desks, with an assistant signed in as a named user.

Book a demo