MCP App Store
by KeenEthics
HYROS icon

HYROS MCP Server for Claude and ChatGPT

By Hyros

Overview

Hyros tracks every ad click, lead, and sale, so you can see which campaigns, ads, and keywords actually produce revenue. This connector brings that data into Claude. Ask in plain language and get answers from your live Hyros account: • "Which Meta campaigns had the best ROAS last month?" • "What were my best performing ads last month?" • "Where did last week's revenue actually come from?" • "Show me an overview of the last 7 days" Claude can pull attribution reports, spend and ROAS by campaign or ad set, lead and customer journeys, revenue and LTV breakdowns, and call and booking data, then chart it, summarize it or drop it into the doc you're already writing. Built for media buyers, agencies, and growth teams who spend their days reconciling ad platform numbers against what actually hit the bank account. Requires an active Hyros account. You connect with your Hyros login, and Claude only sees data that account already has access to.

How to connect

  1. Claude: Open the HYROS listing in the Claude connectors directory and choose Connect. Claude listing HYROS exposes 60 tools here.
  2. ChatGPT: Open the HYROS listing in the ChatGPT app directory and choose Connect. ChatGPT listing HYROS exposes 79 tools here.

Tools

hyros_add_dashboard_repository_collaborator

ChatGPT
Invite a GitHub account to push to the account's dashboard repository. The account gets access once it accepts the invitation. Look the account up with hyros_get_github_user first and confirm with the user it is the right person, since the invitation is sent right away. Returns the account's GitHub profile and the link to accept the invitation; invited is false, with no link, when the account already had access. To take an invitation back, use hyros_remove_dashboard_repository_collaborator. Fails while the account's dashboard is not set up yet.

hyros_add_tags_to_leads

ChatGPT
Apply the given tags to every lead selected by id and/or email in one call. An email may match several leads, and every match is tagged. A sale tag matching a product's tag generates a sale for each lead that did not already carry it, so in bulk this multiplies across the selection. Use it to tag an audience without one request per lead. Processed asynchronously; the change is typically visible within a few minutes, longer for a large selection. The response carries a requestId; check the outcome with hyros_get_request_status.

hyros_admin_find_user_product_information

ChatGPT
Admin-only tool: Retrieve the product information of the users with the given emails.

hyros_assert_script_presence_on_domain

ChatGPT
Fetch the given URLs and report, per URL, whether the HYROS tracking script is present and correctly installed. Use it to verify an installation, or to find the pages whose missing script explains untracked traffic. The script counts as installed whether it loads from the account's default tracking host or from any of its tracking domains, so the tracking domain does not need to be passed. Maximum of 3 urls. SCRIPT_NOT_FOUND is the only outcome that means the script is missing; TIMEOUT_ERROR (page did not load in time) and the rest are inconclusive, and a TIMEOUT_ERROR is worth retrying or repeating on a lighter page of the same domain.

hyros_check_tracking_parameters_for_integrations

ChatGPT
Check the tracking parameters of the account's ad spend integrations for one advertising channel type, over the integrations seen in the last hour, and report per ad whether the parameters Hyros needs are present and well-formed. Use it to find ads whose links are missing tracking parameters and would therefore lose attribution.

hyros_create_call

ChatGPT
Record a booked call for a lead, with its date, product and qualification state. Creates the lead first if no lead exists for the given email. Use it to feed calls from a booking or CRM system into Hyros so they are attributed to the traffic source that produced them. Processed asynchronously; the change is typically visible within ~10 seconds. The response carries a requestId; check the outcome with hyros_get_request_status.

hyros_create_cart

ChatGPT
Record a cart and its items for a lead. Creates the lead first if no lead exists for the given email; a cart sent with no email or phone number is recorded without one. Use it to feed checkout or cart-creation events from a store into Hyros so later purchases and abandonments are attributed. Processed asynchronously; the change is typically visible within ~10 seconds. The response carries a requestId; check the outcome with hyros_get_request_status.

hyros_create_click

ChatGPT
Record a click for a visitor session. An email on the click identifies the lead, creating it when it does not exist yet. Use it to report traffic that the Hyros tracking script cannot observe itself, such as clicks captured server-side or by another system. Processed asynchronously; the change is typically visible within ~10 seconds. The response carries a requestId; check the outcome with hyros_get_request_status.

hyros_create_custom_cost

ChatGPT
Record a cost that Hyros does not import from an ad platform, with its amount, frequency and active date range. Use it to include spend such as agency retainers, tooling or offline media in profit and ROI reporting. Processed asynchronously; the change is typically visible within ~10 seconds. The response carries a requestId; check the outcome with hyros_get_request_status.

hyros_create_lead

ChatGPT
Create a lead with its contact details and tags, or update the matching lead when one already exists for the email. On an existing lead, phoneNumbers replaces the stored numbers, so omitting it deletes them; prefer hyros_update_lead to modify an existing lead. If an applied tag matches a product's tag, a sale is generated for the lead, unless the lead already carried that tag. Use it to bring contacts from a form, CRM or list into Hyros so their activity is tracked and attributed. Processed asynchronously; the change is typically visible within ~10 seconds. The response carries a requestId; check the outcome with hyros_get_request_status.

hyros_create_order

ChatGPT
Record a purchase with its line items, prices and currency, generating one sale per item. Creates the lead first if no lead exists for the given email. Use it to send orders from a store, checkout or payment processor into Hyros so revenue is attributed to the traffic that produced it. Processed asynchronously; the change is typically visible within ~10 seconds. The response carries a requestId; check the outcome with hyros_get_request_status.

hyros_create_product

ChatGPT
Add a product to the account with its name, price and category; its tag is derived from the name. Use it so sales carrying that product can be recognised and reported per product, for example before importing orders for a newly launched offer. Processed asynchronously; the change is typically visible within ~10 seconds. The response carries a requestId; check the outcome with hyros_get_request_status.

hyros_create_source

ChatGPT
Create a source link so traffic and sales arriving through it are attributed to it. Sources can be organic, non-organic, or tied to an ad platform such as Google or Facebook. Use it to start tracking a new traffic source, campaign or placement. Processed asynchronously; the change is typically visible within ~10 seconds. The response carries a requestId; check the outcome with hyros_get_request_status.

hyros_create_subscription

ChatGPT
Record a subscription for a lead, with its product, price, billing period and state. Creates the lead first if no lead exists for the given email. Use it to bring recurring plans from a billing system into Hyros so recurring revenue is attributed to the traffic that produced it. Processed asynchronously; the change is typically visible within ~10 seconds. The response carries a requestId; check the outcome with hyros_get_request_status.

hyros_create_url_rule

ChatGPT
Create a simple URL rule that tags leads whose tracked URL matches the given words. The tag prefix sets the flavor: '!' action tag, '@' source tag, '$' sale tag, '#' subscription tag. Use it to bulk-create URL-based tagging, e.g. for dynamically generated webinar or booking URLs.

hyros_delete_call

ChatGPT
Delete a booked call by its call id, removing it from call reporting and from its lead's journey. Use it to remove a call that was recorded in error or duplicated. Processed asynchronously; the change is typically visible within ~5 minutes. The response carries a requestId; check the outcome with hyros_get_request_status.

hyros_delete_custom_cost

ChatGPT
Delete a custom cost by its id, removing it from profit and ROI reporting. Use it to remove a cost entered in error or one that no longer applies. The change applies immediately.

hyros_delete_lead

ChatGPT
Permanently erase a lead, identified by lead id or email: personal data is redacted, phone numbers, sales and tracking data are deleted, and subscriptions are cancelled. The lead's email address and phone numbers are also blacklisted, so later events carrying them are discarded instead of re-creating the lead. Use it for data-erasure requests such as GDPR or CCPA. This cannot be undone. The erasure applies immediately; the lead takes up to ~5 minutes to disappear from lead retrieval. The response carries a requestId; check the outcome with hyros_get_request_status.

hyros_delete_product

ChatGPT
Delete a product by its id. Use it to retire a product from the catalogue so it is no longer offered for attribution of new sales. The change applies immediately.

hyros_delete_sale

ChatGPT
Delete a sale by its sale id, removing it from revenue and attribution reporting. Use it to remove a sale that was reported in error or duplicated. Processed asynchronously; the change is typically visible within ~5 minutes. The response carries a requestId; check the outcome with hyros_get_request_status.

hyros_delete_source

ChatGPT
Delete a source link by its tag. The source is soft-deleted and stops appearing in attribution. Use it to retire a tracked link that is no longer in use. The deletion applies immediately; the source takes up to ~5 minutes to disappear from source retrieval.

hyros_delete_url_rule

ChatGPT
Delete a URL rule by its id, so it no longer tags matching traffic. Use it to retire a rule the account no longer needs.

hyros_generate_public_report

ChatGPT
Start generating a report over the account's attribution and revenue data, grouped by source, ad, creative, keyword, geography, referrer, cohort, lead journey or sale item, over a date range. Use it to answer questions the individual retrieval tools cannot, such as which sources drove the most profit, which keywords earned their spend, or which products sold best. Pass 'timeZone' as the requester's UTC offset (+HH:mm / -HH:mm) whenever it is known, so that relative ranges such as 'yesterday' resolve in their day rather than the account's. Returns a report id immediately; the report itself is computed asynchronously, so read it with 'hyros_poll_public_report_result'.

hyros_get_account_tracking_script

ChatGPT
Retrieve the account's default HYROS tracking script, ready to install on a site. Use it when the snippet is needed as-is, with no domain override and no tracking options.

hyros_get_active_external_integrations

ChatGPT
Retrieve the account's active integrations of one external platform type, with their configuration. Use it to confirm whether a platform is connected and how, for example when ad spend or sales from that platform are missing. The configuration carries the settings that govern what the integration imports, never its credentials.

hyros_get_ad_account_report

ChatGPT
Retrieve the attribution report aggregated per ad account for a date range, rather than per campaign, ad set or ad. Use it for account-level spend and revenue totals, or to compare whole ad accounts against each other; prefer it over hyros_get_attribution_report when you only need totals, since it sums all sources in one call with no pagination. Ad account ids are the id values of the connected ad accounts listing.

hyros_get_ad_accounts

ChatGPT
Retrieve the ad accounts connected to the Hyros account, with the ad platform and ad account id of each. Use it to see which ad platforms are connected, or to obtain the ad account ids that the ad account attribution report takes as input. When ids are provided only the matching ad accounts are returned; otherwise every connected ad account is returned.

hyros_get_ads

ChatGPT
Search and retrieve the ad-level sources of the account, filtering by ad spend type and id. Use it when reporting needs individual ads rather than the source links above them. Results are paginated.

hyros_get_attribution_report

ChatGPT
Retrieve the ads attribution report for a date range, broken down by campaign, ad set or ad. Returns the ad spend, revenue and conversion metrics Hyros attributes to each ad source under the requested attribution model. With isAdAccountId it pages over the account's sources, oldest first unless newestFirst is set. With leadStage every attributed lead and sale is filtered to the given account lead stages, matched on the lead's current stage, so leads, sales, revenue and ROAS all narrow while ad spend does not. That is how ads are ranked by a funnel outcome such as approvals or booked calls, and the stage names come from hyros_get_stages. Use it for ad performance questions such as which campaigns or ad sets are profitable, or to compare how the same period looks under different attribution models.

hyros_get_calls

ChatGPT
Search and retrieve booked calls by creation date, last-modified date, lead email, lead id, product tag, call id, qualification state or qualification stage. Use it to review call volume and outcomes over a period, or to find the calls belonging to a specific lead. Filter by updatedFromDate to fetch only what changed since a previous sync instead of the whole window. Results are paginated.

hyros_get_calls_aggregation

ChatGPT
Counts the calls from a search by grouping them according to the tag of their first or last source, or their qualification stage. It is used to determine how many calls there are per source or per stage; for example, to break down the booked calls of a period between paid and organic traffic, or across the stages of the call funnel. The response contains three numbers that answer different questions: "groups" field shows how the calls that have a value for the selected attribute are distributed; "remainingCount" field indicates how many calls were left out because their group did not fit within "groupsLimit" request param, so increasing this limit by that number is enough to retrieve all remaining groups; and "totalCount" field indicates how many calls matched the search. A call has at most one value of each attribute, so it belongs to at most one group, and a call without a value (no source, or no qualification stage yet) belongs to none: totalCount minus the sum of the groups is the number of calls with no value for that attribute. When grouping by FIRST_SOURCE_TAG or LAST_SOURCE_TAG, each group also carries a "details" object whose "source" describes the source link: name, organic and disregarded flags, traffic source, category, goal, and ad source (platform and ad account). This makes it possible to calculate paid vs. organic traffic, as well as calls by traffic source or ad account, from this call. FIRST_SOURCE_TAG and LAST_SOURCE_TAG group by the source stored on each call, not by an attribution model, so counts can differ from FIRST_CLICK and LAST_CLICK reports.

hyros_get_carts

ChatGPT
Search and retrieve carts by creation date, purchased state, lead email or lead id. Each cart includes its items and the lead that owns it. Use it for abandoned-cart work, for example carts created more than a couple of hours ago that still have no orderId. When both emails and leadIds are given they are combined with AND. Results are paginated.

hyros_get_conversion_paths

ChatGPT
Retrieves the conversions of one type (sales, calls or leads) in a date range together with the ordered source touches each one was attributed with, so an external attribution model can be computed over them.

hyros_get_conversion_targets

ChatGPT
Admin-only tool: Retrieve the account's active ad sets, ad groups or campaigns on one ad platform, live from the platform, with what each one optimizes on and whether Hyros sends conversions to it. Use it to tell how much the account's advertising relies on the conversions Hyros sends versus the client's own tracking.

hyros_get_custom_costs

ChatGPT
Retrieve the manually entered costs of the account. A cost matches the requested window when its active range overlaps it. Use it to review costs that are not imported from an ad platform, or to obtain the id needed to update or delete one. Results are paginated.

hyros_get_dashboard_repository_collaborators

ChatGPT
List the GitHub accounts that can push to the account's dashboard repository and the invitations still waiting to be accepted, each with the link to accept it and whether it expired. Fails while the account's dashboard is not set up yet.

hyros_get_dashboard_repository_token

ChatGPT
Create a GitHub access token that can clone, pull and push the account's dashboard repository, valid for one hour. Returns the token, its expiry and the repository's HTTPS clone URL. Git authenticates with the username x-access-token and the token as password. Request a new token when the current one expires or git reports an authentication error. Fails while the account's dashboard is not set up yet.

hyros_get_domains

ChatGPT
Retrieve the domains verified for the account. Use it to confirm which domains Hyros accepts for tracking, or to pick the domain to request a tracking script for.

hyros_get_github_user

ChatGPT
Look a GitHub account up by its username and return its public profile: login, display name and avatar URL. Use it to show the user whose account it is before inviting it to the dashboard repository. Fails when no GitHub user has that name, or it belongs to an organization, which cannot be invited.

hyros_get_integrations_types

ChatGPT
Retrieve the external integration types Hyros supports, each with its identifier and display name, or only the ad-spend subset when adspendOnly is set. Use it to obtain the valid type value that the integration tools take as input. Lists the supported types themselves, not the account's connections.

hyros_get_keywords

ChatGPT
Retrieve the keywords tracked by the account, or only those of one Google ad group when adgroupId is supplied. Use it for keyword-level search reporting, or to confirm which keywords Hyros has ingested from a connected Google Ads account. Results are paginated.

hyros_get_lead_clicks

ChatGPT
Retrieve the clicks recorded for one or many leads, identified by a single lead id, a list of lead ids or a list of emails, each click with its URL and ad source. Exactly one of those three selectors is accepted, and each click carries the id and email of the lead it belongs to. Use it to see the traffic that brought a lead in, or to find clicks whose URL has no matching source link and is therefore untracked. Results are paginated.

hyros_get_lead_journey

ChatGPT
Retrieve the click and attribution journey of one or more leads, identified by lead ID and/or email: sales, calls, carts, subscriptions and linked leads. Use it to reconstruct everything Hyros knows about a person's path from first click to purchase.

hyros_get_lead_stage_rules

ChatGPT
Retrieve the lead stage rules of the account's active integrations, as the integration's Lead Stage Rules settings show them: for each rule, the stage it applies, the integration events that apply it (for HighLevel, the contact tags), and whether it is active. Use it to confirm which event feeds which stage. When useDefaultLeadStages is true the rules are not consulted: each event applies the stage named after it. Saving a rule does not backfill: it applies its stage to events received from then on, so a lead that already carried the tag or event gets the stage only when a new event for it arrives (for HighLevel, any tag update on the contact, which carries all its tags).

hyros_get_leads

ChatGPT
Search and retrieve leads by join date, last-modified date, email, phone number, lead id, current stage, tags or the date a tag was applied. Use it to look up a specific person, to list leads that entered or changed within a period, to report on who was tagged during a period, or to obtain the lead ids other lead tools take as input. Results are paginated.

hyros_get_leads_aggregation

ChatGPT
Counts the leads from a search by grouping them according to an attribute, which can be a tag, the current stage, or the tag of the first or last source. It is used to determine how many leads there are rather than which leads they are; for example, to understand how leads are distributed across stages, which tags are most frequently used, or where leads from a given period came from. The response contains three numbers that answer different questions: "groups" field shows how the leads that have a value for the selected attribute are distributed; "remainingCount" field indicates how many leads were left out because their group did not fit within "groupsLimit" request param, so increasing this limit by that number is enough to retrieve all remaining groups; and "totalCount" field indicates how many leads matched the search. The groups should not be summed to obtain a total, since a lead without the attribute does not belong to any group, while a lead with multiple values can belong to more than one group.

hyros_get_marginal_cac_curve

ChatGPT
Compute how the cost of acquiring the next customer changes at every daily spend level for a single ad, ad set, campaign or ad account, from the account's own spend history. Returns the curve points (average and marginal CAC per spend level), the saturation point past which the next dollar costs more than the CAC ceiling, and the ceiling used. Customers are attributed under the first-click model with rebills included, so values differ from last-click reports such as hyros_get_roas_report; pass attributionModel to measure under last-click instead, which turns it into a closing-cost curve for retargeting and bottom-of-funnel entities. Use it to decide how far an entity's daily budget can scale before it stops paying for itself; use hyros_get_roas_report to judge past profitability at the current spend level.

hyros_get_offline_conversion_delivery

ChatGPT
Admin-only tool: Report whether HYROS sent the account's offline conversions to its ad platforms. Per integration that sends them: how many conversions were sent (accepted by the platform), failed and discarded, when the latest successful and failed sends happened, and the 10 most frequent failure reasons, as conversion state codes or the platform's own message when no code describes it. A failure without a code shows as NO_INFO or that message, where the Events manager may show the state of the sale instead. The counts are the ones of the Events manager and of the agency "Server events" card; conversions still waiting to be sent are not counted. HYROS-side delivery only: it does not tell whether the platform later attributed a conversion. To check whether offline conversions are switched on and where they are sent, use hyros_get_offline_conversions_config; its entries match these on 'platform' and 'integrationId'. Pass productId to read a customer's account.

hyros_get_offline_conversions_config

ChatGPT
Admin-only tool: Retrieve whether the account sends offline conversions to each ad platform, one entry per integration. 'status' is ON, OFF (switched off), NOT_CONFIGURED (no integration, or a Meta or TikTok integration with no pixel) or CONNECTED_WITH_ERRORS, with the cause in 'errorReason'. Each entry carries the destination ('pixelId' for Meta and TikTok, 'businessId' for Meta) and the HYROS events mapped to platform event names in 'events'. Use it to confirm whether offline conversions are live for a platform before investigating missing conversions on the platform side. For how many conversions were sent or failed, when, and why, use hyros_get_offline_conversion_delivery.

hyros_get_products

ChatGPT
Search and retrieve products by name, tag, category or recurrence. Use it to see the product catalogue Hyros attributes sales against, or to obtain the id needed to update or delete a product. Results are paginated.

hyros_get_request_status

ChatGPT
Check the outcome of a write that is processed asynchronously, using the requestId the write returned. 'PENDING' means the write has not been confirmed yet, and is never a reason to resend it; 'PROCESSED' means it completed, and carries a 'result' holding the resource as its own retrieval tool returns it, as it stood when the write completed, for the writes that produce a readable one; 'FAILED' carries an 'errorMessage' explaining why. Poll this instead of resending the write, which would duplicate it. Statuses are kept for 2 hours; wait a few seconds between polls.

hyros_get_roas_report

ChatGPT
Retrieve the ROAS of a single ad, ad set, campaign or ad account for a date range, from the cash Hyros attributes to it rather than from platform-reported conversions. Returns one row with roas, which is revenue over spend and so breaks even at 1.0, plus new_customers_roas, revenue including subscription rebills, cost, and the gap against what the platform reported. Use it to judge whether one entity is profitable; use hyros_get_attribution_report to compare several, to pick metrics, or to break a period down by date.

hyros_get_rules

ChatGPT
Retrieve the account's rules of one type: URL rules, lead stage rules, or sale and call conversion rules, each in the same structure with what triggers it (condition) and what it does (action). Use it to audit how the account tags traffic, moves leads between stages and sends conversions to ad platforms, or to compare the conversion rules of one ad platform by priority. A conversion rule whose condition.status is INVALID never sends conversions. Use small pages, and narrow by date when you can. Results are paginated.

hyros_get_sales

ChatGPT
Search and retrieve sales by creation date, last-modified date, lead email, lead id, product tag, sale id, recurrence or refunded state. Each sale carries its attributed first and last source. Use it for revenue reporting, or to find sales whose attribution is missing because both sources are empty. Filter by updatedFromDate to fetch only what changed since a previous sync instead of the whole window. fromDate/toDate always bound when the sale was made, never when it was refunded, so refunded sales over a range is not the same count as refunds issued in it, each sale's own refundDate answers the second. Results are paginated.

hyros_get_sales_aggregation

ChatGPT
Counts the sales from a search by grouping them according to the tag of their first or last source. It is used to determine how many sales there are per source; for example, to break down the sales of a period between paid and organic traffic. The response contains three numbers that answer different questions: "groups" field shows how the sales that have a value for the selected attribute are distributed; "remainingCount" field indicates how many sales were left out because their group did not fit within "groupsLimit" request param, so increasing this limit by that number is enough to retrieve all remaining groups; and "totalCount" field indicates how many sales matched the search. A sale has at most one source of each kind, so it belongs to at most one group, and a sale without a source belongs to none: totalCount minus the sum of the groups is the number of sales with no source of that kind. Each group also carries a "details" object with two parts: "source" describes the source link (name, organic and disregarded flags, traffic source, category, goal, and ad source with platform and ad account), and "revenue" is the sum of the stable USD price of the sales counted in the group, with its currency. This makes it possible to calculate paid vs. organic traffic, and revenue as well as sales by traffic source or ad account, from this call. FIRST_SOURCE_TAG and LAST_SOURCE_TAG group by the source stored on each sale, not by an attribution model, so counts can differ from FIRST_CLICK and LAST_CLICK reports.

hyros_get_sources

ChatGPT
Search and retrieve the source links of the account, filtering by name or tag, by organic and disregarded status, or by ad spend type and id. A source link is the tracked link Hyros attributes traffic and sales to. Use it to audit which links are tracked, or to find the tag needed to update or delete one. To check whether one specific source exists, filter by its name or tag instead of paging through the whole account. Results are paginated.

hyros_get_stages

ChatGPT
Retrieve the lead stages defined for the account, each with a count of leads in it. Without stageFromDate/stageToDate the count is the leads whose current stage it is; with them it is the leads the stage was applied to inside that period, which is what answers questions like how many leads entered a stage this week. The two counts are not comparable: applications accumulate, so a lead that moved between stages inside the period is counted under both. Use it to see the funnel Hyros tracks leads through, or to obtain the stage names that lead retrieval and the ads attribution report filter on. Results are paginated.

hyros_get_subscriptions

ChatGPT
Search and retrieve subscriptions by start and end date, lead email, lead id, product tag, subscription id or state. Use it for recurring-revenue reporting, such as which subscriptions are active, cancelled or churned in a period. Results are paginated.

hyros_get_tags

ChatGPT
Retrieve the names of every tag defined in the account, as a flat list without lead counts, filtering or pagination. Use it when only the tag names are needed. Superseded by hyros_get_tags_count, which returns the same tags together with the number of leads carrying each one and supports filtering by name and pagination.

hyros_get_tags_count

ChatGPT
Retrieve the tags defined in the account together with the number of leads carrying each one, filtering by name and paginating the results. A lead holding several tags is counted once under each of them. Use it to see how the audience is segmented, or to find the tag that identifies a product or campaign.

hyros_get_tracking_script

ChatGPT
Retrieve the Hyros tracking script to install on a site, optionally for a specific verified domain and with single-page-app tracking, previous-URL handling or iframe embedding enabled. Without a domain the account's default script is returned. Use it to obtain the snippet to install, or to regenerate it with different options. Supplying deleteTrackingScriptParams also stores that choice as the account's tracking preference.

hyros_get_tracking_script_with_custom_domain

ChatGPT
Retrieve the account's HYROS tracking script rewritten to load from a custom domain. Use it when tracking must be served from the customer's own domain, for example to survive tracking blockers.

hyros_get_url_rule

ChatGPT
Retrieve a single URL rule by its id, with its name, tag, matching words and flavor. Returns nothing when no rule has that id.

hyros_get_url_rules

ChatGPT
Retrieve the account's URL rules, each with its name, tag, matching words and flavor. Use it to see which URL-based tagging rules exist, or to obtain the id needed to update or delete one. Results are paginated.

hyros_get_user_info

ChatGPT
Retrieve the account's profile, its connected accounts and its true-tracking configuration. 'allowedAccounts' lists the accounts that have been granted access over this one, typically the agency managing it. 'accessibleAccounts' lists the accounts this one has been granted access over (for an agency, its client accounts). Each entry has an 'accountId' to pass as 'accessible_account_id' on other tools, a 'status' (only APPROVED accounts can be operated on), and the 'companyName', 'firstName'/'lastName' and 'email' to match an account referred to by name.

hyros_poll_public_report_result

ChatGPT
Read the status of a report started with 'hyros_generate_public_report', and its rows once the status is SUCCESSFUL. Poll again while the status is IN_PROGRESS. Returns every row by default; pass 'pageSize' to read a wide report a page at a time, and compare against 'totalRows', which always reports the size of the whole report. A report that could not be generated comes back FAILED, and one that was generated too long ago comes back EXPIRED. Both could carry a 'message' explaining what happened, written for the person who asked: relay it to them rather than paraphrasing it, since it is often something only they can act on, such as a plan that does not cover the report or a filter that has to be narrowed. Both statuses are final for that report id — generate the report again, once the message has been acted on.

hyros_refund_order

ChatGPT
Refund an order by its order id and recompute the lead's income. Without refundedAmount the whole order is refunded; otherwise the amount is split across the order's sales in proportion to their price. Use it to reflect a refund or chargeback so revenue and ROI reporting exclude it. Processed asynchronously; the change is typically visible within ~5 minutes. The response carries a requestId; check the outcome with hyros_get_request_status.

hyros_remove_dashboard_repository_collaborator

ChatGPT
Take a GitHub account's access to the account's dashboard repository away, cancelling its invitation if it was not accepted yet. Fails while the account's dashboard is not set up yet.

hyros_search_hyros_docs

ChatGPT
Retrieve the official HYROS documentation for setting up or integrating an external platform, such as Shopify, Facebook or Google Ads, returning the guide's content and a link to it. Use it for questions about how to install or configure an integration. Returns a not-found message when no guide exists for the platform.

hyros_update_call

ChatGPT
Update the state of one or more existing calls, identified by their call ids. Use it to move calls to a new qualification state as they progress, for example after a call is held or marked as qualified. Processed asynchronously; the change is typically visible within ~5 minutes. The response carries a requestId; check the outcome with hyros_get_request_status.

hyros_update_cart

ChatGPT
Update an existing cart, identified by its cart id. Use it when the cart contents change before checkout. Processed asynchronously; the change is typically visible within ~5 minutes. The response carries a requestId; check the outcome with hyros_get_request_status.

hyros_update_custom_cost

ChatGPT
Replace a custom cost, identified by its id. Use it to correct the amount, frequency or date range of a previously recorded cost. The change applies immediately.

hyros_update_lead

ChatGPT
Update an existing lead's details, tags and stages. Tags managed by Hyros AIR cannot be removed: a request that tries is rejected without applying any change. Stages listed in removeLeadStages are taken off the lead, so a stage applied by mistake can be undone; the same stage cannot be applied and removed in one request. Use it to correct lead details or to move a lead between tag-driven segments. Processed asynchronously; the change is typically visible within ~5 minutes. The response carries a requestId; check the outcome with hyros_get_request_status.

hyros_update_order

ChatGPT
Update the line items of an existing order, identified by its order id, and optionally its order-level fields. Supplied items are matched against the order's existing sales by external id and then by name: matched sales are updated in place, items with no match create new sales, and existing sales with no matching item are soft-deleted. Use it when the contents or totals of an already reported order change. Processed asynchronously; the change is typically visible within ~5 minutes. The response carries a requestId; check the outcome with hyros_get_request_status.

hyros_update_product

ChatGPT
Update a product, identified by its id. Use it to correct a product's price, category, cost of goods or recurrence. The change applies immediately.

hyros_update_sale

ChatGPT
Update one or more existing sales, identified by their sale ids, including recurrence and refund state, refunded amount and refund date. Use it to correct sale data already in Hyros, or to mark sales as refunded without going through the order. Processed asynchronously; the change is typically visible within ~5 minutes. The response carries a requestId; check the outcome with hyros_get_request_status.

hyros_update_source

ChatGPT
Update an existing source link, identified by its tag. Editing a source re-attributes its associated sales in the background. Use it to correct a source's name, type or ad platform details. Processed asynchronously; the change is typically visible within ~5 minutes. The response carries a requestId; check the outcome with hyros_get_request_status.

hyros_update_subscription

ChatGPT
Update one or more existing subscriptions, identified by their subscription ids. Use it to reflect a change of state such as a cancellation or a pause, or to correct the price or billing dates of a subscription already in Hyros. Processed asynchronously; the change is typically visible within ~5 minutes. The response carries a requestId; check the outcome with hyros_get_request_status.

hyros_update_url_rule

ChatGPT
Update an existing URL rule, identified by its id. Only the fields sent are modified and anything omitted keeps its stored value, so a single option can be changed without reading the rule and sending it back whole.

hyros_assert_script_presence_on_domain

Claude

hyros_check_tracking_parameters_for_integrations

Claude

hyros_create_call

Claude

hyros_create_cart

Claude

hyros_create_click

Claude

hyros_create_conversion_definition

Claude

hyros_create_custom_conversion

Claude

hyros_create_custom_cost

Claude

hyros_create_lead

Claude

hyros_create_order

Claude

hyros_create_product

Claude

hyros_create_source

Claude

hyros_create_subscription

Claude

hyros_delete_call

Claude

hyros_delete_conversion_definition

Claude

hyros_delete_custom_cost

Claude

hyros_delete_lead

Claude

hyros_delete_product

Claude

hyros_delete_sale

Claude

hyros_delete_source

Claude

hyros_get_account_tracking_script

Claude

hyros_get_active_external_integrations

Claude

hyros_get_ad_account_report

Claude

hyros_get_ad_accounts

Claude

hyros_get_ads

Claude

hyros_get_attribution_report

Claude

hyros_get_calls

Claude

hyros_get_carts

Claude

hyros_get_conversion_definitions

Claude

hyros_get_custom_costs

Claude

hyros_get_domains

Claude

hyros_get_integrations_types

Claude

hyros_get_keywords

Claude

hyros_get_lead_clicks

Claude

hyros_get_lead_journey

Claude

hyros_get_leads

Claude

hyros_get_marginal_cac_curve

Claude

hyros_get_products

Claude

hyros_get_roas_report

Claude

hyros_get_sales

Claude

hyros_get_sources

Claude

hyros_get_stages

Claude

hyros_get_subscriptions

Claude

hyros_get_tags

Claude

hyros_get_tags_count

Claude

hyros_get_tracking_script

Claude

hyros_get_tracking_script_with_custom_domain

Claude

hyros_get_user_info

Claude

hyros_refund_order

Claude

hyros_search_hyros_docs

Claude

hyros_update_call

Claude

hyros_update_cart

Claude

hyros_update_conversion_definition

Claude

hyros_update_custom_cost

Claude

hyros_update_lead

Claude

hyros_update_order

Claude

hyros_update_product

Claude

hyros_update_sale

Claude

hyros_update_source

Claude

hyros_update_subscription

Claude

Similar Apps

Listed on MCP App Store

Listed on MCP App Store

Add this badge to your site or README. It links to this page.

HTML

<a href="https://mcp-app-store.keenethics-labs.com/app/hyros"><img src="https://mcp-app-store.keenethics-labs.com/badges/listed-on-mcp-app-store.svg" alt="Listed on MCP App Store" width="220" height="44"></a>

Markdown

[![Listed on MCP App Store](https://mcp-app-store.keenethics-labs.com/badges/listed-on-mcp-app-store.svg)](https://mcp-app-store.keenethics-labs.com/app/hyros)