Skip to main content
Glama
@kanopi/callrail-mcp

@kanopi/callrail-mcp

by kanopi

@kanopi/callrail-mcp

A Model Context Protocol (MCP) server for the CallRail API v3. It exposes CallRail's call tracking, text messaging, form submissions, trackers, companies, tags and more as MCP tools so an LLM client (Claude Desktop, Claude Code, etc.) can read from and write to your CallRail account.

  • Transport: stdio (local)

  • Auth: CallRail API v3 key via environment variable

  • Coverage: 34 tools across 11 resources (full read + write)

Prerequisites

  • Node.js 18+ (uses the global fetch)

  • A CallRail API v3 key — in CallRail go to Settings → Integrations → API Keys → Create New API v3 Key. Keys are user-scoped; the server can only see what that user can.

Related MCP server: GoHighLevel MCP Server

Usage

No install needed — run the published package directly with npx:

npx -y @kanopi/callrail-mcp

npx fetches @kanopi/callrail-mcp and runs its callrail-mcp binary over stdio. This is what you point your MCP client at (see Connecting to a client).

Build from source (for development)

git clone <repo-url> && cd call-rail-mcp
npm install
npm run build

This compiles TypeScript to dist/. The entrypoint is dist/index.js.

Configuration

The server reads credentials from environment variables:

Variable

Required

Description

CALLRAIL_API_KEY

✅

Your CallRail API v3 key.

CALLRAIL_ACCOUNT_ID

optional

Default account id. When set, tools may omit account_id. Find it with the list_accounts tool.

CALLRAIL_BASE_URL

optional

Override the API base URL (default https://api.callrail.com/v3). Mainly for testing.

Copy .env.example to .env for local reference (the server reads from the process environment; your MCP client passes these in — see below).

Connecting to a client

Claude Code

claude mcp add callrail \
  --env CALLRAIL_API_KEY=your_api_key_here \
  --env CALLRAIL_ACCOUNT_ID=your_account_id \
  -- npx -y @kanopi/callrail-mcp

Claude Desktop / other clients (JSON config)

Add to the mcpServers block of the client's config (e.g. claude_desktop_config.json):

{
  "mcpServers": {
    "callrail": {
      "command": "npx",
      "args": ["-y", "@kanopi/callrail-mcp"],
      "env": {
        "CALLRAIL_API_KEY": "your_api_key_here",
        "CALLRAIL_ACCOUNT_ID": "your_account_id"
      }
    }
  }
}

To run a local checkout instead of the published package, point at the built entrypoint — "command": "node", "args": ["/absolute/path/to/call-rail-mcp/dist/index.js"] — or the TypeScript source via tsx: "command": "npx", "args": ["tsx", "/abs/path/src/index.ts"].

Tools

Write tools are prefixed with WRITE: in their descriptions and carry MCP annotations (readOnlyHint/destructiveHint) so clients can prompt for confirmation. Most tools accept an optional account_id that falls back to CALLRAIL_ACCOUNT_ID. List tools share common params: page, per_page (max 250), sort, order, search, date_range/start_date/ end_date, and fields for optional extra fields.

Resource

Tools

Accounts

list_accounts, get_account

Companies

list_companies, get_company, create_company ✏️, update_company ✏️, delete_company 🗑️

Calls

list_calls, get_call, create_outbound_call ✏️, update_call ✏️, get_calls_summary, get_calls_timeseries

Trackers

list_trackers, get_tracker, create_tracker ✏️, update_tracker ✏️, delete_tracker 🗑️

Text messages

list_conversations, get_conversation, send_text_message ✏️

Form submissions

list_form_submissions, get_form_submission, update_form_submission ✏️

Users

list_users, get_user

Tags

list_tags, create_tag ✏️, update_tag ✏️, delete_tag 🗑️

Integrations

list_integrations (per company)

Notifications

list_notifications

Outbound caller IDs

list_outbound_caller_ids, create_outbound_caller_id ✏️

✏️ = write (create/update) · 🗑️ = destructive (delete)

Notes & caveats

  • Premium data: transcription, sentiment, call summaries and highlights require a CallRail Premium Conversation Intelligence subscription. Request them via the fields argument on get_call / list_calls.

  • SMS compliance: outbound texts must include opt-out instructions; CallRail enforces this.

  • Rate limits: ~1,000 requests/hour by default. The server surfaces HTTP 429 (with Retry-After when provided) as a tool error rather than crashing.

  • Data retention: communication records are retained ~25 months; older date ranges error.

  • Pagination is manual: pass page to walk results; the server does not auto-page.

Development

npm run dev     # run from source with tsx
npm run build   # type-check + emit dist/
npm start       # run the built server

Project layout

src/
  index.ts            entrypoint (stdio transport)
  config.ts           env loading + validation
  client.ts           CallRail HTTP client (auth, query, errors, account resolution)
  types.ts            shared types + CallRailApiError
  tools/
    index.ts          registers all tools
    shared.ts         common zod params, response/error helpers, annotations
    <resource>.ts     one file per CallRail resource

License

MIT

Available Tools

34 tools
create_companyCreate company (write)B

WRITE: Create a new company in an account. Requires a name; other fields optional.

Inputs: name (required), time_zone, account_id, callscore_enabled, +2 more.

create_outbound_callCreate outbound call (write)C

WRITE: Place an outbound call that connects an agent number to a customer number.

Inputs: caller_id (required), company_id (required), agent_phone_number (required), customer_phone_number (required), +4 more.

create_outbound_caller_idCreate outbound caller ID (write)A

WRITE: Register a phone number as an outbound caller ID. CallRail sends a verification call/code to the number before it can be used.

Inputs: phone_number (required), account_id.

create_tagCreate tag (write)C

WRITE: Create a new tag in an account.

Inputs: name (required), color, tag_level, account_id, +1 more.

create_trackerCreate tracker (write)B

WRITE: Create a tracking number. type is source or session; provisions a number in the given company. Use a JSON object for source-specific config.

Inputs: name (required), type (required), company_id (required), destination_number (required), +6 more.

delete_companyDelete company (destructive)A
Destructive

WRITE/DESTRUCTIVE: Permanently delete a company. This cannot be undone.

Inputs: company_id (required), account_id.

delete_tagDelete tag (destructive)B
Destructive

WRITE/DESTRUCTIVE: Permanently delete a tag. This cannot be undone.

Inputs: tag_id (required), account_id.

delete_trackerDelete tracker (destructive)A
Destructive

WRITE/DESTRUCTIVE: Permanently delete a tracker. This cannot be undone.

Inputs: tracker_id (required), account_id.

get_accountGet accountA
Read-only

Retrieve details for a single CallRail account.

Inputs: fields, account_id.

get_callGet callA
Read-only

Retrieve a single call by id, optionally with extra fields (transcription, keywords, sentiment, etc — some require Premium Conversation Intelligence).

Inputs: call_id (required), fields, account_id.

get_calls_summaryGet calls summaryB
Read-only

Summarize call data grouped by a dimension (source, keywords, campaign, referrer, landing_page, or company).

Inputs: end_date, group_by, account_id, company_id, +2 more.

get_calls_timeseriesGet calls timeseriesA
Read-only

Retrieve call analytics grouped by a time interval.

Inputs: end_date, group_by, account_id, company_id, +2 more.

get_companyGet companyA
Read-only

Retrieve a single company by id.

Inputs: company_id (required), account_id.

get_conversationGet text conversationA
Read-only

Retrieve a single text conversation, including its messages.

Inputs: conversation_id (required), fields, account_id.

get_form_submissionGet form submissionA
Read-only

Retrieve a single form submission by id.

Inputs: form_submission_id (required), fields, account_id.

get_trackerGet trackerA
Read-only

Retrieve a single tracker by id.

Inputs: tracker_id (required), account_id.

get_userGet userA
Read-only

Retrieve a single user by id.

Inputs: user_id (required), account_id.

list_accountsList accountsA
Read-only

List all CallRail accounts accessible to the API key. Use this to discover account ids.

Inputs: page, sort, order, per_page, +1 more.

list_callsList callsB
Read-only

List calls in an account with filtering, sorting, search and field selection.

Inputs: page, sort, tags, order, +11 more.

list_companiesList companiesB
Read-only

List companies in an account. Companies contain trackers and calls.

Inputs: page, sort, order, search, +3 more.

list_conversationsList text conversationsB
Read-only

List SMS/MMS text-message conversations in an account.

Inputs: page, sort, order, fields, +7 more.

list_form_submissionsList form submissionsB
Read-only

List form submissions captured in an account.

Inputs: page, sort, order, fields, +7 more.

list_integrationsList integrationsB
Read-only

List third-party integrations configured for a company in an account.

Inputs: company_id (required), page, per_page, account_id.

list_notificationsList notificationsC
Read-only

List notification settings configured for the account's users.

Inputs: page, per_page, account_id.

list_outbound_caller_idsList outbound caller IDsA
Read-only

List verified phone numbers usable as outbound caller IDs.

Inputs: page, per_page, account_id.

list_tagsList tagsA
Read-only

List tags defined in an account.

Inputs: page, per_page, account_id, company_id.

list_trackersList trackersC
Read-only

List tracking numbers (trackers) in an account.

Inputs: page, sort, order, search, +4 more.

list_usersList usersB
Read-only

List users in an account, with their company associations.

Inputs: page, sort, order, search, +3 more.

send_text_messageSend text message (write)A

WRITE: Send an SMS/MMS reply in a conversation. Outbound texts must include opt-out instructions per compliance rules. Provide media_url for MMS.

Inputs: content (required), conversation_id (required), media_url, account_id.

update_callUpdate call (write)B

WRITE: Update a call's notes, tags, lead status, customer name, value, or spam flag.

Inputs: call_id (required), spam, tags, notes, +5 more.

update_companyUpdate company (write)C

WRITE: Update fields on an existing company.

Inputs: company_id (required), name, time_zone, account_id, +3 more.

update_form_submissionUpdate form submission (write)B

WRITE: Update a form submission's notes, tags, lead status, value, or spam flag.

Inputs: form_submission_id (required), spam, tags, notes, +4 more.

update_tagUpdate tag (write)A

WRITE: Update an existing tag's name or color.

Inputs: tag_id (required), name, color, account_id.

update_trackerUpdate tracker (write)C

WRITE: Update fields on an existing tracker.

Inputs: tracker_id (required), name, source, disabled, +4 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.5/5.0

    Scored across 34 tools

    Disambiguation5/5

    Each tool targets a distinct resource and operation (e.g., company, call, tag, tracker). Even with 34 tools, there is no ambiguity; every tool has a clear, separate purpose.

    Naming Consistency5/5

    All tools follow a consistent 'verb_noun' pattern (e.g., create_company, list_calls, delete_tracker). Plural for list operations is consistent. No mixing of styles.

    Tool Count2/5

    34 tools is excessive; it exceeds the 25+ threshold for 'too many' and feels overwhelming. While the domain is broad, many tools could be consolidated or are unnecessary for an agent.

    Completeness5/5

    The toolset covers full CRUD for core resources (companies, tags, trackers) and provides list/get/create/update for relevant entities (calls, conversations, form submissions). Missing delete for calls and some minor operations, but overall the surface is comprehensive.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • F
      license
      Not graded
      quality
      C
      maintenance
      MCP server for Bvoip / 1Stream that exposes call-reporting, phone-status, and CRM-extension-mapping endpoints as MCP tools.
      -