# Perk MCP connector

Connect Perk to Elaichi and Claude, ChatGPT, Cursor, Microsoft Copilot or the Elaichi Agent can look up trips, bookings, invoices and cost centers in Perk, each person inside their own access, with every call logged.

Source: https://elaichi.ai/connectors/perk/

## Facts

| | |
| --- | --- |
| Application | Perk |
| Category | Travel |
| AI tools | 36 |
| Authentication | Connects with an API key |
| Bring your own OAuth app | No |
| MCP endpoint | https://api.elaichi.ai/mcp |
| Works with | Claude, ChatGPT, Cursor, Microsoft Copilot, any MCP client, and the Elaichi Agent |
| Tools advertised by name | No. Connected tools are never listed one by one, however few there are. The endpoint advertises `search_tools` and `execute_tool` instead |

## What you can ask once Perk is connected

- Which trips are booked for next week and who is traveling?
- Summarize last month's Perk invoices by cost center.
- Which cost centers have no travelers assigned?

## Connect Perk in Elaichi

This happens once for the organization, before any client is involved.

1. Open Connections, choose Add connection, and pick Perk.
2. Optionally set Share with, then press Connect.
3. Paste a Perk API key. One person generates a token in Perk and pastes it once. Everyone else works through Share with, and never sees it.

Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which Perk tools are exposed, rename them, or freeze arguments before anyone points a client at it.

## Perk MCP connector for Claude

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

1. Open Customize, then Connectors.
2. Press Add.
3. Name it, paste the MCP server URL, then Continue.
4. Sign in and approve.

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

## Perk MCP connector for Claude Code

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

1. In a terminal, run `claude mcp add` with the endpoint.
2. Start Claude Code and run `/mcp`.
3. Pick elaichi, then sign in and approve in the browser.

```bash
claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp
```

Use `--scope project` instead to share it with the repository through `.mcp.json`.

## Perk MCP connector for ChatGPT

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

1. Open Plugins, then press the + button.
2. Name it and paste the endpoint into Server URL.
3. Leave Authentication on OAuth, then tick the risk acknowledgement.
4. Press Create, then sign in and approve.

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

## Perk MCP connector for Cursor

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

1. Open `~/.cursor/mcp.json`.
2. Add the endpoint under `mcpServers`.
3. Reload Cursor, then sign in and approve.

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

## Perk MCP connector for Microsoft Copilot

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

1. In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
2. Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
3. Create a new connection, sign in and approve, then press Add to agent.
4. Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.

Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.

## Connect Perk to any MCP client

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

1. Add the endpoint as a remote MCP server.
2. Sign in and approve.

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

## What the consent screen decides

Every scope the client asks for starts ticked except "Delete things", which you tick yourself. Calling a Perk tool needs "Use your connected apps". Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Think hard before granting Use your connected apps, which can also delete in connected apps and cannot be undone.

## What teams do with Perk through Elaichi

### Pull the month's invoices by cost center

Finance. Ask for every Perk invoice from last month grouped by cost center and get the lines behind each one. Open the PDF for any invoice that needs checking before the close.

### Keep cost centers tidy

Finance. Create a new cost center when a project starts, rename one that changed, or update a batch at once. Move travelers between cost centers in one go instead of editing each person.

### See who is traveling next week

Travel desk. List upcoming Perk trips and the bookings inside them, then check a single trip when a traveler calls with a question.

### Answer a travel question on the spot

Operations. A manager asks what was booked for the offsite, and the answer comes from the live Perk bookings rather than a forwarded email.

### Check travelers and profiles

People. List the users and profiles in your Perk account, see which company they belong to, and spot anyone missing from the right cost center.

### Keep trip custom fields current

Travel desk. List the custom fields on trips, add a new option to a dropdown when a new project appears, and archive options nobody should pick anymore.

## Elaichi vs Zapier MCP vs Composio for Perk

All three can connect Perk to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.

| What to check | Elaichi | Zapier MCP | Composio |
| --- | --- | --- | --- |
| Where the AI connects | One address for the whole organization. Endpoint: https://api.elaichi.ai/mcp | A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over Perk tools | Allow or restrict single Perk tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per Perk call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | Free for one person; $15 per user per month on Gold. | 2 tasks per successful call. | Billed per tool call. |

Sources: Zapier MCP [docs](https://docs.zapier.com/mcp/get-started/quickstart), [security](https://docs.zapier.com/mcp/manage/security), [usage](https://docs.zapier.com/mcp/features/usage); Composio [docs](https://docs.composio.dev/docs/composio-connect), [gateway](https://composio.dev/mcp-gateway), [enterprise](https://composio.dev/enterprise), [pricing](https://composio.dev/pricing). Checked September 2026.

Longer take: [Zapier MCP alternative](/blog/zapier-mcp-alternative/) and [when you don't need an MCP gateway](/blog/when-you-dont-need-an-mcp-gateway/).

## Frequently asked questions

### How do I connect Perk to Claude?

Connect Perk in Elaichi by pasting in a Perk API key, which takes a minute and needs 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 as yourself and Claude can start reading your Perk trips, bookings and invoices.

### Does Perk work with ChatGPT and Cursor as well as Claude?

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

### What can an AI agent actually do with my Perk data?

It can list and look up trips, bookings, invoices and invoice lines in Perk, open an invoice PDF, and show the users, profiles and companies in your account. It can also create and update cost centers, including bulk changes and moving travelers between them, manage trip custom field options, and set up webhooks. Short, concrete asks like "invoices for cost center Marketing in March" work better than long paragraphs.

### Does connecting Perk give the AI access to every trip and invoice in the account?

No. Each person signs in to Elaichi as themselves, so the agent sees only what that person's Perk access already allows. Elaichi can narrow that further with roles and restrictions, and it never widens what someone could already see in Perk.

### Can my team share one Perk connection?

Yes. One person connects Perk with the API key and shares the connection with a team, and nobody else ever handles the key. Each teammate still signs in to Elaichi as themselves, so the audit log names the person who looked up a trip or changed a cost center.

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

Yes. Restrictions in Elaichi apply per action, so you can allow reading Perk invoices and trips while restricting cost center updates or webhook deletion, for a role or for one person. A restricted tool still appears in Elaichi's tool search, flagged as restricted, but no client can run it whatever the prompt says.

### What happens to a Perk connection when someone leaves?

Offboarding that person in Elaichi ends their access to Perk through every client at once. A shared Perk connection keeps working for everyone else on the team. If you ever want to remove Perk entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor, Microsoft Copilot and every other client.

### Does the Perk MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. Perk is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.

### Is Elaichi an alternative to Zapier MCP for Perk?

Yes. Both let Claude, ChatGPT or Cursor use Perk. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Perk call.

### How is Elaichi different from Composio for Perk?

Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Perk: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.

## All 36 Perk tools

Every tool below is callable through https://api.elaichi.ai/mcp once Perk is connected, subject to the toolbox it is in and the restrictions on the caller.

- **List all Perk profiles** (List). List all invoice profiles associated to this TravelPerk account. Returns: id, company_id, name, payment_method_type, billing_period, currency, billing_information.
- **List all Perk invoices** (List). List TravelPerk invoices with filters for profile, serial number, billing period, status, issuing and due dates, and sort order. Returns: serial_number, profile_id, profile_name, billing_information, tk_billing_address, mode, status, due_date, currency, total, and 11 more. Only invoices issued on or after January 1st 2019 are returned.
- **Get single Perk invoice by ID** (Get). Get a single TravelPerk invoice by id, where id is the invoice serial number (e.g. INV-01-987654). Returns the full invoice including serial_number, profile_name, status, total, taxes_summary, lines, and pdf. Required: id.
- **List all Perk invoices lines** (List). List all invoice lines in TravelPerk with optional filters. Returns: id, expense_date, description, quantity, unit_price, total_amount, metadata, invoice_serial_number, invoice_status, currency, and 10 more. Only invoices issued on or after January 1st 2019 are returned; network_transaction_id cannot be combined with other filters.
- **Get single Perk invoice PDF by ID** (Get). Download a TravelPerk invoice in PDF format. Returns the invoice document itself as binary PDF file content, not a JSON object. INV-01-987654). Required: id.
- **List all Perk trips** (List). List all trips in TravelPerk, returned in descending order of modified time. Returns: id, trip_name, start, start_datetime_utc, start_datetime_local, end, end_datetime_utc, end_datetime_local, status, modified, start_location, end_location, booker_id.
- **Get single Perk trip by ID** (Get). Get a single TravelPerk trip by id. Returns: id, trip_name, start, start_datetime_utc, start_datetime_local, end, end_datetime_utc, end_datetime_local, status, modified, start_location, end_location, booker_id. Required: id.
- **List all Perk trip custom fields** (List). List all custom field values associated with a trip in TravelPerk. Returns: trip_id, created_date, custom_fields (each with name and value). Required: trip_id.
- **List all Perk companies** (List). List all companies associated to this TravelPerk account. Returns: id, name, address, tax_id, enabled, is_default. Max 50 per page.
- **List all Perk cost centers** (List). List all cost centers in your Perk organization. Returns each cost center's id, name, type, and count_users. The type field is only present when cost object types are enabled for your organization.
- **Create a Perk cost center** (Create). Create a cost center in Perk with the given name. Returns the created cost center including id, name, type, archived, approver, delegate, company scope, and owners. Required: name.
- **Get single Perk cost center by ID** (Get). Get a single Perk cost center by id. Returns the full cost center including name, type, archived, approver, delegate, assigned users, company scope, and owners. Required: id.
- **Update a Perk cost center by ID** (Update). Update a Perk cost center by id — rename it, archive or unarchive it, change approver, delegate, delegate expiry, company scope, or cost object type. Returns the updated cost center including id, name, type, archived, approver, delegate, and owners. Required: id.
- **Perk cost centers bulk updates bulk update** (Update). Bulk update Perk cost centers in a single request: archive or unarchive them and/or set their cost object type. Returns: updated_count. When cost object types are not enabled, archive is required; when enabled, supply at least one of archive or a non-null type (max 256 chars; fails with 400 if any listed cost…. Required: id_list.
- **Perk cost center users bulk update** (Update). Replace all users assigned to a Perk cost center with the provided list; any users not in the list are removed from the cost center. Returns the updated cost center including id, name, users, count_users, and owners. Required: cost_center_id.
- **List all Perk custom field select options** (List). List the select options of a Perk custom field, filterable by value substring and status. Returns options with id, value, and is_archived. Required: custom_field_id. Max 100 options per page.
- **Create a Perk custom field select option** (Create). Create one or more select options on a Perk custom field, which must be a select or multi-select field with target 'BOOKING'. Returns the created or revived options with id, value, is_archived, and erp_code. Required: custom_field_id, select_options.
- **Perk custom field select options archive** (Archive). Archive or unarchive a select option on a Perk custom field. Returns the option's resulting state with id, value, and is_archived. Required: custom_field_id, option_id, archive_action. Idempotent; unarchiving is rejected if another active option on the field has the same value.
- **List all Perk users** (List). List Perk users, a read-only view of user information in the account (user management itself is handled separately via SCIM). Returns: id, attributes (the remaining user fields are not enumerated upstream).
- **List all Perk bookings** (List). List bookings in Perk trips, ordered by modified time (most recent first). Returns each booking with id, trip_id, type (flight, train, hotel, car hire), status, start/end times, references, location, and legs. MICE bookings are not supported.
- **Get single Perk webhook by ID** (Get). Get a TravelPerk webhook endpoint by id. Returns the webhook subscription including id, name, url, secret, status, and its subscribed events. Required: id.
- **Create a Perk webhook** (Create). Create a TravelPerk webhook endpoint that subscribes to one or more events. Returns the created subscription: id, name, url, secret, status, events, and delivery stats (successfully_sent, failed_sent, error_rate). The target url must be unique for the account.
- **Update a Perk webhook by ID** (Update). Update a TravelPerk webhook endpoint by id — edit its name, url, secret, status, or subscribed events. Returns the updated webhook: id, name, url, secret, status, events. The target url must be unique for the account (HTTP 409 otherwise). Required: id.
- **Delete a Perk webhook by ID** (Delete). Delete a TravelPerk webhook endpoint by id. Returns an empty 204 response on success. Required: id.
- **Create a Perk SCIM user** (Create). Create a new user in Perk via SCIM. Returns the created user resource including id, userName, name, active, phoneNumbers, meta, and travel attributes (gender, dateOfBirth, travelPolicy, travelDocuments). Required: userName, name (givenName, familyName), active.
- **List all Perk SCIM users** (List). List SCIM-provisioned users in Perk. Returns user records with id, userName, name, active, phoneNumbers, meta, and travel attributes (gender, dateOfBirth, travelPolicy). Filter with a SCIM expression, e.g. filter=externalId eq &lt;id&gt;; max 100 per page.
- **Get single Perk SCIM user by ID** (Get). Get a single SCIM user in Perk by id. Returns the full user resource including id, userName, name, active, phoneNumbers, meta, and travel attributes (gender, dateOfBirth, travelPolicy, travelDocuments). Required: id.
- **Update a Perk SCIM user by ID** (Update). Update an existing Perk SCIM user by id. Returns the updated user resource including id, userName, name, active, phoneNumbers, meta, and travel attributes (gender, dateOfBirth, travelPolicy, travelDocuments). Required: id, userName, name (givenName, familyName), active.
- **Delete a Perk SCIM user by ID** (Delete). Delete a Perk SCIM user by id. Returns an empty 204 response on success. Required: id.
- **Perk SCIM users bulk update** (Update). Update attributes of an existing Perk SCIM user via a SCIM PatchOp body (add, remove, or replace operations); attributes not included stay unchanged. Returns the updated user: id, username, name, active, meta. Required: user_id, schemas, Operations. userName, name.givenName, name.familyName and active must not be null or empty.
- **List all Perk SCIM schemas** (List). List the SCIM schemas available in Perk (e.g. the User schema and the perkCustomFields extension schema). Returns each schema's id (URN), name, description, attributes, and meta.
- **Get single Perk SCIM schema by ID** (Get). Get a Perk SCIM schema by id (the schema URN, e.g. urn:ietf:params:scim:schemas:core:2.0:User) and all its attributes. Returns: id, name, description, attributes, meta, openapi, info, servers, components, security, paths, x-readme, x-readme-fauxas. Required: id.
- **List all Perk suppliers** (List). List suppliers in Perk. Returns the collection of supplier records as served by the suppliers endpoint; the supplier fields are not enumerated in Perk's current documentation, so treat the record shape as opaque.
- **Perk cost center access bulk update** (Update). Set the access configuration for a Perk cost center, controlling which users and user groups can access it. Returns the updated cost center including access_type, users, groups, approver, and delegate details. Required: cost_center_id, access_type.
- **Create a Perk webhook test** (Create). Send a test notification to a Perk webhook endpoint. Returns the test stub payload with test set to true, which Perk fires to the webhook's target URL. Required: webhook_id.
- **List all Perk webhook events** (List). List the webhook event types available in Perk that can be subscribed to (invoice.issued, trip.created/updated). Returns each event's model and trigger, with the trip.created/updated payload including id, trip_name, start/end datetime fields, status, modified, start_location, end_location, bookings, and booker_id.
