---
title: "Pinpoint MCP server for AI agents - actionlake"
description: "Give Claude 113 Pinpoint actions through one MCP server: applications, custom attributes. Your agent never holds the credential. 100,000 calls a month free."
canonical: https://actionlake.com/connectors/pinpoint
updated: 2026-10-23
---

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.

[Connect Pinpoint free](https://actionlake.com/console?start=sandbox) [See pricing](https://actionlake.com/pricing)

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
```

- 113 actions in one signed file
- 63 read look, never change
- 35 write create and update
- 15 wait for a yes destructive, 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_key` Pinpoint API key: in Pinpoint open Settings > API & Webhooks, switch the Pinpoint API toggle on, then create a key…
   - `host` Where 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 call
   check { 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 2026[developers.pinpointhq.com](https://developers.pinpointhq.com/reference) [developers.pinpointhq.com](https://developers.pinpointhq.com/docs/introduction)

**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.

- **63** read look, never change
- **35** write create and update
- **15** destructive wait 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.

| Action | What it does | Effect | Same name in |
| --- | --- | --- | --- |
| `pinpoint.users.list` List users | List users. | read | `identity.user.list` 474 connectors |
| `pinpoint.departments.list` List departments | List departments. | read | `hr.department.list` 40 connectors |
| `pinpoint.locations.list` List locations | List locations. | read | `hr.location.list` 32 connectors |
| `pinpoint.candidates.list` List candidates | List candidates. | read | `hr.candidate.list` 22 connectors |
| `pinpoint.users.create` Create an user | Create an user. | write | `identity.user.create` 262 connectors |
| `pinpoint.departments.create` Create a department | Create a department. | write | `hr.department.create` 32 connectors |
| `pinpoint.locations.create` Create a location | Create a location. | write | `hr.location.create` 23 connectors |
| `pinpoint.users.delete` Delete an user | Delete an user. | destructive | `identity.user.delete` 253 connectors |
| `pinpoint.candidates.get` Get a candidate | Get a candidate. | read | `hr.candidate.get` 19 connectors |
| `pinpoint.jobs.list` List jobs | List jobs. | read | `hr.job_opening.list` 24 connectors |
| `pinpoint.jobs.create` Create a job | Create a job. | write | `hr.job_opening.create` 15 connectors |
| `pinpoint.applications.list` List applications | List applications. | read | `hr.application.list` 15 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. Read read
   Who has access in Pinpoint? List every user and their role.
   calls `pinpoint.users.list`
2. Write write
   Create an user in Pinpoint. Show me exactly what you will send before you save it.
   calls `pinpoint.users.create`

Governance for Pinpoint

## Destructive actions wait for a yes.

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

- Delete an user `pinpoint.users.delete`
- Delete a department `pinpoint.departments.delete`
- Delete a location `pinpoint.locations.delete`
- Delete an application `pinpoint.applications.delete`
- Delete a job `pinpoint.jobs.delete`
- Delete an answer `pinpoint.answers.delete`
- Delete a comment `pinpoint.comments.delete`
- Delete a division `pinpoint.divisions.delete`
- Delete a job seeker `pinpoint.job_seekers.delete`
- Delete a requisition `pinpoint.requisitions.delete`
- Delete a custom field `pinpoint.custom_fields.delete`
- Delete a structure link `pinpoint.structure_links.delete`
- Delete a custom attribute `pinpoint.custom_attributes.delete`
- Delete a structure custom group one `pinpoint.structure_custom_group_ones.delete`
- Delete a structured section response `pinpoint.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.

do pinpoint.users.delete confirm_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: "lead@example.com" },
    { match: "pinpoint.departments.delete", approver: "lead@example.com" },
    { match: "pinpoint.locations.delete", approver: "lead@example.com" }
  ]
}
```

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.

- 1 upstream call per action all 113 Pinpoint actions
- 113 actions page each page of a long list is one call
- 63 reads can be cached a cache hit costs nothing
- 100,000 calls a month, free paid plans from US$49 a month for 250,000

[See pricing](https://actionlake.com/pricing)

Action index

## Every Pinpoint action.

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

**Applications 5**

- `pinpoint.applications.create` Create an application write
- `pinpoint.applications.delete` Delete an application destructive
- `pinpoint.applications.get` Get an application read
- `pinpoint.applications.list` List applications read
- `pinpoint.applications.update` Update an application write

**Custom attributes 5**

- `pinpoint.custom_attributes.create` Create a custom attribute write
- `pinpoint.custom_attributes.delete` Delete a custom attribute destructive
- `pinpoint.custom_attributes.get` Get a custom attribute read
- `pinpoint.custom_attributes.list` List custom attributes read
- `pinpoint.custom_attributes.update` Update a custom attribute write

**Custom fields 5**

- `pinpoint.custom_fields.create` Create a custom field write
- `pinpoint.custom_fields.delete` Delete a custom field destructive
- `pinpoint.custom_fields.get` Get a custom field read
- `pinpoint.custom_fields.list` List custom fields read
- `pinpoint.custom_fields.update` Update a custom field write

**Departments 5**

- `pinpoint.departments.create` Create a department write
- `pinpoint.departments.delete` Delete a department destructive
- `pinpoint.departments.get` Get a department read
- `pinpoint.departments.list` List departments read
- `pinpoint.departments.update` Update a department write

**Divisions 5**

- `pinpoint.divisions.create` Create a division write
- `pinpoint.divisions.delete` Delete a division destructive
- `pinpoint.divisions.get` Get a division read
- `pinpoint.divisions.list` List divisions read
- `pinpoint.divisions.update` Update a division write

**Job seekers 5**

- `pinpoint.job_seekers.create` Create a job seeker write
- `pinpoint.job_seekers.delete` Delete a job seeker destructive
- `pinpoint.job_seekers.get` Get a job seeker read
- `pinpoint.job_seekers.list` List job seekers read
- `pinpoint.job_seekers.update` Update a job seeker write

**Jobs 5**

- `pinpoint.jobs.create` Create a job write
- `pinpoint.jobs.delete` Delete a job destructive
- `pinpoint.jobs.get` Get a job read
- `pinpoint.jobs.list` List jobs read
- `pinpoint.jobs.update` Update a job write

**Locations 5**

- `pinpoint.locations.create` Create a location write
- `pinpoint.locations.delete` Delete a location destructive
- `pinpoint.locations.get` Get a location read
- `pinpoint.locations.list` List locations read
- `pinpoint.locations.update` Update a location write

**Requisitions 5**

- `pinpoint.requisitions.create` Create a requisition write
- `pinpoint.requisitions.delete` Delete a requisition destructive
- `pinpoint.requisitions.get` Get a requisition read
- `pinpoint.requisitions.list` List requisitions read
- `pinpoint.requisitions.update` Update a requisition write

**Structure custom group ones 5**

- `pinpoint.structure_custom_group_ones.create` Create a structure custom group one write
- `pinpoint.structure_custom_group_ones.delete` Delete a structure custom group one destructive
- `pinpoint.structure_custom_group_ones.get` Get a structure custom group one read
- `pinpoint.structure_custom_group_ones.list` List structure custom group ones read
- `pinpoint.structure_custom_group_ones.update` Update a structure custom group one write

**Structure links 5**

- `pinpoint.structure_links.create` Create a structure link write
- `pinpoint.structure_links.delete` Delete a structure link destructive
- `pinpoint.structure_links.get` Get a structure link read
- `pinpoint.structure_links.list` List structure links read
- `pinpoint.structure_links.update` Update a structure link write

**Users 5**

- `pinpoint.users.create` Create an user write
- `pinpoint.users.delete` Delete an user destructive
- `pinpoint.users.get` Get an user read
- `pinpoint.users.list` List users read
- `pinpoint.users.update` Update an user write

**Answers 4**

- `pinpoint.answers.create` Create an answer write
- `pinpoint.answers.delete` Delete an answer destructive
- `pinpoint.answers.get` Get an answer read
- `pinpoint.answers.update` Update an answer write

**Background checks 4**

- `pinpoint.background_checks.create` Create a background check write
- `pinpoint.background_checks.get` Get a background check read
- `pinpoint.background_checks.list` List background checks read
- `pinpoint.background_checks.update` Update a background check write

**Candidate assessments 4**

- `pinpoint.candidate_assessments.create` Create a candidate assessment write
- `pinpoint.candidate_assessments.get` Get a candidate assessment read
- `pinpoint.candidate_assessments.list` List candidate assessments read
- `pinpoint.candidate_assessments.update` Update a candidate assessment write

**Comments 4**

- `pinpoint.comments.create` Create a comment write
- `pinpoint.comments.delete` Delete a comment destructive
- `pinpoint.comments.get` Get a comment read
- `pinpoint.comments.list` List comments read

**Candidates 3**

- `pinpoint.candidates.get` Get a candidate read
- `pinpoint.candidates.list` List candidates read
- `pinpoint.candidates.update` Update a candidate write

**Interviews 3**

- `pinpoint.interviews.get` Get an interview read
- `pinpoint.interviews.list` List interviews read
- `pinpoint.interviews.update` Update an interview write

**Structured section responses 3**

- `pinpoint.structured_section_responses.create` Create a structured section response write
- `pinpoint.structured_section_responses.delete` Delete a structured section response destructive
- `pinpoint.structured_section_responses.update` Update a structured section response write

**Access groups 2**

- `pinpoint.access_groups.get` Get an access group read
- `pinpoint.access_groups.list` List access groups read

**Candidate surveys 2**

- `pinpoint.candidate_surveys.get` Get a candidate survey read
- `pinpoint.candidate_surveys.list` List candidate surveys read

**Equality monitoring categories 2**

- `pinpoint.equality_monitoring_categories.get` Get an equality monitoring category read
- `pinpoint.equality_monitoring_categories.list` List equality monitoring categories read

**Hiring workflows 2**

- `pinpoint.hiring_workflows.get` Get a hiring workflow read
- `pinpoint.hiring_workflows.list` List hiring workflows read

**Job postings 2**

- `pinpoint.job_postings.get` Get a job posting read
- `pinpoint.job_postings.list` List job postings read

**Onboarding applications 2**

- `pinpoint.onboarding_applications.get` Get an onboarding application read
- `pinpoint.onboarding_applications.list` List onboarding applications read

**One way video interviews 2**

- `pinpoint.one_way_video_interviews.get` Get an one-way video interview read
- `pinpoint.one_way_video_interviews.list` List one-way video interviews read

**Positions 2**

- `pinpoint.positions.get` Get a position read
- `pinpoint.positions.list` List positions read

**Quality of hire surveys 2**

- `pinpoint.quality_of_hire_surveys.get` Get a quality of hire survey read
- `pinpoint.quality_of_hire_surveys.list` List quality of hire surveys read

**Reference checks 2**

- `pinpoint.reference_checks.get` Get a reference check read
- `pinpoint.reference_checks.list` List reference checks read

**Requisition templates 2**

- `pinpoint.requisition_templates.get` Get a requisition template read
- `pinpoint.requisition_templates.list` List requisition templates read

**Scorecards 2**

- `pinpoint.scorecards.get` Get a scorecard read
- `pinpoint.scorecards.list` List scorecards read

**Structured sections 2**

- `pinpoint.structured_sections.get` Get a structured section read
- `pinpoint.structured_sections.list` List structured sections read

**Job templates 1**

- `pinpoint.job_templates.list` List job templates read

**Questions 1**

- `pinpoint.questions.list` List questions read

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.

## More connectors like Pinpoint

Shares the most action names with

- [Teamtailor 28](https://actionlake.com/connectors/teamtailor)
- [Recruitee 20](https://actionlake.com/connectors/recruitee)
- [Greenhouse Harvest 20](https://actionlake.com/connectors/greenhouse-harvest)
- [SmartRecruiters 19](https://actionlake.com/connectors/smartrecruiters)
- [Gem 16](https://actionlake.com/connectors/gem)
- [Lever 15](https://actionlake.com/connectors/lever)

Joins with, on shared entities

- [Rippling 4](https://actionlake.com/connectors/rippling)
- [Gusto 3](https://actionlake.com/connectors/gusto)
- [Factorial 3](https://actionlake.com/connectors/factorial)
- [Sesame HR 3](https://actionlake.com/connectors/sesame-hr)
- [Kombo 3](https://actionlake.com/connectors/kombo)
- [Brex 3](https://actionlake.com/connectors/brex)

Browse

- [All Work & projects connectors](https://actionlake.com/connectors/category/work-and-projects)
- [All connectors](https://actionlake.com/connectors)
- [How actionlake compares](https://actionlake.com/compare)

actionlake is independent. It is not made or endorsed by Pinpoint; the name is the vendor's own. Counts are from the Pinpoint service file, version 1.0.0.

## Give your agent Pinpoint today.

[Connect Pinpoint free](https://actionlake.com/console?start=sandbox) [See pricing](https://actionlake.com/pricing)

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

---

Source: https://actionlake.com/connectors/pinpoint
More: https://actionlake.com/llms.txt