Skip to main content
Glama
Hyros MCP

Hyros MCP

by HyrosOG

Hyros MCP Server

npm version License: MIT

Connect Hyros advertising attribution to AI assistants (Claude, Cursor, etc.) through the Model Context Protocol. Ask questions about your leads, sales, calls, subscriptions, and ad performance — and let the AI pull the data and run the reports for you.

61 tools covering leads, sales, calls, subscriptions, products, custom costs, carts, webhooks, URL rules, attribution reports (including ROAS and marginal CAC curve), ad management, async request tracking, and smart analytics. Targets Hyros REST API v1.41 and Webhooks v1.1. Agencies can run every tool against a connected client account via the optional accessible_account_id argument.

Built by Carlos Aragon.


You only need the Claude app (desktop or web). Nothing to install. No terminal. No Node.js. No config files.

  1. Open Claude → Settings → Connectors.

  2. Click Add custom connector.

  3. Paste this address and click Add:

    https://hyrosmcp.callwithcarlos.com/mcp
  4. A small page opens in your browser asking for your Hyros API key. Get it from Hyros → Settings → Integrations → API, paste it, and click Connect.

  5. Done ✅ — Hyros now shows up in Claude's tools. Try asking "What was my revenue today?"

That's the whole thing. Your key is checked the moment you paste it (so you know right away if it's wrong) and is stored encrypted on the server — it never lives on your computer, and you never edit any files.

Controlling what the AI can do (permissions)

Inside Claude, every tool can be set to:

  • Always allow — runs without asking (great for read-only reports and lookups)

  • Ask every time — Claude asks for your approval before each use

  • Blocked — never runs

You'll find these in the connector's settings in Claude. The tools that change data (create a lead, refund an order, etc.) are flagged so Claude asks first by default.

If a tool answers "Unauthorized"

Hyros API keys carry roles, and several endpoints need a role that is not on a key by default. When a key lacks the role the API replies 401 Unauthorized with no explanation of which role is missing, so the tool looks broken when the key is simply too narrow.

Verified against Hyros API v1.39 on 2026-08-04, these tools need extra roles:

Tools

Needs a role for

hyros_get_products, hyros_update_product, hyros_delete_product

Products

hyros_get_custom_costs, hyros_update_custom_cost, hyros_delete_custom_cost

Custom costs

hyros_get_carts

Carts

hyros_get_webhook_subscriptions, hyros_create_webhook_subscription, hyros_delete_webhook_subscription

Webhooks

hyros_update_source, hyros_delete_source

Sources (write)

hyros_delete_lead

Leads (delete)

Fix it in the Hyros app under Settings → API Keys by enabling the roles on your key, or issue a key with full roles. A wrong key reads differently: it returns a JSON body containing Api key not valid, while a missing role returns the bare text Unauthorized.

Agency-level keys are a separate limit. They authenticate on hyros_get_user_info but return 401 on every data endpoint, and the API has no way to scope a request to a client account. Use a key from the client account itself.

How it works (the short version)

You (Claude app)  ──▶  hyrosmcp.callwithcarlos.com  ──▶  Hyros API
                       (a secure hosted server)

There's a small server running in the cloud (on Cloudflare) that speaks to Hyros on your behalf. When you connect, it asks for your API key once, verifies it, and keeps it encrypted. From then on, when you ask Claude a question, Claude talks to that server, which fetches your real Hyros data and hands it back. You don't host or maintain anything.

For developers / self-hosters: the server lives in worker/ and runs on Cloudflare Workers. See DEPLOY.md to deploy your own copy.


Related MCP server: Google Analytics MCP Server

Alternative — Run it locally (advanced / developers)

Prefer to run the server on your own machine instead of using the hosted one? This uses the npm package and Claude Desktop's local config. You'll need Node.js 18+.

Step 1 — Install the package

Open a terminal and run:

npm install -g hyros-mcp

This works on Windows, macOS, and Linux.

Step 2 — Add to Claude Desktop

Open your Claude Desktop config file:

  • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json

  • Windows: %APPDATA%\Claude\claude_desktop_config.json

Add this (replace your_api_key_here with your key from Hyros → Settings → Integrations → API):

{
  "mcpServers": {
    "hyros": {
      "command": "hyros-mcp",
      "args": [],
      "env": {
        "HYROS_API_KEY": "your_api_key_here"
      }
    }
  }
}

Step 3 — Restart Claude Desktop

Close and reopen Claude Desktop. That's it — you're ready to use it.


Claude Code (CLI)

npm install -g hyros-mcp
claude mcp add hyros -e HYROS_API_KEY=your_api_key_here -- hyros-mcp

Cursor / Windsurf

Same config as Claude Desktop above — add it to your MCP settings file.


Troubleshooting

Remote connector (the 60-second install)

"That key didn't work" when you paste it — The key is wrong, expired, or lacks permissions. Copy it again, exactly, from Hyros → Settings → Integrations → API. The page tells you immediately if it's valid.

Hyros tools don't appear in Claude — Make sure you finished the browser step (pasting the key and clicking Connect). Re-open Settings → Connectors and confirm Hyros is listed and connected.

Need to change your API key later — Just disconnect and re-add the connector (or reconnect) and paste the new key. Nothing else to update.

Local install

"401 Unauthorized" — Your API key is wrong, missing, or lacks the role the endpoint needs. Make sure:

  1. HYROS_API_KEY is inside the env block

  2. The key is copied exactly from Hyros → Settings → Integrations → API

  3. You restarted Claude Desktop after saving the config

  4. The key has the role that tool needs, if only some tools fail — see If a tool answers "Unauthorized"

MCP tools not showing up — Restart Claude Desktop. The config is only read at startup.

"command not found: hyros-mcp" — The global install didn't complete. Run npm install -g hyros-mcp again and make sure npm's global bin folder is in your PATH.

Configuration

Variable

Required

Description

HYROS_API_KEY

Yes

Your Hyros API key (Settings > Integrations > API)

HYROS_BASE_URL

No

API base URL (default: https://api.hyros.com/v1)

Tools

Read Operations (26)

Tool

Description

hyros_get_user_info

Account information

hyros_get_leads

Search and retrieve leads

hyros_get_lead_journey

Full customer journey with attribution

hyros_get_sales

Query sales records

hyros_get_calls

Query call records

hyros_get_subscriptions

Query subscriptions

hyros_get_clicks

Get click history for a lead

hyros_get_tags

List all tags (deprecated, use hyros_get_tags_count)

hyros_get_tags_count

List tags with lead counts, paginated

hyros_get_stages

List funnel stages

hyros_get_domains

List verified domains

hyros_get_sources

Get ad sources and campaigns

hyros_get_ads

Get ads by platform

hyros_get_keywords

Get keywords by ad group

hyros_get_tracking_script

Get tracking script HTML

hyros_get_attribution_report

Attribution metrics (ROAS, ROI, CPA, etc.)

hyros_get_ad_account_report

Account-level attribution metrics

hyros_get_ad_accounts

List connected ad accounts and their ids

hyros_get_products

List catalog products with price and cost of goods

hyros_get_custom_costs

List custom costs active in a date window

hyros_get_carts

List carts, filterable to abandoned ones

hyros_get_webhook_subscriptions

List configured webhook subscriptions

hyros_get_roas_report

ROAS of one ad, ad set, campaign, or account (cash-based, break-even 1.0)

hyros_get_marginal_cac_curve

Cost of the next customer at each spend level, with saturation point

hyros_get_url_rules

List URL rules, or fetch one by its ur-<id>

hyros_get_request_status

Status of an async write (PENDING / PROCESSED / FAILED)

Write Operations (30)

Tool

Description

hyros_create_lead

Create a new lead

hyros_update_lead

Update lead data and tags

hyros_create_order

Register a sale/order

hyros_update_order

Replace an order's items and fees (shipping, taxes, discount, hardCost)

hyros_refund_order

Process a refund

hyros_update_sale

Update sale status

hyros_delete_sale

Delete a sale

hyros_create_call

Register a call event

hyros_update_call

Update call qualification

hyros_delete_call

Delete a call

hyros_create_subscription

Create subscription

hyros_update_subscription

Update subscription

hyros_create_source

Create ad source

hyros_create_custom_cost

Add custom ad cost

hyros_create_product

Create product

hyros_create_cart

Track a shopping cart

hyros_update_cart

Update pending cart

hyros_create_click

Manually record a click

hyros_delete_lead

Erase a lead and its PII (GDPR / CCPA)

hyros_update_product

Update price, SKU, cost of goods, category

hyros_delete_product

Delete a product

hyros_update_custom_cost

Replace a custom cost

hyros_delete_custom_cost

Delete a custom cost

hyros_update_source

Rename or reclassify an ad source

hyros_delete_source

Delete an ad source

hyros_create_webhook_subscription

Subscribe an endpoint to Hyros events

hyros_delete_webhook_subscription

Delete a webhook subscription

hyros_create_url_rule

Create a URL rule that tags matching traffic

hyros_update_url_rule

Replace a URL rule (full replacement; omitted fields are cleared)

hyros_delete_url_rule

Delete a URL rule

Agency access

Every tool accepts an optional accessible_account_id argument. Agencies pass the accountId listed under accessibleAccounts in hyros_get_user_info to run the call against that client account; the API rejects any target that is not an approved connected account.

Smart Analytics (5)

Tool

Description

hyros_daily_summary

Today's performance: revenue, leads, calls, subscriptions

hyros_best_performers

Top ads/campaigns ranked by any metric

hyros_compare_periods

Compare metrics between two date ranges

hyros_funnel_overview

Full funnel from leads to revenue

hyros_subscription_health

MRR, ARR, churn, and subscription breakdown

Resources

URI

Description

hyros://account

Account information

hyros://tags

Available tags

hyros://stages

Funnel stages

Prompts

Name

Description

daily_briefing

Daily performance summary

campaign_analysis

Campaign performance analysis

lead_lookup

Investigate a specific lead

Example Questions

Once connected, you can ask things like:

  • "What was my revenue today?"

  • "Show me my best performing Facebook ads this month"

  • "Compare last week vs this week"

  • "Look up the customer journey for john@example.com"

  • "What's my current MRR?"

  • "Which campaigns have the highest ROAS?"

  • "Create a lead with email test@example.com and tag them as VIP"

  • "Which leads were updated since yesterday?"

  • "Show me carts abandoned in the last week"

  • "Remove the trial tag from john@example.com"

  • "Which custom costs are still running with no end date?"

Security

  • HTTPS-only connections (API key never sent over plaintext)

  • Domain-restricted to *.hyros.com (prevents SSRF)

  • Runtime input validation on all tool parameters

  • Request timeouts (30s) with retry logic

  • Client-side rate limiting (25 req/sec)

  • Path traversal prevention on URL parameters

Development

git clone https://github.com/CachoMX/Hyros-MCP.git
cd Hyros-MCP
npm install
cp .env.example .env    # Add your API key
npm run build           # Compile TypeScript (local/stdio version)
npm run dev             # Run in development mode
npm test                # Run tests

Remote server (Cloudflare Worker)

The hosted connector lives in worker/ and reuses all the tool logic in src/. It adds a Streamable HTTP transport plus an OAuth layer that collects each user's Hyros API key on a single-field page.

npm run worker:check    # Validate the bundle (wrangler dry-run, no deploy)
npm run worker:dev      # Local dev server (wrangler dev)
npm run worker:deploy   # Deploy to Cloudflare

Full operator instructions — Cloudflare token scopes, KV setup, custom domain — are in DEPLOY.md.

License

MIT - Carlos Aragon

Available Tools

53 tools
hyros_best_performersBest PerformersA
Read-only

Get the top performing ads/campaigns ranked by revenue, ROAS, ROI, etc. for a given date range. Requires an ad account ID and the level of analysis. Use hyros_get_sources to find your ad account IDs first. Perfect for "what are my best ads this week?" or "which campaigns have the highest ROAS this month?"

Inputs: level (required), endDate (required), startDate (required), adAccountId (required), +4 more.

hyros_compare_periodsCompare PeriodsA
Read-only

Compare ad performance metrics between two date ranges using attribution data. Requires an ad account ID and level. Returns revenue, cost, ROAS, sales, leads, and percentage changes. Perfect for "compare this week vs last week".

Inputs: level (required), adAccountId (required), period1EndDate (required), period2EndDate (required), +4 more.

hyros_create_callCreate CallB

Register a call event in Hyros. Used to track sales calls and attribute them to ad sources.

Inputs: name (required), date, email, stage, +7 more.

hyros_create_cartCreate CartA

Create a new cart in Hyros to track a shopping cart before it converts to an order. Use this when a lead adds items to a cart so Hyros can attribute the eventual purchase.

Inputs: items (required), date, email, cartId, +5 more.

hyros_create_clickCreate ClickA

Manually track a click event in Hyros for attribution purposes. Use when you need to create a click record that was not automatically tracked by the Hyros tracking script.

Inputs: referrerUrl (required), ip, tag, date, +11 more.

hyros_create_custom_costAdd Custom CostA

Add a custom ad cost in Hyros. Use this to track offline ad spend, influencer payments, or any cost not automatically tracked by Hyros integrations.

Inputs: cost (required), tags (required), frequency (required), startDate (required), +2 more.

hyros_create_leadCreate LeadA

Create a new lead in Hyros. At least one of email or phoneNumbers must be provided. If the email already exists, the lead will be updated with any new information provided.

Inputs: tags, email, stage, leadIps, +4 more.

hyros_create_orderCreate OrderA

Register a new sale/order in Hyros. This creates a sale record attributed to a lead.

Inputs: items (required), date, email, stage, +6 more.

hyros_create_productCreate ProductA

Create a new product in Hyros for sale attribution.

Inputs: name (required), price (required), category, packages.

hyros_create_sourceCreate Ad SourceB

Create a new ad source/traffic source in Hyros for tracking custom marketing channels.

Inputs: name (required), goal, category, accountId, +7 more.

hyros_create_subscriptionCreate SubscriptionB

Register a new subscription in Hyros for recurring revenue tracking.

Inputs: price (required), status (required), startDate (required), periodicity (required), +10 more.

hyros_create_webhook_subscriptionCreate Webhook SubscriptionA

Subscribe an endpoint to Hyros events. Returns a secretKey used to verify the X-Hyros-Signature header on delivered payloads; the key is shown only once, so surface it to the user immediately.

Inputs: name (required), targetUrl (required), eventTypes (required).

hyros_daily_summaryDaily SummaryA
Read-only

Get a complete performance summary for today (or a specific date). Returns total revenue from sales, number of new leads, call team performance, and subscription stats. Perfect for answering "how did we do today?" or "what is today's revenue?"

Inputs: date, timezone.

hyros_delete_callDelete CallB
Destructive

Permanently delete a call record from Hyros.

Inputs: callId (required).

hyros_delete_custom_costDelete Custom CostA
DestructiveIdempotent

Delete a custom cost. Use this to stop a mistaken or open-ended recurring cost from skewing profit and ROAS on every report.

Inputs: id (required).

hyros_delete_leadDelete LeadA
DestructiveIdempotent

Permanently erase a lead and its personal data, found by email or id. Use this for GDPR or CCPA right-to-erasure requests. Cannot be undone.

Inputs: id, email.

hyros_delete_productDelete ProductA
DestructiveIdempotent

Delete a product from the Hyros catalog. Use this to remove one created by mistake or by a duplicate import.

Inputs: id (required).

hyros_delete_saleDelete SaleA
Destructive

Permanently delete a sale record from Hyros. This action cannot be undone.

Inputs: saleId (required).

hyros_delete_sourceDelete Ad SourceA
DestructiveIdempotent

Delete an ad source by its tag. Use this to clean up sources created by mistake that clutter every attribution pull. Setting isDisregard via hyros_update_source is the reversible alternative.

Inputs: tag (required).

hyros_delete_webhook_subscriptionDelete Webhook SubscriptionA
DestructiveIdempotent

Delete a webhook subscription by its externalId. Deliveries stop immediately and the secretKey is not recoverable afterwards.

Inputs: externalId (required).

hyros_funnel_overviewFunnel OverviewA
Read-only

Get a complete funnel overview showing the full customer journey from clicks to revenue for a date range. Shows: total leads, calls (with qualification rate), sales (with amounts), subscriptions, and calculates conversion rates between each stage.

Inputs: toDate (required), fromDate (required), currency.

hyros_get_ad_account_reportAd Account ReportA
Read-only

Get attribution metrics grouped by ad account. Provide the ad account ID(s) to get aggregated performance across all campaigns/ads in those accounts.

Inputs: ids (required), fields (required), endDate (required), startDate (required), +12 more.

hyros_get_ad_accountsList Ad AccountsA
Read-only

List the ad accounts connected to Hyros with their id, name, and platform. Call this first to discover the ids that hyros_get_ad_account_report and hyros_get_attribution_report need.

Inputs: ids, fields.

hyros_get_adsGet AdsA
Read-only

Get ads from a specific advertising platform tracked in Hyros.

Inputs: integrationType (required), pageId, pageSize, adSourceIds.

hyros_get_attribution_reportAttribution ReportA
Read-only

Get detailed attribution metrics for specific ads, campaigns, or ad sets. Use this to answer "what is my ROAS?", "how much did I earn vs spend?", "which ad has the best ROI?". Requires specifying the level (e.g., facebook_adset, google_campaign) and the IDs to query. Use hyros_get_sources to find source IDs first.

Inputs: ids (required), level (required), fields (required), endDate (required), +11 more.

hyros_get_callsGet CallsB
Read-only

Retrieve call records from Hyros. Useful for businesses with phone sales teams. Filter by date, email, qualification status, or call state.

Inputs: ids, state, emails, pageId, +6 more.

hyros_get_cartsGet CartsA
Read-only

List shopping carts filtered by purchase status, lead, or date. Set purchased=false to find abandoned carts for a recovery campaign.

Inputs: emails, pageId, toDate, leadIds, +3 more.

hyros_get_clicksGet ClicksA
Read-only

Get click tracking data for a specific lead. Shows the ad clicks and traffic sources that led a customer to your site.

Inputs: email, leadId, pageId, toDate, +2 more.

hyros_get_custom_costsGet Custom CostsA
Read-only

List custom costs (agency fees, tool subscriptions, offline spend) active in a date window. Use this to audit costs that skew profit and ROAS, especially recurring ones left without an end date.

Inputs: ids, pageId, toDate, fromDate, +1 more.

hyros_get_domainsGet DomainsA
Read-only

Get all verified domains in your Hyros account.

Inputs: no named parameters.

hyros_get_keywordsGet KeywordsB
Read-only

Get keywords for a specific ad group (mainly for Google Ads keyword tracking).

Inputs: adgroupId (required).

hyros_get_lead_journeyLead JourneyA
Read-only

Get the complete customer journey for one or more leads: sales, calls, carts, subscriptions, linked leads, and ad attribution sources. Use this to understand what ads drove a customer to convert. Accepts emails directly, so no lookup round-trip is needed.

Inputs: ids, emails, includeEvents.

hyros_get_leadsGet LeadsA
Read-only

Search and retrieve leads from Hyros. Filter by email, phone, tag, stage, join date, or last-updated date. Use this to find customers, check their tags and current funnel stage, and sync changes into another system.

Inputs: ids, tags, stage, emails, +7 more.

hyros_get_productsGet ProductsA
Read-only

List products in the Hyros catalog with price, cost of goods, and category. Use this before creating a product to avoid duplicates, or to audit the pricing that feeds profit and ROAS reporting.

Inputs: ids, name, tags, pageId, +2 more.

hyros_get_salesGet SalesA
Read-only

Retrieve sales records filtered by date, email, lead ID, product tag, or recurring/refund status. Use this to check revenue, see what products sold, and track refunds.

Inputs: ids, emails, pageId, toDate, +6 more.

hyros_get_sourcesGet Ad SourcesC
Read-only

Get ad sources and campaigns tracked in Hyros. Sources represent your marketing channels, campaigns, and ad sets.

Inputs: pageId, pageSize, adSourceIds, includeOrganic, +2 more.

hyros_get_stagesGet Funnel StagesA
Read-only

Get all lead funnel stages configured in your Hyros account (e.g., MQL, SQL, Opportunity, Customer).

Inputs: name, pageId, pageSize.

hyros_get_subscriptionsGet SubscriptionsA
Read-only

Retrieve subscription records. Use this to check MRR, see active subscribers, find churned customers, and track subscription status changes.

Inputs: ids, emails, pageId, states, +5 more.

hyros_get_tagsGet TagsA
Read-only

Get all available tags in your Hyros account as a flat list. Tags starting with $ are product tags, @ are source tags, ! are action tags. Deprecated by Hyros in favour of hyros_get_tags_count, which adds lead counts and pagination.

Inputs: no named parameters.

hyros_get_tags_countTag CountsA
Read-only

List tags along with how many leads carry each one. Use this instead of hyros_get_tags when you need sizes, pagination, or to look up one tag.

Inputs: name, pageId, pageSize.

hyros_get_tracking_scriptGet Tracking ScriptB
Read-only

Get the Hyros tracking script to install on your website.

Inputs: domain.

hyros_get_user_infoAccount InfoA
Read-only

Get the authenticated Hyros account information including email, timezone, and currency settings.

Inputs: no named parameters.

hyros_get_webhook_subscriptionsWebhook SubscriptionsA
Read-only

List the webhook subscriptions configured on the account, with their target URL, subscribed events, and delivery state. Use this to audit which systems receive Hyros events.

Inputs: no named parameters.

hyros_refund_orderRefund OrderA
Destructive

Process a refund for an existing order in Hyros.

Inputs: orderId (required), refundedAmount.

hyros_subscription_healthSubscription HealthB
Read-only

Get a health report for your subscription business. Shows active count, MRR (monthly recurring revenue), trial count, churn (canceled this period), past due, and other subscription statuses. Perfect for "what is my MRR?" or "how many active subscribers do I have?"

Inputs: toDate, currency, fromDate.

hyros_update_callUpdate CallB
Idempotent

Update the qualification status or state of existing call records.

Inputs: name (required), ids, state, externalIds, +1 more.

hyros_update_cartUpdate CartA
Idempotent

Update an existing cart in Hyros. Use this to modify items or customer info on a pending cart before it converts to an order.

Inputs: items (required), cartId (required), date, email, +5 more.

hyros_update_custom_costUpdate Custom CostA
Idempotent

Update a custom cost. The whole cost is replaced, so send every field, not only the ones changing. Use this to fix a wrong amount or to close an open-ended recurring cost by setting endDate.

Inputs: id (required), cost (required), tags (required), frequency (required), +3 more.

hyros_update_leadUpdate LeadA
Idempotent

Update an existing lead in Hyros. At least one search parameter (searchEmail, searchId, or searchPhone) must be provided. Can update email, name, tags, IPs, phone numbers, and funnel stage.

Inputs: tags, email, leadIps, lastName, +9 more.

hyros_update_productUpdate ProductA
Idempotent

Update a product's price, SKU, cost of goods, or category. Cost of goods feeds profit and ROAS reporting, so correcting it changes historical margins.

Inputs: id (required), sku, name, price, +3 more.

hyros_update_saleUpdate SaleA
Idempotent

Update one or more sale records in Hyros. Can mark sales as recurring, refunded, or update refund amounts.

Inputs: ids (required), isRefunded, refundedDate, refundedAmount, +1 more.

hyros_update_sourceUpdate Ad SourceA
Idempotent

Update an ad source: rename it, change its category, goal or traffic source, or toggle its organic and disregarded flags. Sources are addressed by tag, not by id.

Inputs: tag (required), goal, name, category, +3 more.

hyros_update_subscriptionUpdate SubscriptionB
Idempotent

Update existing subscription records. Can change status, price, dates, and cancellation.

Inputs: ids (required), price (required), name, status, +4 more.

Tool Schema Changelog

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

Loading tool schema changelog…

    TDQS

    B3.4/5.0

    Scored across 53 tools

    Disambiguation3/5

    Most tools have distinct resource-action purposes, but there are several overlap issues. hyros_get_tags and hyros_get_tags_count serve the same purpose (one deprecated), and multiple reporting tools (hyros_get_attribution_report, hyros_best_performers, hyros_compare_periods) have similar parameters and outputs, making it easy for an agent to misselect.

    Naming Consistency4/5

    The majority of tools follow a consistent hyros_verb_noun pattern (e.g., hyros_get_leads, hyros_create_order, hyros_delete_sale). However, a few tools break this pattern with noun-phrase names like hyros_daily_summary, hyros_best_performers, and hyros_compare_periods, which is a minor deviation.

    Tool Count2/5

    With 53 tools, the server is well beyond the 'heavy' threshold and feels bloated. While the domain is complex, several tools are redundant or could be consolidated (e.g., hyros_get_tags vs hyros_get_tags_count), and the sheer number will likely overwhelm agents.

    Completeness4/5

    The tool surface is quite comprehensive, covering CRUD operations for leads, sales, calls, subscriptions, carts, products, sources, custom costs, and webhooks, plus a range of attribution and analytics reports. Minor gaps exist, such as no update/delete for clicks and no direct delete for carts, but core workflows are well supported.

    Maintenance

    ActivityNo data
    ResponsivenessSyncing

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      An implementation of Model Context Protocol (MCP) that allows users to interact with TripleWhale's e-commerce analytics platform using natural language queries through Claude Desktop.
      106 npm
      7
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Connects Google Analytics 4 data to Claude, Cursor and other MCP clients, enabling natural language queries of website traffic, user behavior, and analytics data with access to 200+ GA4 dimensions and metrics.
      12
      2,370 PyPI
      244
      MIT
    • A
      license
      B
      quality
      F
      maintenance
      Connects AI assistants like Claude to Sealmetrics analytics data, enabling natural language queries for traffic analysis, conversions, marketing performance, ROAS tracking, and funnel analysis.
      8
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Connect AI assistants to live Meta Ads, GA4, and Google Search Console data. 100% local, credentials machine-locked and encrypted. Supports Claude Desktop, Cursor, Windsurf, Cline, and more.
      1
      MIT