Pult Docs

MCP Server

Use your organization's Pult data in AI assistants such as Claude, through the MCP server.

The Pult MCP server lets AI assistants read your organization's data in Pult. You ask a question in plain language, and the assistant fetches what it needs. It reads the same data as the REST API and can't change anything.

WhatValue
Server URLhttps://api.pult.com/v1beta/mcp
TransportStreamable HTTP
AuthenticationOAuth, or an API key in the Authorization header

What the assistant can see

  • With OAuth, each person connects the assistant to their own Pult account, and it reads with that person's rights (see Who can connect).
  • With an API key, the assistant reads with the key owner's admin rights, so it sees what an admin sees in the dashboard's reports. In a shared AI workspace (a Claude Team or Enterprise workspace, or a shared Langdock connection, for example) every member uses the same key, whatever their role in Pult. Create a dedicated key for each AI tool, so you can revoke it on its own.

See Authentication for both.

What you can ask

  • "How many people were in each office location every day last week?"
  • "On which days was Anna in the office this month?"
  • "Who has an office booking at the Berlin office for Friday?"
  • "Which team booked the most home office days in October?"
  • "Which visitors are expected at the Berlin office tomorrow?"

Bookings, presence and visits cover at most 31 days per request. For a longer period, the assistant has to ask several times.

Tools

ToolWhat it returns
list_usersYour organization's users, active ones by default
get_userOne user, whatever their status
list_groupsYour organization's groups
get_groupOne group
list_officesYour organization's offices, active ones by default
get_officeOne office, archived or not
list_bookingsBookings for up to 31 days
get_bookingOne booking
list_presence_locationsThe places where presence is detected
get_presence_locationOne presence location
list_presence_daysWho was detected at which presence location, per day, for up to 31 days
list_presence_location_countsHow many people were detected per presence location and day, for up to 31 days
list_visitsVisits for up to 31 days, in every status
get_visitOne visit

Each tool matches one endpoint of the reference and returns the same data, except that characters that hide or reorder text (such as zero-width spaces and direction controls) are removed, so the assistant reads what you would see. The REST API returns text exactly as stored.

The assistant sees only the tools your key or connection, and your organization, can use: the booking tools need Pult Workplace, the office tools Pult Workplace or Pult Visitors, the presence tools Pult Presence, and the visit tools Pult Visitors. The server also names the tools it left out and why, so an assistant that receives this can tell you what to do.

Errors

Rate limits and errors are the same as for the REST API. They reach you in one of two ways:

  • As the tool's result, when a call is refused with organization_disabled, api_not_enabled, api_key_paused, connection_paused, feature_not_enabled or rate_limited. The result carries the same error object as the REST API, so the assistant can explain it, or wait the seconds in data.retryAfterSeconds and try again.
  • As an HTTP error to your AI tool, for a missing, invalid, expired or revoked key or access token, a key or connection that lacks a tool's scope, the per IP address limit, and any error while your AI tool connects. These reach your AI tool rather than the assistant. See Authentication for these errors and Rate limits for the wait.

Connect an AI tool

With OAuth

Add the server URL in your AI tool, without a key. If the tool asks how to authenticate, choose OAuth, and if it offers to send the resource parameter, leave that on. The tool opens Pult in your browser: sign in and approve the connection (see Connect with OAuth).

AI toolStatus
ClaudeTested
ChatGPTTested
Claude CodeTested
LangdockTested
Microsoft 365 CopilotTested
CursorExpected to work
VS CodeExpected to work

"Tested" means we connected the tool to Pult end to end. "Expected to work" means the tool's own documentation says it registers itself and sends the resource parameter, and we have not tested it yet. Other tools that do both should work too, whether they register with a client secret or without one.

Microsoft 365 Copilot: in the Microsoft 365 admin center, connect Pult's MCP server with DCR (OAuth 2.0). Then select Authorize right away, sign in to Pult and approve as an admin. Pult may remove a registration that never connects an account, so don't leave it for later. In a tenant without a Copilot license, the admin center can stop with "an access token could not be acquired for the authentication service" before it reaches Pult: connect from a tenant with Copilot.

With an API key

Add the server URL in your AI tool and send your key in the Authorization header. Tools ask for the key in one of two ways:

  • The whole header value: type Bearer pult_<key>, with the space.
  • Only the key: type pult_<key>. The tool adds Bearer itself, so typing it would double it.
AI toolWhat to enterStatus
Claude Code--header "Authorization: Bearer pult_<key>"Tested
ClaudeRequest header authorization: Bearer pult_<key>Expected to work
Copilot StudioAPI key, type Header, Authorization: Bearer pult_<key>Expected to work
LangdockAPI key, header type "Authorization: Bearer": pult_<key>Expected to work
Le ChatAPI token, Bearer: pult_<key>Expected to work
n8nBearer Auth credential: pult_<key>Expected to work
CodexBearer token: pult_<key>Expected to work
CursorHeader Authorization: Bearer pult_<key>Expected to work
VS CodeHeader Authorization: Bearer pult_<key>Expected to work
Gemini CLIHeader Authorization: Bearer pult_<key>Expected to work
ZedHeader Authorization: Bearer pult_<key>Expected to work

"Expected to work" means the tool's own documentation supports an API key in a header, and we have not tested it yet. In Claude, the Request headers option is a beta that not every account has yet.

For Claude Code, add the server with one command:

claude mcp add --transport http pult https://api.pult.com/v1beta/mcp \
  --header "Authorization: Bearer pult_<key>"

Not supported yet

Gemini Enterprise connects to MCP servers only with a client ID and secret that an admin registers with the server in advance. Pult doesn't offer registering apps that way yet.

Last updated on

On this page