ChartMogul

Name: ChartMogul MCP Server
Availability: InStock
Author: ChartMogul

HIPAA CompliantSOC2 ReadyISO 27001 Ready

Analytics76 tools

Query MRR, ARR, churn, retention, cohorts, customers and sales pipeline from your AI assistant. 76 tools, read-only access, works with any MCP client.

Verified connector

Listed by Anthropic as a partner connector in its Connectors Directory.

Connection checked by Agentman on 18 August 2026.

Anthropic states this reflects the level of review a connector received, not a security audit.

Connect ChartMogul via MCP

https://mcp.chartmogul.com/

Works in any MCP-compatible client. In Agentman Studio it is one click — no config file to edit.

Use in Agentman

Connect ChartMogul once and your agents call these tools on their own — on a schedule, in a workflow, with nobody at the keyboard.

Open in Agentman Studio

ChartMogul Tools & Capabilities (76)

ARPA

ASP

CMRR

CMRR_movements

LTV

MRR_and_ARR

MRR_movements

account_retention_for_benchmarks

benchmarks

benchmarks_metadata

benchmarks_segmented

cash_flow

cash_flow_analytics

cash_flow_summary

cfl_reference

cfl_reference_for_plan_filters

churn_summary

churned_subscribers

cohorts

cohorts_summary

currency_fluctuation

currency_fluctuation_summary

customer_count

free_and_paid_subscriber_movements

free_trial_customers

get_current_account

lead_and_trial_trends

leads

leads_and_free_trials_summary

list_account_team_members

list_contacts

list_customer_custom_attributes

list_customer_notes

list_customer_subscriptions

list_customer_timeline_events

list_data_sources

list_emails

list_invoices

list_line_items

list_opportunities

list_plan_groups

list_plans

list_reference_data

list_sales_pipeline_stages

list_sales_pipelines

list_saved_charts_and_lists

list_segments

list_subscription_events

list_tags

list_tasks

list_transactions

maps

maps_churn_ltv

metrics_by_plan

metrics_by_region

metrics_for_top_10_countries

net_MRR

net_MRR_summary

non_subscription_customer_summary

non_subscription_customer_trends

non_subscription_customers

paid_subscriber_movements

retention

sales_cycle

sales_cycle_length_trends

sales_cycle_summary

scenario_analysis

search_all

search_custom_attributes

search_customers

subscriber_movement_summary

subscribers

subscription_movements

subscription_quantity

trial_conversion_trends

trial_conversions

Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.

Limits

One scope, mcp, with no read/write split and no per-resource narrowing. The consent screen offers nothing to decline. Access control lives in ChartMogul's role model and in the account-wide security toggle, not in the OAuth grant.
MCP access is on by default. An Admin or Owner has to visit Settings → Admin → Security to turn it off. Accounts that would rather opt in than opt out should check that toggle before anyone connects.
The connector reads your CRM, not just your charts. Twenty-four of the 76 tools list customer records, and list_customer_notes and list_emails reach call logs and email threads attached to accounts. Weigh that separately from the metrics.
Two roles are excluded. ChartMogul's roles article documents Lite and CRM-only team members, and neither appears in the four roles its MCP article permits.
One tool is admin-gated. list_account_team_members is marked available to admins only, so results differ by who authorised the connection.
We could not read tool schemas or safety annotations. The endpoint requires authentication, so the 76 count and the tool names are the directory's, and parameter-level detail is not published here. What we did read is the auth posture, both OAuth descriptors and the vendor's tool table.
The endpoint publishes no resource_metadata pointer. ChartMogul's 401 challenge omits the parameter that normally names the protected-resource descriptor. The descriptor exists anyway, at the conventional path — a client that follows only the header would conclude there was none.
ChartMogul publishes no MCP-specific rate limit. Its REST API documents 40 requests per second and a maximum of 20 parallel connections, but that page does not state whether the MCP server shares that budget. Treat the API figures as context, not as the connector's limit.
The connector delivers your data, not advice. It returns metrics and records from your own account. Interpreting them, and any decision that follows, sits with you.

Frequently asked questions

No. ChartMogul's documentation states the server uses OAuth 2.0 and connects to your account with read-only access, and that data is only retrieved in response to your queries. All 75 tools in its published table read or search. Nothing in the 76-name directory listing carries a create, update, delete, import or merge verb.

Owner, Admin, Staff or Read-only. ChartMogul's MCP article names exactly those four team member roles. Its roles article lists two more, Lite and CRM-only, which are not on that list. Managing the MCP setting itself is narrower still and requires Admin or Owner.

All of them, including Free. ChartMogul's plan comparison table marks the row API, MCP, and standard CSV exports as included on Free, Starter, Pro and Enterprise. The Free plan tracks up to 120,000 dollars of ARR, so the constraint is account size rather than the connector itself.

In Settings, Admin, Security, toggle Allow MCP server access. ChartMogul documents that MCP access is enabled by default and that managing this setting requires an Admin or Owner role. Individual users can also revoke a connection from their AI assistant's connector settings at any time.

Run claude mcp add --transport http chartmogul https://mcp.chartmogul.com in a terminal. ChartMogul publishes that exact command. Then type /mcp inside the Claude Code session and complete the OAuth flow against your ChartMogul account. The same URL works in any MCP-compatible client that supports streamable HTTP.

CMRR is Committed Monthly Recurring Revenue, which ChartMogul describes as a forward-looking projection of MRR based on scheduled subscription changes. MRR measures revenue already billed, so it trails; CMRR incorporates future committed changes, so it leads. The connector exposes both as separate tools.