CallRail
Connect CallRail to see which marketing drives your phone calls, read call recordings and transcripts, qualify leads, and manage tracking numbers and texts.
You end up with one CallRail API key, a long hex string, which goes into PopMCP's API key field.
- Setup time
- 3 min
- Auth
- API credentials
- API base URL
- https://api.callrail.com/v3
- Rate limits
- 1,000 requests an hour and 10,000 a day for general endpoints. SMS sends (150/hour, 1,000/day) and outbound calls (100/hour, 2,000/day) are capped lower, and over-limit requests return HTTP 429.
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
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.
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.
API Keys
Keys you created. Keys made by other users are never listed here.
| Name | Key | Version | Created |
|---|---|---|---|
| Reporting exportcreated by you | a71b****4e08 | v2 | Mar 4, 2026 |
| Legacy dashboardcreated by you | c904****11fd | v1 | Nov 18, 2025 |
Rename a key with the pencil icon in the Name column. Remove one with the Delete icon on the right.
Create the key
Click Create API V2 Key, type a name such as PopMCP, and click Create.
API Keys
There is no scope picker. The key acts with the permissions of the user who made it.
Copy the key into PopMCP
Copy the value from the confirmation dialog and paste it into PopMCP's API key field.
API Keys
- Base URL
- https://api.callrail.com/v3/
- Header
- Authorization: Token token="****"
Treat the key like a password. Anyone holding it can read your call recordings.
Connect in PopMCP
Open your workspace, choose CallRail in the marketplace, and fill in the connect dialog:
| Field | What to enter |
|---|---|
| API keysecret | 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.Encrypted with AES-256-GCM on save and never shown again. |
PopMCP verifies the credential against CallRail immediately. On success the connection flips to Verified and its MCP tools are provisioned.
Verify it worked
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
Why: 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
Why: 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
Why: 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
Why: 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
Why: 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
Why: You crossed the hourly or daily quota.
Fix: Pause and retry after the window resets, or ask CallRail support to raise the limit.