Skip to content

Connectors · Work & projects

Pinpoint MCP server for AI agents.

actionlake is an MCP gateway: one remote MCP server that connects Claude and other MCP clients to Pinpoint and the rest of your systems. It gives your agent 113 Pinpoint actions (63 reads, 35 writes and 15 that wait for a confirmation) and holds the Pinpoint credential itself, so the agent never does. It paces Pinpoint's limits and records every call.

100,000 free calls a month. No card, no email, no password: press Start a free sandbox on the next screen and keep the key it shows you.

claude mcp add --transport http actionlake https://connect.actionlake.com/mcp
the first call
do {  action: "pinpoint.users.list",  intent: "check which Pinpoint account is connected"}# List users · read · 1 upstream call
  • 113actionsin one signed file
  • 63readlook, never change
  • 35writecreate and update
  • 15wait for a yesdestructive, confirmed first

Set up

Connect Pinpoint in three steps.

  1. 01

    Add actionlake to Claude.

    Run the command once in Claude Code; its consent page can create a free sandbox: 100,000 calls a month, no card. In the Claude app, add a custom connector with the URL below and paste your key on the consent page. Creating a new sandbox from the Claude app is not yet tested by us.

    https://connect.actionlake.com/mcp
  2. 02

    Connect Pinpoint.

    API key. No consent screen: your agent can connect it for you, but the key then passes through your chat. To keep it out of the model's context, paste it in the console instead. actionlake stores what you paste write-only, sealed under your tenant's key.

    • api_keyPinpoint API key: in Pinpoint open Settings > API & Webhooks, switch the Pinpoint API toggle on, then create a key…
    • hostWhere your Pinpoint lives: your host
    account { op: "connections.requirements", service: "pinpoint" }
    # free: exactly what to paste, and what is found for you
  3. 03

    Make the first call. Check before a write.

    Ask in plain words; Claude picks the action. Before anything changes, check validates the call and prices it, for free.

    do    { action: "pinpoint.users.list" }# list users · read · 1 upstream callcheck { action: "pinpoint.users.create", input: { … } }# free: inputs, permissions, cost and confirmations, nothing sent

Pinpoint at a glance

Sign-in
API key. No consent screen: your agent can connect it for you, but the key then passes through your chat. To keep it out of the model's context, paste it in the console instead.
You provide
api_key
Setup fields
host
Limits we pace to
120 calls a minute and 240 per 8 minutes, per connection
API covered
Pinpoint API v1 (OpenAPI 3.0.1, JSON:API), at your Pinpoint instance's API base URL, which you enter when connecting
Built from
Pinpoint's documentation, read 23 October 2026developers.pinpointhq.comdevelopers.pinpointhq.com
Service file
Version 1.0.0, signed (Ed25519)
Cached reads
63 of 63 reads, for up to 5 minutes; a write clears what it affects
Shared entities
4, so ask can line Pinpoint up with your other systems
Data
Processed and stored in Sydney, Australia. No US region yet

Capabilities

What an AI agent can do in Pinpoint.

113 actions in 34 areas. Every one carries its effect, so a key can allow the reads and hold the rest.

  • 63readlook, never change
  • 35writecreate and update
  • 15destructivewait for a confirmation
  1. Applications

    5

    2 read · 2 write · 1 destructive

    List applications · Create an application · Get an application · Update an application

  2. Custom attributes

    5

    2 read · 2 write · 1 destructive

    Create a custom attribute · List custom attributes · Get a custom attribute · Update a custom attribute

  3. Custom fields

    5

    2 read · 2 write · 1 destructive

    Create a custom field · List custom fields · Get a custom field · Update a custom field

  4. Departments

    5

    2 read · 2 write · 1 destructive

    List departments · Create a department · Get a department · Update a department

  5. Divisions

    5

    2 read · 2 write · 1 destructive

    Create a division · List divisions · Get a division · Update a division

  6. Job seekers

    5

    2 read · 2 write · 1 destructive

    Create a job seeker · List job seekers · Get a job seeker · Update a job seeker

  7. Jobs

    5

    2 read · 2 write · 1 destructive

    List jobs · Create a job · Get a job · Update a job

  8. Locations

    5

    2 read · 2 write · 1 destructive

    List locations · Create a location · Get a location · Update a location

26 more areas · 73 actions
  • Requisitions 5
  • Structure custom group ones 5
  • Structure links 5
  • Users 5
  • Answers 4
  • Background checks 4
  • Candidate assessments 4
  • Comments 4
  • Candidates 3
  • Interviews 3
  • Structured section responses 3
  • Access groups 2
  • Candidate surveys 2
  • Equality monitoring categories 2
  • Hiring workflows 2
  • Job postings 2
  • Onboarding applications 2
  • One way video interviews 2
  • Positions 2
  • Quality of hire surveys 2
  • Reference checks 2
  • Requisition templates 2
  • Scorecards 2
  • Structured sections 2
  • Job templates 1
  • Questions 1

Top actions

The Pinpoint API, shaped for agents.

The ids your agent types, what each does, and the one name it shares with other systems. 31 of Pinpoint's 31 action names are shared with at least one other connector, so an agent learns them once.

ActionWhat it doesEffectSame name in
pinpoint.users.listList usersList users.readidentity.user.list474 connectors
pinpoint.departments.listList departmentsList departments.readhr.department.list40 connectors
pinpoint.locations.listList locationsList locations.readhr.location.list32 connectors
pinpoint.candidates.listList candidatesList candidates.readhr.candidate.list22 connectors
pinpoint.users.createCreate an userCreate an user.writeidentity.user.create262 connectors
pinpoint.departments.createCreate a departmentCreate a department.writehr.department.create32 connectors
pinpoint.locations.createCreate a locationCreate a location.writehr.location.create23 connectors
pinpoint.users.deleteDelete an userDelete an user.destructiveidentity.user.delete253 connectors
pinpoint.candidates.getGet a candidateGet a candidate.readhr.candidate.get19 connectors
pinpoint.jobs.listList jobsList jobs.readhr.job_opening.list24 connectors
pinpoint.jobs.createCreate a jobCreate a job.writehr.job_opening.create15 connectors
pinpoint.applications.listList applicationsList applications.readhr.application.list15 connectors

Try it

Prompts to paste into Claude.

Each one names the Pinpoint actions it will call, so you know what it reads and what it changes before you send it.

  1. Readread

    Who has access in Pinpoint? List every user and their role.

    callspinpoint.users.list

  2. Writewrite

    Create an user in Pinpoint. Show me exactly what you will send before you save it.

    callspinpoint.users.create

Governance for Pinpoint

Destructive actions wait for a yes.

15 Pinpoint actions are destructive. These are all of them:

  • Delete an userpinpoint.users.delete
  • Delete a departmentpinpoint.departments.delete
  • Delete a locationpinpoint.locations.delete
  • Delete an applicationpinpoint.applications.delete
  • Delete a jobpinpoint.jobs.delete
  • Delete an answerpinpoint.answers.delete
  • Delete a commentpinpoint.comments.delete
  • Delete a divisionpinpoint.divisions.delete
  • Delete a job seekerpinpoint.job_seekers.delete
  • Delete a requisitionpinpoint.requisitions.delete
  • Delete a custom fieldpinpoint.custom_fields.delete
  • Delete a structure linkpinpoint.structure_links.delete
  • Delete a custom attributepinpoint.custom_attributes.delete
  • Delete a structure custom group onepinpoint.structure_custom_group_ones.delete
  • Delete a structured section responsepinpoint.structured_section_responses.delete

A destructive action runs only with confirm: true. Under the human policy the agent cannot confirm for itself: the run stops until a named person approves, in the console or from a signed link in an email. The cap on a key is refused before the call is sent, never after.

dopinpoint.users.deleteconfirm_policy: human

Delete an user?

intent: the user asked me to delete an user

run suspended · waiting for a named person · key pinpoint-agent cannot confirm itself
In the console, or from an emailed signed link.
a key for this connector
account {  op: "keys.create", name: "pinpoint-agent",  allowed_actions: ["pinpoint.*"], cap_calls: 2000,  confirm_policy: "human_for_writes",  approval_rules: [    { match: "pinpoint.users.delete", approver: "[email protected]" },    { match: "pinpoint.departments.delete", approver: "[email protected]" },    { match: "pinpoint.locations.delete", approver: "[email protected]" }  ]}
Illustrative. Scoped to Pinpoint only, capped at 2,000 upstream calls, every write confirmed, and the destructive ones approved by a named person.

Cost

What Pinpoint costs on actionlake.

Every Pinpoint action is one upstream call, the only thing actionlake bills. Searching, check, cost, account and any call Pinpoint refused with 401, 403, 429 or a 5xx are free. Paid plans start at US$49 a month for 250,000 calls, with overage from US$0.30 down to US$0.18 per 1,000.

  • 1upstream call per actionall 113 Pinpoint actions
  • 113actions pageeach page of a long list is one call
  • 63reads can be cacheda cache hit costs nothing
  • 100,000calls a month, freepaid plans from US$49 a month for 250,000

See pricing

Action index

Every Pinpoint action.

113 actions by area: the id your agent calls, what it does, and its effect.

Applications5
  • pinpoint.applications.createCreate an applicationwrite
  • pinpoint.applications.deleteDelete an applicationdestructive
  • pinpoint.applications.getGet an applicationread
  • pinpoint.applications.listList applicationsread
  • pinpoint.applications.updateUpdate an applicationwrite
Custom attributes5
  • pinpoint.custom_attributes.createCreate a custom attributewrite
  • pinpoint.custom_attributes.deleteDelete a custom attributedestructive
  • pinpoint.custom_attributes.getGet a custom attributeread
  • pinpoint.custom_attributes.listList custom attributesread
  • pinpoint.custom_attributes.updateUpdate a custom attributewrite
Custom fields5
  • pinpoint.custom_fields.createCreate a custom fieldwrite
  • pinpoint.custom_fields.deleteDelete a custom fielddestructive
  • pinpoint.custom_fields.getGet a custom fieldread
  • pinpoint.custom_fields.listList custom fieldsread
  • pinpoint.custom_fields.updateUpdate a custom fieldwrite
Departments5
  • pinpoint.departments.createCreate a departmentwrite
  • pinpoint.departments.deleteDelete a departmentdestructive
  • pinpoint.departments.getGet a departmentread
  • pinpoint.departments.listList departmentsread
  • pinpoint.departments.updateUpdate a departmentwrite
Divisions5
  • pinpoint.divisions.createCreate a divisionwrite
  • pinpoint.divisions.deleteDelete a divisiondestructive
  • pinpoint.divisions.getGet a divisionread
  • pinpoint.divisions.listList divisionsread
  • pinpoint.divisions.updateUpdate a divisionwrite
Job seekers5
  • pinpoint.job_seekers.createCreate a job seekerwrite
  • pinpoint.job_seekers.deleteDelete a job seekerdestructive
  • pinpoint.job_seekers.getGet a job seekerread
  • pinpoint.job_seekers.listList job seekersread
  • pinpoint.job_seekers.updateUpdate a job seekerwrite
Jobs5
  • pinpoint.jobs.createCreate a jobwrite
  • pinpoint.jobs.deleteDelete a jobdestructive
  • pinpoint.jobs.getGet a jobread
  • pinpoint.jobs.listList jobsread
  • pinpoint.jobs.updateUpdate a jobwrite
Locations5
  • pinpoint.locations.createCreate a locationwrite
  • pinpoint.locations.deleteDelete a locationdestructive
  • pinpoint.locations.getGet a locationread
  • pinpoint.locations.listList locationsread
  • pinpoint.locations.updateUpdate a locationwrite
Requisitions5
  • pinpoint.requisitions.createCreate a requisitionwrite
  • pinpoint.requisitions.deleteDelete a requisitiondestructive
  • pinpoint.requisitions.getGet a requisitionread
  • pinpoint.requisitions.listList requisitionsread
  • pinpoint.requisitions.updateUpdate a requisitionwrite
Structure custom group ones5
  • pinpoint.structure_custom_group_ones.createCreate a structure custom group onewrite
  • pinpoint.structure_custom_group_ones.deleteDelete a structure custom group onedestructive
  • pinpoint.structure_custom_group_ones.getGet a structure custom group oneread
  • pinpoint.structure_custom_group_ones.listList structure custom group onesread
  • pinpoint.structure_custom_group_ones.updateUpdate a structure custom group onewrite
Structure links5
  • pinpoint.structure_links.createCreate a structure linkwrite
  • pinpoint.structure_links.deleteDelete a structure linkdestructive
  • pinpoint.structure_links.getGet a structure linkread
  • pinpoint.structure_links.listList structure linksread
  • pinpoint.structure_links.updateUpdate a structure linkwrite
Users5
  • pinpoint.users.createCreate an userwrite
  • pinpoint.users.deleteDelete an userdestructive
  • pinpoint.users.getGet an userread
  • pinpoint.users.listList usersread
  • pinpoint.users.updateUpdate an userwrite
Answers4
  • pinpoint.answers.createCreate an answerwrite
  • pinpoint.answers.deleteDelete an answerdestructive
  • pinpoint.answers.getGet an answerread
  • pinpoint.answers.updateUpdate an answerwrite
Background checks4
  • pinpoint.background_checks.createCreate a background checkwrite
  • pinpoint.background_checks.getGet a background checkread
  • pinpoint.background_checks.listList background checksread
  • pinpoint.background_checks.updateUpdate a background checkwrite
Candidate assessments4
  • pinpoint.candidate_assessments.createCreate a candidate assessmentwrite
  • pinpoint.candidate_assessments.getGet a candidate assessmentread
  • pinpoint.candidate_assessments.listList candidate assessmentsread
  • pinpoint.candidate_assessments.updateUpdate a candidate assessmentwrite
Comments4
  • pinpoint.comments.createCreate a commentwrite
  • pinpoint.comments.deleteDelete a commentdestructive
  • pinpoint.comments.getGet a commentread
  • pinpoint.comments.listList commentsread
Candidates3
  • pinpoint.candidates.getGet a candidateread
  • pinpoint.candidates.listList candidatesread
  • pinpoint.candidates.updateUpdate a candidatewrite
Interviews3
  • pinpoint.interviews.getGet an interviewread
  • pinpoint.interviews.listList interviewsread
  • pinpoint.interviews.updateUpdate an interviewwrite
Structured section responses3
  • pinpoint.structured_section_responses.createCreate a structured section responsewrite
  • pinpoint.structured_section_responses.deleteDelete a structured section responsedestructive
  • pinpoint.structured_section_responses.updateUpdate a structured section responsewrite
Access groups2
  • pinpoint.access_groups.getGet an access groupread
  • pinpoint.access_groups.listList access groupsread
Candidate surveys2
  • pinpoint.candidate_surveys.getGet a candidate surveyread
  • pinpoint.candidate_surveys.listList candidate surveysread
Equality monitoring categories2
  • pinpoint.equality_monitoring_categories.getGet an equality monitoring categoryread
  • pinpoint.equality_monitoring_categories.listList equality monitoring categoriesread
Hiring workflows2
  • pinpoint.hiring_workflows.getGet a hiring workflowread
  • pinpoint.hiring_workflows.listList hiring workflowsread
Job postings2
  • pinpoint.job_postings.getGet a job postingread
  • pinpoint.job_postings.listList job postingsread
Onboarding applications2
  • pinpoint.onboarding_applications.getGet an onboarding applicationread
  • pinpoint.onboarding_applications.listList onboarding applicationsread
One way video interviews2
  • pinpoint.one_way_video_interviews.getGet an one-way video interviewread
  • pinpoint.one_way_video_interviews.listList one-way video interviewsread
Positions2
  • pinpoint.positions.getGet a positionread
  • pinpoint.positions.listList positionsread
Quality of hire surveys2
  • pinpoint.quality_of_hire_surveys.getGet a quality of hire surveyread
  • pinpoint.quality_of_hire_surveys.listList quality of hire surveysread
Reference checks2
  • pinpoint.reference_checks.getGet a reference checkread
  • pinpoint.reference_checks.listList reference checksread
Requisition templates2
  • pinpoint.requisition_templates.getGet a requisition templateread
  • pinpoint.requisition_templates.listList requisition templatesread
Scorecards2
  • pinpoint.scorecards.getGet a scorecardread
  • pinpoint.scorecards.listList scorecardsread
Structured sections2
  • pinpoint.structured_sections.getGet a structured sectionread
  • pinpoint.structured_sections.listList structured sectionsread
Job templates1
  • pinpoint.job_templates.listList job templatesread
Questions1
  • pinpoint.questions.listList questionsread

Questions

The Pinpoint MCP server, answered.

Is there a Pinpoint MCP server for Claude?

Yes. actionlake is an MCP gateway: a remote MCP server that gives Claude, or another MCP client, 113 Pinpoint actions across applications, custom attributes, custom fields and departments, through the same eight tools it uses for every other connector. actionlake is independent; it is not made or endorsed by Pinpoint.

What do I need to connect Pinpoint?

Pinpoint API key: in Pinpoint open Settings > API & Webhooks, switch the Pinpoint API toggle on, then create a key…. Plus your host. The free call account { op: "connections.requirements", service: "pinpoint" } lists exactly what to paste.

Can an AI agent delete or change things in Pinpoint?

Only if its key allows it, and only with an explicit confirmation. 15 Pinpoint actions are destructive, including delete an user, delete a department and delete a location. Each runs only with confirm: true. Under the human confirm policy, or an approval rule on the key, the run waits until a named person approves it.

Will an AI agent use up my Pinpoint API limit?

actionlake paces every call to the limits in the Pinpoint service file: 120 calls a minute and 240 per 8 minutes per connection. Repeated reads are answered from cache (63 Pinpoint actions can be), which never reaches Pinpoint.

What does a Pinpoint action cost?

One upstream call, the only unit actionlake bills. A list that pages bills one call per page (113 Pinpoint actions page). Cache hits, searches, dry runs and calls Pinpoint refused with 401, 403, 429 or a 5xx are free. The Free plan includes 100,000 calls a month with no card. Paid plans start at US$49 a month for 250,000 calls, with overage from US$0.30 down to US$0.18 per 1,000.

Which Pinpoint API does it cover?

The Pinpoint API v1 (OpenAPI 3.0.1, JSON:API) at your Pinpoint instance's API base URL, which you enter when connecting. It is built from Pinpoint's documentation as read on 23 October 2026. 113 actions in 34 areas, each one in the signed service file (version 1.0.0).

Does actionlake keep my Pinpoint data, and where?

actionlake processes and stores data in Sydney, Australia; there is no US region yet. Reads may be cached for up to 5 minutes, and a write clears the reads it affects. Each run's request and response is kept, sealed, for your plan's trace window: 1 day on Free, 3 days on Starter, 7 days on Pro, 14 days on Team, 30 days on Business and 30 days on Enterprise. Your Pinpoint credential is sealed under your tenant's key, never logged and never returned. Your traffic is not used to train models.

Which AI clients can use it?

Claude Code, tested by us end to end, and the Claude app as a custom connector, tested by us with an existing key. Other MCP clients that support remote servers over Streamable HTTP (MCP revisions 2025-06-18 and 2025-11-25) and OAuth dynamic client registration, or a bearer header, should connect the same way; we have not tested them. Or plain REST, under the same action names.

Give your agent Pinpoint today.

Start free - 100,000 calls/month, no card. No signup. Hard caps on every key. Cached answers are free.