Skip to main content
Glama
Sign In

CallRail MCP by InsightfulPipe

by com.insightfulpipe
OverviewDiscussionsAdmin

Server Details

Hosted CallRail MCP server for Claude, ChatGPT and Cursor, with each action switched per account.

Ownership verified
Status
Healthy
Uptime
100.0% over the last 24 hours
OAuth
Works in Glama
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
Repository
Insightful-Pipe/callrail-mcp-server
GitHub Stars
0
ChatGPT
–
Claude
–

TDQS

A3.7/5.0

Scored across 4 tools

Disambiguation3/5

query_data and execute_action are both labeled as the final workflow step and require the exact same prerequisite calls, making it unclear when to use one versus the other. The read-versus-write distinction is implied but not stated, while query_contexts and prompts_menu are reasonably distinct.

Naming Consistency4/5

Most tool names follow a snake_case verb_noun pattern (query_contexts, query_data, execute_action), but prompts_menu breaks the verb_noun convention. The deviation is minor and the names remain readable.

Tool Count5/5

Four tools is well within the typical 3-15 range, and each appears to serve a clear workflow role: context lookup, data querying, action execution, and prompt catalog browsing.

Completeness4/5

The surface covers metadata discovery, data querying, action execution, and prompt browsing, which broadly supports the CallRail workflow. Minor gaps exist, such as prompt execution or creation, but generic query and action tools likely cover most domain operations.

Available Tools

4 tools
execute_actionCallRail Execute ActionA
Destructive
Inspect

Execute CallRail action (Step 3 (FINAL) of workflow).

REQUIRED: Complete these steps first using query_contexts:

  1. request='accounts' - Get workspace_id, brand_id AND available_actions

  2. request='actions_details' with actions=['xxxxxx', 'xxxxxx', 'xxxxxx'] - Get detailed body structure for specific action(s) using actions from available_actions

IMPORTANT: Always call step 2 to see the exact body structure before executing.

Rely on info from steps 1-2 to construct the action body. Follow the schema exactly.

Inputs: body (required). Returns: object

prompts_menuCallRail PromptsA
Read-only
Inspect

Browse the CallRail prompt catalog.

  1. request='menu' – List public/system prompts (optionally pass workspace_id + prompt_type).

  2. request='prompt_details' – Fetch prompt body by prompt_id. Set is_custom=True + workspace_id for workspace prompts.

Inputs: request (required), is_custom, prompt_id, prompt_type, +1 more. Returns: object

query_contextsCallRail Setup HelperA
Read-only
Inspect

Helper for planning InsightfulPipe CallRail data queries.

Step 1: request='accounts' – Retrieve workspace_id, brand_id, other source metadata, AND available_actions (all tables you can query).

Step 2: request='actions_details' with actions=['xxxxxx', 'xxxxxx', 'xxxxxx'] – REQUIRED before querying. Replace with actions from available_actions to get the exact request body, required identifiers, fields, time ranges, and notes for each action.

Optional: request='available_actions' – Standalone call to list all available tables/actions (already included in accounts response).

Optional: request='brands' with brand_id + workspace_id to pull brand guidelines.

Inputs: request (required), actions, brand_id, platform, +1 more. Returns: object

query_dataCallRail Data QueryB
Read-only
Inspect

Query CallRail data (Step 3 (FINAL) of workflow).

REQUIRED: Complete these steps first using query_contexts:

  1. request='accounts' - Get workspace_id, brand_id AND available_actions

  2. request='actions_details' with actions=['xxxxxx', 'xxxxxx', 'xxxxxx'] - Get detailed body structure for specific action(s) using actions from available_actions

IMPORTANT: Always call step 2 to see the exact body structure before querying.

Rely on info from steps 1-2 to construct the query body. Follow the schema exactly.

Inputs: body (required). Returns: object

Tool Schema Changelog

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

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    • Follow Up Boss Connector

      thehillisrockin
      F
      license
      Not graded
      quality
      D
      maintenance
      A self-hosted MCP server that connects a Follow Up Boss CRM account to Claude, enabling CRM operations through natural language via 25 curated tools and a raw API tool.
      -

    • ghl-mcp-remote

      jamersoncalixto
      F
      license
      Not graded
      quality
      D
      maintenance
      Remote MCP server for GoHighLevel that enables multi-tenant agency access via OAuth, allowing Claude or ChatGPT to use GHL tools through natural language.
      -
    Try in Browser
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    Glama MCP Gateway

    Add one secure layer between your agents and this server.

    Resources