# CallRail setup for PopMCP

You end up with one CallRail API key, a long hex string, which goes into PopMCP's API key field.

- Auth: API credentials
- Setup time: 3 min
- API base URL: https://api.callrail.com/v3
- Credentials screen: https://app.callrail.com/
- Provider docs: https://apidocs.callrail.com/

## Before you begin

- A CallRail account on any plan
- Sign in as a user who can see every company you want the MCP to reach. Keys are personal and inherit that user's permissions
- That same user needs the rights to send texts or place outbound calls if you want those tools to work

## Get your credentials

### 1. Sign in as the right CallRail user

Sign in at app.callrail.com as the user whose company access you want the AI to have.

Screen: https://app.callrail.com/

### 2. Open the API Keys page

Click your name at the bottom left, choose My Account, then select API Keys under the Security heading in the left menu.

Screen: https://app.callrail.com/

### 3. Create the key

Click Create API V2 Key, type a name such as `PopMCP`, and click Create.

### 4. Copy the key into PopMCP

Copy the value from the confirmation dialog and paste it into PopMCP's API key field.

## Fields PopMCP asks for

- API key (apiKey) [required]: In CallRail, click your name (bottom left) → My Account → API Keys → Create API key, then copy the value. The key inherits the permissions of the user who creates it, so make it with an account that can see every company you want this MCP to reach. Sent as an Authorization: Token header, stored encrypted, used server-side only.

## Verify

PopMCP marks the CallRail connection Connected and the account or company tools return your CallRail companies with their names and IDs.

## Troubleshooting

### 401 Unauthorized on every call

Cause: The key was mistyped, has extra whitespace, or was deleted in CallRail.

Fix: Create a fresh key on the API Keys page and paste it again with no surrounding spaces.

### You cannot find a key a colleague made

Cause: The API Keys page lists only keys created by the signed-in user, even for admins.

Fix: Create your own key, or ask that colleague to send theirs.

### Some companies are missing

Cause: API keys inherit the permissions of the user who created them.

Fix: Have an account-level user create the key, then reconnect in PopMCP with that key.

### The button reads Create API V3 Key, not V2

Cause: Some accounts show a newer label on the same screen.

Fix: Use it. Either button mints a token the v3 API accepts.

### 403 on sending a text or tagging a call

Cause: The user who created the key lacks that permission in CallRail.

Fix: Grant the user the missing permission, or create the key from an account-level user, then reconnect.

### 429 Too Many Requests

Cause: You crossed the hourly or daily quota.

Fix: Pause and retry after the window resets, or ask CallRail support to raise the limit.

---

Source: https://www.docs.popmcp.com/docs/integrations/call-rail/