CallRail MCP server

Read from the package source without running it. The installed server may list more.

• add_call_tags

  Append tags to a call WITHOUT replacing existing ones.

• bulk_update_callswrite action

  Apply the same update to every call matching a filter.

• call_eligibility_check

  Audit whether a specific call is/was eligible to count as a Google Ads conversion. Useful for "where did my conversion go" debugging.

• call_stats

  Server-side call aggregation via CallRail's /calls/summary.json.

• call_summary

  Summarize calls over a date window.

• call_timeseries

  Call volume over time via CallRail's /calls/timeseries.json. One request for a trend line instead of client-side bucketing.

• compare_periods

  Compare current N-day window vs the previous N-day window.

• create_companywrite action

  Create a new company (client) under the account.

• create_form_submissionwrite action

  Manually create a form submission (e.g. backfill an offline lead).

• create_notificationwrite action

  Create a notification rule (who gets pinged on which event).

• create_outbound_callwrite action

  Place an outbound call. THIS ACTUALLY DIALS REAL PHONES.

• create_tagwrite action

  Create a new tag, scoped to one company or to the whole account.

• create_trackerwrite action
• create_userwrite action

  Invite a new user. CallRail emails them an account-creation link.

• delete_companywrite action

  Soft-delete a company. Status flips to 'disabled', records retained.

• delete_notificationwrite action

  Delete a notification rule. The rule is gone. To keep but mute it, prefer `update_notification(send_email=False, send_desktop=False, send_push=False)`.

• delete_tagwrite action

  Delete a tag definition from the account. Removes it from any calls or form submissions that had it applied.

• delete_trackerwrite action

  Delete (disable) a tracker. Soft-removes it from active trackers; the tracker keeps its call history but stops receiving new calls. The underlying phone number is released.

• delete_userwrite action

  Remove a user from the account.

• form_stats

  Server-side form-submission totals via /forms/summary.json.

• get_call

  Get full detail for a specific call.

• get_call_page_views

  Get the visitor's page-view history behind a call: which pages they browsed (with timestamps) before and around dialing. Pairs with `call_eligibility_check` for conversion debugging: shows the actual session journey that led to the call.

• get_call_recording

  Get the recording URL for a call. CallRail documents the link as good for at least 24 hours but not guaranteed forever; HIPAA accounts receive a temporary URL that expires in about 24 hours. Play or download it promptly rather than storing the link.

• get_call_transcript

  Get the transcript and conversation-intelligence fields for a call.

• get_company

  Get full detail for one company.

• get_form_submission

  Get full detail for one form submission, including all submitted field data.

• get_integration

  Get full detail for one integration.

• get_lead_timeline

  Get a lead's full cross-channel activity timeline: every call, form submission, and text thread from that person in one response, with first-touch/last-touch attribution.

• get_sms_thread

  Get one SMS thread's lead-management record (notes, value, tags, lead_qualification, state). For the message transcript itself use `get_text_message` with the conversation id.

• get_tag

  Get full detail for one tag.

• get_text_message

  Get full detail for one SMS conversation, including all messages.

• get_tracker

  Get full detail for a specific tracker.

• get_user

  Get full detail for one user on the account.

• list_accounts

  List CallRail accounts accessible to this API key.

• list_calls
• list_companies

  List companies (client businesses) under a CallRail account.

• list_form_submissions

  List form submissions captured by CallRail's Form Tracking. Paginated. Filterable by company and date window.

• list_integrations

  List integrations attached to one company (GMB, Google Ads, Facebook, Slack, Webhooks, etc.).

• list_leads

  List leads (unique people) across calls, forms, and texts.

• list_notifications

  List notification rules on the account.

• list_sms_threads

  List SMS threads. Unlike `list_text_messages` (conversation transcripts), threads carry the lead-management surface: `notes`, `value`, `tags`, `lead_qualification`, `state`. Threads are UPDATABLE via `update_sms_thread`.

• list_tags

  List all tags in the account, or filtered to one company.

• list_text_messages

  List SMS/text message conversations sent to or received via CallRail trackers. Paginated. Filterable by company and date window.

• list_trackers

  List tracking phone numbers (trackers). Each tracker maps a pool of phone numbers to a traffic source (Google Ads, Organic, Direct, etc.).

• list_users

  List users on the account. Paginated.

• remove_call_tagswrite action

  Remove specific tags from a call (case-sensitive on tag name).

• search_calls_by_number

  Find calls from/to a specific phone number. Matches on the last 10 digits of the stored `customer_phone_number` so any format works.

• spam_detector

  Heuristically identify likely-spam calls and (optionally) tag them.

• update_callwrite action

  Update an existing call: notes, tags, spam flag, customer name, lead status.

• update_companywrite action

  Update mutable settings on a company. Pass None to leave a field unchanged; only fields with explicit values are sent in the PUT body.

• update_form_submissionwrite action

  Update an existing form submission: note, tags, value, lead status.

• update_notificationwrite action

  Update a notification rule. Pass None to leave a field unchanged; only fields with explicit values are sent in the PUT body.

• update_sms_threadwrite action

  Update an SMS thread's lead-management fields. This is the texting equivalent of `update_call`. Closes the gap where texting leads couldn't be tagged / noted / qualified via API.

• update_tagwrite action

  Rename, recolor, disable or re-enable a tag.

• update_trackerwrite action

  Update a tracker's mutable settings: name, whisper, SMS, swap targets, campaign name, and the basic call flow (destination, recording, greeting).

• update_userwrite action

  Update a user's name or company access. Pass None to leave unchanged.

• usage_summary

  Per-company cost-attribution summary for the current cycle.

• Code scan5 source files scanned25/25
• –Live reliabilityno gateway calls yet and no remote to proben/a
• –Tool poisoningtools not inspected (local package is not executed); not countedn/a
• Auth qualitystatic API keys via environment variables6/15
• Maintenancelast push 6 days ago15/15
• Maintainer identityregistry namespace matches repository owner6/10

Safety score

80/100

higher than 60% of 48,243 servers

Tools

57

the typical server has 7

Tools that change things

39%

typical: 0%. Fewer write tools means less an agent can break

GitHub stars

2

more than 75% of 28,706 servers

Downloads a week

227

more than 77% of 12,306 servers with a package

CallRail MCP: common questions

Is CallRail MCP server safe?

Mostly: it is graded B (80/100). Read the CallRail MCP safety report

How do I install CallRail MCP?

It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.

Does CallRail MCP need an API key?

Yes. The registry entry asks for CALLRAIL_API_KEY.

Is CallRail MCP maintained?

The last commit was 27 days ago (2026-10-09). The latest release is v1.3.1.

How does CallRail MCP compare with other MCP servers?

safety score 80/100 (higher than 60% of 48,243 servers); tools 57 (the typical server has 7); tools that change things 39% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.