Integrations

Kustomer

Connect Kustomer to find customers, work conversations, draft replies, add notes and tags, and manage custom objects and help articles.

API credentialsSupport & MessagingKustomer API docsKustomer MCP server overview

You paste one Kustomer API key, made under Settings, Security, API Keys. It works for one organization, and PopMCP finds out whether that organization is in the US or EU region for you. The key's roles decide what it can do, and they cannot be changed later.

Setup time
2 min
Auth
API credentials
API base URL
https://api.kustomerapp.com (US) or https://api.prod2.kustomerapp.com (EU)
Rate limits
Depends on your plan: 300 to 2,000 requests a minute across all API keys, with search limited separately to 100 a minute. One record can be updated 100 times in 10 minutes (customers 600), and a single user can update one record 50 times in 10 minutes. Over the limit, Kustomer answers HTTP 429.

Before you begin

  • A Kustomer organization you can sign in to
  • To be an admin, or to have Security permissions. Others can't make API keys.

Get your credentials

Open API Keys in Kustomer

Sign in at your own Kustomer address, such as acme.kustomerapp.com. Open Settings, then Security, then API Keys, and select Add API Key.

acme.kustomerapp.com/app/settings/api_keys
Acme
Settings / Security / API Keys

API Keys

Add API Key
NameRoles
Data warehouse syncUsed by the nightly joborg.permission.customer.read

Name the key and choose its roles

Under Name, enter something you will recognise, like PopMCP. Under Roles, choose org.admin and org.user to reach every tool, or only the roles you want, such as org.user.customer.write. For look-ups only, choose read roles such as org.permission.customer.read, org.permission.conversation.read and org.permission.message.read, plus org.permission.search.create for search. Roles can't be changed after the key is made. Under Expires, choose how many days the key should last. Leave CIDR IP Restriction empty, then select Create.

acme.kustomerapp.com/app/settings/api_keys
Acme
Settings / Security / API Keys

API Keys

Add API Key
Name
PopMCP
Roles
org.admin, org.user
Expires
365 days
CIDR IP Restriction
Optional
CancelCreate

Copy the key

Select Copy Token on the confirmation screen. This is your only chance: Kustomer shows a key once, so if you lose it you need to make a new one.

acme.kustomerapp.com/app/settings/api_keys
Acme
Settings / Security / API Keys

API Keys

This is your only chance to copy the key.
API Key Created
Token
eyJh************************3Rk
Copy Token

Paste the key into PopMCP

Paste it into Kustomer API key. PopMCP tries the key in Kustomer's US and EU regions and remembers where it works. It usually finds your organization's name too. If it says it couldn't, reconnect and add the name under More options: it is the first part of your Kustomer address, and only the public help center tools need it.

Connect in PopMCP

Open your workspace, choose Kustomer in the marketplace, and fill in the connect dialog:

FieldWhat to enter
Kustomer API keysecretFrom Settings > Security > API Keys in Kustomer: Add API Key, then Copy Token. Stored encrypted, used server-side only.Encrypted with AES-256-GCM on save and never shown again.
Organization name (optional)textThe first part of your Kustomer address, as in acme.kustomerapp.com. We usually find it for you. Public help center tools use it.

PopMCP verifies the credential against Kustomer immediately. On success the connection flips to Verified and its MCP tools are provisioned.

Verify it worked

PopMCP shows Kustomer as Verified, labelled with your organization's name, with (EU) added for an organization in the EU region. Ask for your teams: kustomer_list_teams answers with their ids and names.

Troubleshooting

"Kustomer didn't accept this API key in its US or EU region"

Why: The key was copied incompletely, has been deleted, or has an IP restriction.

Fix: Kustomer can't show a key twice, so make a new one under Settings, Security, API Keys without a CIDR IP Restriction, and paste that.

"This Kustomer API key expired"

Why: The number of days chosen under Expires has passed.

Fix: Make a new key and reconnect.

A tool answers that Kustomer refused this key and names roles

Why: The key doesn't have a role that tool needs. Kustomer can also answer this way when your plan lacks the feature.

Fix: Roles can't be changed on an existing key, so make a new key with the role and reconnect.

A public help center tool asks for your organization name

Why: PopMCP couldn't find the name from the key.

Fix: Reconnect and enter it under More options, or use the kustomer_list_kb_articles and kustomer_search_kb_articles tools, which don't need it.

Reference

On this page