Skip to content

ATS

Pinpoint MCP connector

The Pinpoint connector brings candidates, applications, interviews, departments and hiring team users into Claude, ChatGPT, Cursor and any MCP client, so recruiters can ask about their pipeline and update records inside their own Pinpoint access.

  • How it connects. Connects with an API key. The credential goes into a vault nobody reads back.

  • One address. https://api.elaichi.ai/mcp, the same for every user.

  • Their own access. An agent never gets more than the person it acts for.

How to connect

How to connect Pinpoint to Claude, ChatGPT or Cursor

Two steps, about a minute.

1

In Elaichi

Connect Pinpoint once

  1. Open Connections, choose Add connection, and pick Pinpoint.

  2. Optionally set Share with to give a team access, then press Connect.

  3. Paste a Pinpoint API key. One person generates a token in Pinpoint and pastes it once. Everyone else works through Share with, and never sees it.

The credential is vaulted. Nobody reads it back, not even the AI.

Add connection

Choose a connector.

pinpoint
Pinpoint
Ashby
Greenhouse
Manatal
Polymer
Recruitee
2

In your AI client

Point it at one endpoint

Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.

Connect Pinpoint to Claude

  1. 1

    Open Customize, then Connectors.

  2. 2

    Press Add.

  3. 3

    Name it, paste the MCP server URL, then Continue.

    https://api.elaichi.ai/mcp
  4. 4

    Sign in and approve.

On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.

Connect Pinpoint to ChatGPT

  1. 1

    Open Plugins, then press the + button.

  2. 2

    Name it and paste the endpoint into Server URL.

    https://api.elaichi.ai/mcp
  3. 3

    Leave Authentication on OAuth, then tick the risk acknowledgement.

  4. 4

    Press Create, then sign in and approve.

Works on the web today. The plugin directory lives at chatgpt.com/plugins.

Connect Pinpoint to Cursor

  1. 1

    Open ~/.cursor/mcp.json.

  2. 2

    Add the endpoint under mcpServers.

    https://api.elaichi.ai/mcp
  3. 3

    Reload Cursor, then sign in and approve.

~/.cursor/mcp.json

{
  "mcpServers": {
    "elaichi": {
      "url": "https://api.elaichi.ai/mcp"
    }
  }
}

Set up per machine, so repeat it on each computer you work from.

Connect Pinpoint to any MCP client

  1. 1

    Add the endpoint as a remote MCP server.

    https://api.elaichi.ai/mcp
  2. 2

    Sign in and approve.

{
  "mcpServers": {
    "elaichi": {
      "url": "https://api.elaichi.ai/mcp"
    }
  }
}

The Elaichi Agent already has these tools, with nothing to set up.

Use cases

What teams do with Pinpoint through Elaichi

Every one of these runs inside the access the person already has, and lands in the same audit log.

  • Recruiting

    Catch a candidate record up after a screen

    Ask for the candidate by name, then update their details and add or edit the answers to screening questions while the call is still fresh.

  • Recruiting

    See every application for an open role

    Pull the list of applications for a job in Pinpoint and ask which ones are new, which have stalled, and which are ready for the hiring manager.

  • Hiring managers

    Check the week's interview schedule

    List upcoming interviews across your open roles and ask who is interviewing whom, without opening Pinpoint or chasing the recruiter.

  • People

    Move a candidate into a new application

    When a strong candidate fits a different role, create the new application in Pinpoint and remove the old one so the pipeline stays honest.

  • People operations

    Keep departments tidy as the org changes

    Create, rename or remove departments in Pinpoint when teams reorganize, so every open role sits under the right part of the business.

  • HR admin

    Onboard a new recruiter with the right access

    Add a new user to Pinpoint, check which access group they belong to, and remove users who have moved on, all from a plain request.

Try asking

  • “Show applications created in Pinpoint this week”
  • “Which Pinpoint access groups include hiring managers?”
  • “Summarize answers on the senior engineer application”

See all 89 Pinpoint tools below

AI tools

Pinpoint tools for your AI agents

89 tools are ready to call through Elaichi's MCP endpoint the moment you connect Pinpoint, governed by the same roles, restrictions, and audit log as everything else in Elaichi.

See it in Elaichi

What connecting Pinpoint gets you

6 screens from the product, each doing one job for your Pinpoint account.

The agent

Ask about applications, get answers from Pinpoint.

Plain language questions return live Pinpoint applications, users and answers in seconds.

  • applications
  • users
  • access groups
  • answers

Ask Elaichi to work across your apps.

Show applications created in Pinpoint this week

Which Pinpoint access groups include hiring managers?

Summarize answers on the senior engineer application

Also runs in Claude, ChatGPT or Cursor

MCP clients

Claude, ChatGPT and Cursor reach Pinpoint here.

One org MCP endpoint over OAuth, no SDK and no shared API key.

ElaichiMCP clients
Claude ChatGPT Cursor

Copy the endpoint

https://api.elaichi.ai/mcp
Client Connected by Status Last used
Claude
E

Emma Laurent

• Connected 4 minutes ago
Cursor
S

Sofia Ricci

• Connected 2 hours ago
ChatGPT
C

Clara Nowak

• Connected Yesterday

Tool catalog

89 Pinpoint tools are ready to call.

Applications, users, access groups and answers are covered with no custom code.

  • List all Pinpoint users
  • Get single Pinpoint user by ID
  • Delete a Pinpoint user by ID
  • Create a Pinpoint user
ElaichiTools
Tool Action Description
List all Pinpoint users List List users in Pinpoint. Returns id, created_at, email, first_name, last_name, time_zone, and updated_at fields for each user in the response.
Get single Pinpoint user by ID Get Get details for a specific user in Pinpoint. Requires id. Returns fields such as id, created_at, email, first_name, last_name, time_zone, and updated_at in the response.
Delete a Pinpoint user by ID Delete Delete a user in Pinpoint. Requires id. Returns meta information about the deletion in the response.
Create a Pinpoint user Create Create a user in Pinpoint. Requires first_name, last_name, email, and user_type. Returns user id, type, created_at, updated_at, email, first_name, last_name, and time_zone in the response.
List all Pinpoint access groups List List all access groups in Pinpoint. Returns id, type, created_at, description, create_as_referral, name, number_of_roles, updated_at, wizard_enabled, wizard_requirements, and roles relationships in the response.

Toolboxes

Every team gets its own Pinpoint toolbox.

Recruiting, hiring managers and HR ops each see a toolbox scoped to them.

  • Recruiting
  • Hiring managers
  • HR operations
  • Talent sourcing
ElaichiToolboxes
Name Source template Tools Created

Recruiting toolbox

Pinpoint · applications and candidates

Pinpoint starter 18 Mar 4, 2026

Hiring managers toolbox

Pinpoint · applications for their own roles

9 Mar 2, 2026

HR operations toolbox

Pinpoint · users and access groups

24 Feb 27, 2026

Talent sourcing toolbox

Pinpoint · new applications and answers

Pinpoint starter 6 Feb 19, 2026

Interview panel toolbox

Pinpoint · answers and scorecards

31 Jan 30, 2026

People analytics toolbox

Pinpoint · application volume reporting

12 Jan 22, 2026

Shared connections

Share Pinpoint access without sharing a credential.

See who connected each Pinpoint account and which teams and members use it.

  • Engineering hiring
  • Sales hiring EMEA
  • Graduate programme
  • Retail stores
ElaichiConnections
Connection Scope Status Access
PI

Pinpoint (Engineering hiring)

Connected by Emma Laurent

Personal • Active 1 team · 6 members
PI

Pinpoint (Sales hiring EMEA)

Connected by James Whitfield

Organization • Active 3 teams · 24 members
PI

Pinpoint (Graduate programme)

Connected by Sofia Ricci

Organization • Active 2 teams · 11 members
PI

Pinpoint (Retail stores)

Connected by Daniel Ortega

Personal • Needs re-auth 1 team · 3 members
PI

Pinpoint (HR operations)

Connected by Clara Nowak

Personal • Active Not shared
PI

Pinpoint (Executive search)

Connected by Michael Brennan

Personal • Active 2 teams · 9 members

Audit log

Every Pinpoint call is written down.

When, who, what happened, type and resource for each application and user touched.

  • When
  • Who
  • What happened
  • Type
ElaichiAudit log
When Who What happened Type

2 minutes ago

Mar 6, 2026, 3:10 PM

E

Emma Laurent

[email protected]

Restriction Created Access

8 minutes ago

Mar 6, 2026, 3:04 PM

J

James Whitfield

[email protected]

Restriction Updated Access

14 minutes ago

Mar 6, 2026, 2:58 PM

S

Sofia Ricci

[email protected]

Role Assigned Access

20 minutes ago

Mar 6, 2026, 2:52 PM

D

Daniel Ortega

[email protected]

Pinpoint Users Updated MCP

26 minutes ago

Mar 6, 2026, 2:46 PM

C

Clara Nowak

[email protected]

Pinpoint Applications Created MCP

32 minutes ago

Mar 6, 2026, 2:40 PM

M

Michael Brennan

[email protected]

Pinpoint Applications List Toolbox

Launching soon

From answering questions to doing the work

A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.

Automations

A schedule fires and Pinpoint work finishes.

Fetch applications, group them, draft a digest, get approval, post back to Pinpoint.

Pinpoint digest

Run 418 · started 2 minutes ago · on behalf of Emma Laurent

  1. Schedule

    Every weekday at 08:00

    0.2s
  2. Fetch applications

    Pinpoint

    1.4s
  3. Group by owner

    Transform

    0.1s
  4. Draft the digest

    Agent step

    Ran with 4 tools, returned a structured summary

    6.2s
  5. Approve the digest

    Needs approval

    Assigned to Michael Brennan

    Approve
  6. Post the digest

    Pinpoint

    Queued

Collections and dashboards

Pinpoint hiring numbers arrive without being asked.

Applications created over 14 days, four metrics and a team breakdown, refreshed on schedule.

Pinpoint health

Refreshed 4 minutes ago · every 15 minutes · from the applications collection

Live

Applications

1,284 ↓ 12%

Users

96 ↓ 8%

Needs attention

3 ↑ 2

Updated this week

412 ↑ 9%

Applications created

Last 14 days

By team

Share of activity

Engineering hiring 34%

Sales hiring EMEA 27%

Graduate programme 21%

Retail stores 18%

FAQ

Frequently asked questions

How do I connect Pinpoint to Claude?

Two steps. First, connect Pinpoint in Elaichi by pasting a Pinpoint API key from your Pinpoint account; there is no OAuth application to register and no client ID or secret to generate. Then in Claude go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Sign in with your Elaichi account and Pinpoint is available in the conversation.

Does Pinpoint work with ChatGPT and Cursor as well as Claude?

Yes. Once Pinpoint is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client, and the Elaichi Agent. You connect Pinpoint once and every client you use picks it up.

What can an AI agent actually do with my Pinpoint data?

With Pinpoint connected, an agent can look up candidates and update their details, list and create applications for open roles, record or edit screening answers, show upcoming interviews, and manage departments, users and access groups. Because Pinpoint offers a large set of actions, short concrete asks such as "list interviews this week" work better than long paragraphs. Ask in plain language and the agent finds the right action in Pinpoint.

Does connecting Pinpoint give the AI access to every candidate and role?

No. Every request to Pinpoint runs inside the access of the person who signed in, so an agent sees only the candidates, applications and departments that person can already see in Pinpoint. Elaichi can narrow that further with restrictions, and it can never widen it beyond what Pinpoint itself allows.

Can my team share one Pinpoint connection?

Yes. One person connects Pinpoint in Elaichi and shares the connection with a team, and nobody else ever handles the Pinpoint API key. Each teammate still signs in to Elaichi as themselves, so the audit log names the person behind every change to a candidate or application in Pinpoint.

Can I stop an agent from deleting or changing things in Pinpoint?

Yes. Restrictions in Elaichi work per action, so you can allow reading candidates and interviews in Pinpoint while blocking deletes of applications, departments or users. A blocked action is never shown to Claude, ChatGPT or any other client, so no prompt, however worded, can reach it.

What happens to a Pinpoint connection when someone leaves?

Offboarding a person in Elaichi ends their access to Pinpoint through every client at once, and their past actions stay in the audit log. A shared Pinpoint connection keeps working for everyone else on the team. If you ever want to remove Pinpoint entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor and every other client.

Put Pinpoint in front of your team

Fourteen days on Gold, no credit card. Connect it once and pick what each team can call.