MCP App Store
by KeenEthics
Olympus by Old Bones icon

Olympus by Old Bones MCP Server for Claude and ChatGPT

By Old Bones Therapy

Overview

Olympus by Old Bones is business intelligence for Shopify stores. It brings your Shopify sales together with your ad platforms (Meta, Google, Reddit and TikTok), Google Analytics, Search Console and Klaviyo email, and works out what you keep after product costs, shipping, fees and ad spend. Each store's Olympus runs in a hosting account the store owns, so its data stays with the store. This connector lets Claude read your store's numbers and answer in plain words: how last week went, what changed, which products sell, whether customers come back, and what each channel earns. Every metric is defined once, so the answers match what you see in Olympus. Olympus's specialists each cover one area: Hermes the whole business and briefings, Ares paid ads, Aphrodite email, Demeter search, Hephaestus conversion, Athena products and customers, Plutus margins. Ask about any of them and Claude brings in the one who covers it, without needing their names. Each is also a prompt you can pick from Claude's + menu. It only reads. Olympus never changes your store, and requests pass through oldbones.ai to your Olympus without being stored. Each person connects their own Claude and signs in to Olympus as themselves. Requires a Shopify store with Olympus by Old Bones set up, running in the store's own Railway account, on the Pantheon plan (a 14-day free trial, then from $249 a month by store revenue). On the Free plan, Claude connects and says what Pantheon adds, without reading the store's numbers.

How to connect

  1. Claude: Open the Olympus by Old Bones listing in the Claude connectors directory and choose Connect. Claude listing Olympus by Old Bones exposes 30 tools here.
  2. ChatGPT: Open the Olympus by Old Bones listing in the ChatGPT app directory and choose Connect. ChatGPT listing Olympus by Old Bones exposes 30 tools here.

Tools

agent_instructions

ChatGPT
How an Olympus agent answers: its instructions, the same text an app with a prompts menu inserts when the person picks it. Call it before answering as an agent the person asked for. Agents here: hermes.

business_snapshot

ChatGPT
Quick executive summary: today so far, yesterday's scorecard, this week's trends, and cash position.

convene_council

ChatGPT
Convene the Council: two or three of the store's specialists answer one question together, each in their own lane, and Hermes closes it with one decision, who owns it and when to look again. Call it when the person asks for the Council or accepts Hermes's or a specialist's offer of it; leave agents out for the whole business ("what should we do differently?"). It returns how the Council runs, the store's scoreboard fetched once, and each specialist's lens, so get_specialist isn't needed for them. Specialists: plutus, ares, aphrodite, athena, hephaestus, demeter.

data_health

ChatGPT
Check data pipeline health: which sources have fresh data, what's missing or stale.

get_ad_changes

ChatGPT
What changed in the ad accounts over a window, from the platforms' own change logs: budgets, bids and cost caps, campaigns and ads turned on or off, new ads launched, creative and targeting edits, with who made each change (a person, the platform, or an automation such as Google's Recommendations Auto-Apply) and the old and new values. Use it whenever a metric moved and the question is "what changed?". Meta and Google Ads from their own logs (Google keeps only 30 days); Reddit has no log, so its settings are compared night to night: what changed and when, but actor is null (unknown). Days before collection began may have Meta only (platforms on each day says which logs were read). Noise is left out: audience refreshes, image uploads, delivery pings, Meta's review steps. byDay lists each day's changes, oldest first, each with a one-line label.

get_ads

ChatGPT
Meta's ads one by one over a window, as the app's Ads view counts them: spend, link CTR, purchases, CPA and ROAS on one attribution basis (7-day click by default, which every ad reports whatever its ad set's setting; reported is Meta's own count, which flatters view and engaged-view settings), its ad set's setting, and two different fatigue reads. wearingOut: link CTR down while frequency is up, the window's last 7 days against the 7 before: interest now. lifetime: times each person it reached has seen it since it first ran, and newReachShare, the % of its latest week's people who had never seen it, as of the newest week Meta measured whatever the window; worn names why an ad carrying real spend reads as worn, the fatigue flag's own rule, and band its lifetime frequency against the store's levels. A worn ad can still hold its clicks, and an ad wearing out can be new: say which question each answers. lowSample: too few purchases to rank on. Each ad's before is the same number of days just before the window (null if it didn't run then), so whether its CPA held up is in the same call; byWeek adds its weeks through the window (weeks, oldest first): use it with search or a small limit for one ad's trend, rather than a call per week. Each ad's destination is where it's set to send people (its link, the kind of page, redirectsTo when the store redirects it) and enhancementsOn, the Meta enhancements that can send its clicks elsewhere; landings is where its clicks actually landed, from the store's own sessions matched by the utm_content its URL tags fill in: share on its link, shares by kind of page, top pages with their orders and net sales, and landsElsewhere when most of them started somewhere else. landingsUnknown says why an ad's visits can't be told apart (no utm_content, or one naming the ad set) and how to fix it: never estimate its landings. Ads are sorted by spend and capped at limit; matched says how many fit. Google and Reddit ads aren't stored yet: get_campaigns for their campaigns. How Ares reads these is in get_specialist, agent "ares".

get_bought_together

ChatGPT
Which products are bought together in the same order, over any window, from Shopify orders: every pair of products with the orders that held both (an order of three products counts once for each pair in it), those orders' net sales, and how many were first-time vs returning customers' orders; plus the combinations of three or more people buy, and the window's multi-product orders. Whole weeks, Monday to Sunday: from..to picks the weeks starting in it (default the last 12). Use product for one product's partners. A pair first-time buyers make is a starter bundle; one returning customers make is a reorder. complete: false means a week kept only its top combinations, so counts are minimums. A pair with a note had one of its products as a free gift in some orders (a free pick over an order value, say): keep the pair where its orders put it and show the note as a short, quiet line under it, not a warning; paidOrders are the orders where both were paid for. giftsKnown: false means some weeks predate gifts being marked. How Athena reads these is in get_specialist, agent "athena".

get_break_even

ChatGPT
Where ads stop paying, from the store's own margin over the last 90 days. cm1Percent is contribution margin before ads, as Shopify sees it. coverage is how much of those sales had a product cost ("Cost per item") recorded, and missing the products sold without one, most first, with whether each has a cost now: a product sold without a cost counts as free, so CM1 reads high by its share. Check coverage before quoting any margin. lines are the break-evens: mer is the sales per ad dollar below which ads lose money on the first order; ncacFirstOrder the most a new customer can cost and still pay back on their first order; ncacFirstYear the same over their first year, from the store's own repeat buying (observed). Lines are null below minCoverage. now is the last 28 days' MER and nCAC to set against them. Every line is a best case: notIncluded lists the costs Shopify can't see. Beside cm1Percent, two margins, each for its own question: cm1OfSales (CM1 ÷ total sales, tax and shipping in) is what the lines are built on, for anything judged against ad revenue; cm1OfProductSales (CM1 ÷ product sales after discounts and returns, without tax or shipping) is the margin m a discount or a price change comes off: a discount d needs m ÷ (m − d) times the orders. Never do discount or price math on cm1Percent or cm1OfSales: they count shipping and tax as sales, so a discount looks dearer than it is. costBasis says what the store's Cost per item holds (landed, the unit price only, or not said): state it, never guess. Each figure is defined in the metric registry: get_metric_definition cm1_percent, mer or ncac. How Plutus reads these is in get_specialist, agent "plutus".

get_campaigns

ChatGPT
Every ad campaign over a window, on every connected platform, as the app's Ads view adds them up: spend, the platform's revenue, ROAS, purchases or conversions, CPA, CTR, CPC, Google's impression share and share lost to budget and rank, and the window before (before). Each campaign's breakEvenRoas is from what its visitors bought (GA4, by UTM campaign), else the store's, and breakEvenFrom says which; leftAfterAds is what its revenue leaves at that bar after spend. changed: budget, bid and status changes in the window; budgetAt: whether its budget sits on the campaign or its ad sets, the level to judge it at; tooNew: spent under 1.5 times the target CPA or began under 3 days ago. A platform's settling days are still being credited: never call a trend on them. level adSet gives Meta's ad sets (the only platform that stores them), each held to its campaign's bar. Meta's ads one by one: get_ads. Use query_source only for what neither covers (keywords, placements). storeSales (the store's own sales) sits beside platformRevenue; rows can carry awareness, slowToCredit and, for ad sets, lowSample, and notes says what each flag in the result means. How Ares reads these is in get_specialist, agent "ares".

get_current_data

ChatGPT
Get real-time "today so far" data from the production data pipeline. Updated every 15 minutes.

get_customer_cohorts

ChatGPT
Customers by the month of their first order ever (cohorts), from Shopify: for each cohort, how many there were, the share who bought again within their first 3 and 12 months (repeatRate3m, repeatRate12m), and what they spent per customer in those months (ltv3m, ltv12m: sales after refunds, not margin). A figure is null until the cohort's window is over; soFar has it to date. months is each month since the first: payingRate (who placed a paid order that month), and repeatRate and ltv to date. summary weights every finished cohort by its customers: the store's typical figure. An exchange, replacement or gift (a $0 order) is never counted as buying again, so repeat rates are lower than Shopify's own cohort report. Rows flagged lowSample have too few customers to read a rate from. The last 24 cohorts are kept. firstProducts answers which first product brings customers back: for each product (and Product type) a first order had, free gifts left out, the share of those customers who bought again within 3 and 12 months and that against the typical customer (vsTypical, 1.3 = 30% more came back); lowSample under 100 first orders. shopifyComparison is Shopify Analytics' returning customer rate over the last 90 days (of everyone who bought, the share who had bought before at any time), every order and paid only: a different question, so when someone asks why Shopify shows a higher rate, explain the difference with these figures. Each figure is defined in the metric registry: get_metric_definition repeat_rate_3m, repeat_rate_12m, ltv_3m or ltv_12m.

get_daily_data

ChatGPT
Get a single day's data snapshot for a specific source.

get_date_range

ChatGPT
Get aggregated data for a date range (max 31 days). Returns combined metrics across all days. USE THIS for any multi-day or "last N days" question, including organic social — pass source "instagram-organic" or "facebook-organic" for a trailing-window social summary. For organic social the response includes a "publishAttributed" block: engagement attributed to each post's publish date and summed over posts published in the window, so no post is counted twice. PREFER publishAttributed for any "last N days" engagement question, and publishAttributed.topPosts for "best posts from the last N days". Check publishAttributed.reachCoverage before quoting a rate, and note Facebook rates are always null (post-level reach deprecated Nov 2025). The top-level metrics.* fields are rolling-window sums that overcount posts across days — account-level fields (accountReach, accountViews, pageViews) are true daily flows and sum correctly, but post engagement there does not. Instagram accountReach counts every surface, paid placements included, and is mostly ads for a store running Instagram ads: quote organicReach (posts, reels, carousels, stories) for organic reach, adReach for the paid part. tagCount and totalMentions are snapshots of the latest 25 tags, never daily volume.

get_email

ChatGPT
One Klaviyo email, flow or campaign, as the shopper sees it: its subject, preview text, sender, discount codes, its words (live text and each image's alt text, personalization left as tags), where it sits (a flow's step, hours after the trigger, its branch), and its picture: the whole email top to bottom in screen-sized pieces where Olympus photographed it, else Klaviyo's first screen only. Designed emails are mostly images, so read the picture, not just the words. A cart in the picture is a sample product. Use it when someone asks to review or improve a specific email; its numbers come from get_email_results. openInKlaviyo is a link to the email in Klaviyo's own editor (a campaign: its report), in the account the person is signed into: give it when suggesting a change. Name the email by words from its subject or its flow or campaign name; when several match, it lists them with their ids. How Aphrodite reads these is in get_specialist, agent "aphrodite".

get_email_results

ChatGPT
Email's results over a window, as the app's Email view shows them: for each flow and each campaign sent, its sends, unique clicks, unsubscribes and revenue two ways (shopify: Shopify's attribution, which adds up next to sales; klaviyo: what Klaviyo credits itself, always higher), plus totals and the same span before. Use it for "which flows or campaigns made money", "how did email do these weeks", or comparing flows. grain "weekly" adds each week's revenue, flows and campaigns apart, and each flow's by week. flow (an id, or words from its name) returns that flow's emails step by step instead. Campaigns still earning are marked settling. An email's picture and words: get_email. flowSetup lists the live flows by job, core flows not set up (missing) and flows waiting on an event that stopped (stuck); a flow's abTests read each side of a live A/B test. How Aphrodite reads these is in get_specialist, agent "aphrodite".

get_metric

ChatGPT
A registry metric's values over an EXACT date window: one total for the window (MER = total revenue / total spend, never an average of days) plus a series by day, week or month. Each value says whether it has settled and where it sits against its bands; null means not measured, never zero. Weeks or months cut by the window are marked partial. Prefer this over reading aggregate files for any "what was X between A and B" question. Metrics with scope "platform" (ad_spend, ad_revenue, ad_purchases, ad_roas, ad_cpa, ad_nmer, ad_ncac) are for one ad platform at a time: pass platform. Meta's purchases, revenue, ROAS and CPA can also be read on one attribution window for every ad set (basis "7d_click" or "1d_click"), since its own count mixes each ad set's setting: compare periods across a change of setting on 7d_click. Email revenue (email_revenue) is Shopify's count, on the attribution model Shopify's Marketing report opens on unless model is passed; klaviyo_email_revenue is what Klaviyo's own dashboard credits, always higher. Say which one a figure is.

get_metric_definition

ChatGPT
The definition of one metric from the registry (config/metrics.yaml): formula, role, sources, how long it takes to settle, date basis, bands (target/warning/critical), caveats and, for the outcome, the weekly decision rule. Read it before interpreting a number: e.g. yesterday's CM1 is still moving because label costs post late.

get_organic_searches

ChatGPT
Every Google organic search (Search Console) the store showed up for over a window, from every search Google named each day, against the window before (compare "previous", the default) or the same days last year (compare "year"). Each search: clicks, impressions, CTR and position in both windows (position weighted by impressions; lower is better, 1 to 10 is page one, 11 to 20 page two), the change (change.position negative is up), crossedPageOne ("onto" or "off") when it crossed position 10, and the page Google showed it with. Filter with brand, search, page, position ("page_one" or "page_two") or crossed_page_one; sorted by how far a search moved, or by impressions, clicks or position. Use it first for any question about particular searches. totals.coverage is the named searches' share of the site's impressions (Google hides rare ones); Search Console runs two to three days behind. How Demeter reads these is in get_specialist, agent "demeter".

get_page_funnel

ChatGPT
Every landing page's funnel over a window, from Shopify: visits that STARTED on the page, and how many added to cart, reached checkout and bought, with the same for a comparison window and the change. Bots excluded; matches Shopify Analytics. Credits only the first page of a visit: for "how is this product converting" use get_product_funnel. Rows flagged lowSample have too few visits to read a rate from. Filter by channel (UTM tags first, then the referring site, as GA4 groups them), device, referrer and utm_source/utm_medium together, OR by utm_campaign alone; and by page_type or path. channels gives each channel's visits and conversion. Each rate is defined in the metric registry: get_metric_definition page_cart_rate, page_checkout_rate or page_conversion_rate.

get_price_test

ChatGPT
Did a price change pay? Every price change in the store's timeline (found in Shopify's sales, or logged), read by one method with one verdict, so the same question always gets the same answer. Use it for any price change already made, never windows of your own. Each test holds the 28 days before against the days after (up to 28), against control: every product whose price didn't move over those days, so traffic and the season net out (vsControl). Products that changed within 7 days of each other are one test: together is the change as a whole, and leads, since shoppers move between products that moved together. verdict (pays, costs, no clear change, too early, too few orders) is on CM1 a day against control and the product's own band, how far it moves in an ordinary month; rule states it. Quote why: the same figures every time. breakEvenUnits is the change in units at which the new price keeps the same margin. ga4 is buyers per view (all, new, returning) beside it: a rise is meant to cost some buyers, so it decides nothing; watch says when new visitors fell beyond their band. status final: the read won't change (28 days passed, or endedBy the next price change); provisional: more days are coming. overlapping lists the other timeline events in those days.

get_product_funnel

ChatGPT
Every product shoppers looked at over a window, from GA4 ecommerce events, WHEREVER they saw it (its page, a collection, a bundle, the cart): views, add-to-carts, paid units bought, revenue, purchaseRate (paid units per view), revenuePerView, the same for a comparison window, and vsRest: Free gifts (a gift-with-purchase or BOGO app's free product) are not purchases: they are taken out and reported as gifts. A product with giftProduct: true was given free in the window: its cartRate includes gift picks and is not comparable; never rank it on cartRate. A product with trackingDrop set is one whose sales GA4 stopped seeing over the last 28 days while the store's held (broken tracking, or an add-on or bundle app selling it): its purchaseRate reads low, so never report it as a fall in sales; use Shopify's units for it. the product's change in purchase rate measured against every other product's, so a store-wide dip isn't blamed on one product. Products are grouped by their Shopify Product type (groups). GA4 sees most but not all buyers (blocked trackers), so compare a product with its own history, not with Shopify's order counts. Use by for a breakdown per channel, device, source/medium, visitor or campaign. Each rate is defined in the metric registry: get_metric_definition product_cart_rate, product_purchase_rate or product_revenue_per_view.

get_product_margin

ChatGPT
Each product's contribution margin over a window of days, from Shopify's sales and the cost each product had recorded when it sold (the product-margin source). For each product: units, netSales (after discounts and returns, without tax or shipping), cogs, and its share of net shipping (shipping: labels less what customers paid), Shopify Payments fees (fees) and ad spend (adSpend), each shared by its share of net sales (method: Olympus doesn't yet know which product an ad sold, so CM2 by product differs only by each product's own CM1). cm1 and cm1Percent: contribution margin before ads; cm2 and cm2Percent: after its share of ads. Units given away (a discount took their whole price) aren't their product's cost: giftUnits/giftCogs were free in an order that paid for something (a gift with purchase: shared by net sales as gifts, in CM1) and freeUnits/freeCogs in an order with nothing paid (free product for athletes, creators, promotions: marketing, shared as freeOrders with ad spend, in CM2). soldUnits/soldCogs are what it sold, and costShare is on those. Never call a product unprofitable for what it gave away. A product with noCost sold without any cost recorded: its margin is null, never estimate one. partialCost: some of its sales had none, so its margin reads high. coverage is the share of the window's sales with a cost; under minCoverage every margin reads high: say so first. costChecks lists products sold without a cost, costs that look wrong ($0 typed in, or at or above the price) and the highest cost shares. breakEvenRoas, for each product and each Product type in types: the platform ROAS below which ads on it lose money. Platforms count tax and shipping in revenue and net sales has neither, so it is net sales × totals.salesPerNetSale ÷ CM1, never 1 ÷ cm1Percent (that sets the bar too low). Judge an ad set that sells one type against its type's breakEvenRoas. The products' CM1 adds up to a little less than the store's (get_metric cm1): what free orders cost is marketing here, in CM2. Contribution margin is not profit: fixed costs come after it. How Plutus reads these is in get_specialist, agent "plutus".

get_search_queries

ChatGPT
Google organic searches (Search Console) over a window, each against the window before (compare "previous", the default) or the same days last year (compare "year"): clicks, impressions, CTR and position (weighted by impressions; lower is better, 1 to 10 is page one), moved (negative is up), its topPage, branded or not, and flags: nearPageOne (positions 11 to 20, where a fix moves a search onto page one) and pageOneNoClicks. Filter with brand, search, page or near_page_one; sort by impressions, clicks, position or moved. From each day's top 300 search × page pairs: days says how many days a search was among them, and the notes say what share of impressions the rows carry. How Demeter reads these is in get_specialist, agent "demeter".

get_search_terms

ChatGPT
Google Ads search terms (what people typed) added up over a window: each term's spend, clicks, conversions, revenue, CPA and ROAS, and the campaigns it ran in, or one row per campaign (by "campaign"). no_conversions: true lists the terms that spent without converting, the candidates for negative keywords; read brand and non-brand apart (brand). totals say what share of Google spend the terms cover (Google hides rare terms, and Performance Max shows none) and how much went to terms with no conversions. Google credits conversions up to 90 days late, and the notes say how much of a recent day's are still to come. fewClicks marks a term too thin to judge alone.

get_specialist

ChatGPT
How one of the store's specialists reads its numbers: their area, what they rank first, how they judge it, what a briefing or check from them covers, and the store's own context and timeline. Each specialist's page is also in the app's prompts menu, where there is one. Use it when the person asks for a specialist by name, asks for a briefing, or asks a question inside one specialist's area. Specialists here, with their areas: hermes (Hermes): the whole business: how it's doing, what changed and why, a briefing, and which specialist goes deeper; aphrodite (Aphrodite): email: what email earns, which flows are missing or broken, what to send next, list health and deliverability; ares (Ares): paid ads: whether the spend pays, where to add or cut budget, which ads and audiences work, why a number moved; athena (Athena): products and customers: which products carry the store, repeat buying, bundles, discounts and refunds; demeter (Demeter): organic search and SEO: growth, the easiest Google wins, what free traffic is worth, showing up in AI answers; hephaestus (Hephaestus): site conversion: where shoppers drop off before buying, which pages and products to fix, and what to change; plutus (Plutus): margins: break-even ad spend, customer worth, pricing and discounts, product margins, whether spend can grow.

get_timeline

ChatGPT
Dated events the store's owner logged in Olympus (Settings, Timeline): price changes, sales and promos, site and theme changes, launches and restocks, emails, operations (shipping, a supplier), tests, each with a date (and an end date for something that ran), a short label, often a detail, and the products or pages it touches. Use it whenever a number moved and the question is "why?", before blaming the ads or the market, and name the event you think explains it. Events go back as far as the owner logged them: when comparing two periods (this month against last year), ask for both, since a lasting change between them (free shipping ended, a new theme) may explain the difference. With them, events Olympus found in the store's own data (source: "detected"): price changes (from what each variant sold at), launches, and products selling out or back in stock, each naming its product; a price change's detail says when sales only bracket the day it changed. Also page edits Olympus found (detected: "page") by comparing each product's and collection's page night to night: one event per page per day, its what (title, seo, copy, handle, status, products, rules, created, deleted), changes with before and after for titles, SEO titles and web addresses, and a weight. Major ones (a title, SEO title, web address or status) come by default; minor ones (a description, an SEO description, a collection's products or rules) only when asked with weight or what, and are counted otherwise. Before blaming Google or the ads for a page's drop, ask for its page edits, e.g. what "seo" with search "/collections/<handle>". The ad accounts' own change logs are get_ad_changes.

get_weekly_data

ChatGPT
Get weekly aggregate data (Monday-Sunday). Includes revenue, orders, AOV, ad spend, ROAS, customer segmentation, profitability (CM1/CM2), and cash flow — AND organic social rollups in the "instagramOrganic" and "facebookOrganic" blocks (followers, reach, likes, comments, saves, shares, mentions, engagementRate, daysWithData), plus "postingHistory", "ugc", "searchConsole", and "judgeme". USE THIS for weekly organic social reporting. It also returns "socialPublishAttributed": per-platform engagement attributed to each post's publish date with the week's best posts ranked — PREFER that block for engagement totals and rates. The instagramOrganic/facebookOrganic blocks carry rolling-window sums whose rates are deliberately null (no valid denominator); followers and followerChange in them are reliable. Instagram reach: organicReach is posts, reels, carousels and stories, adReach the paid placements, accountReach both (each a sum of daily reach). instagramOrganic.commentReplies is comments received on the store's posts and how the store answered them (replyRate, medianReplyHours). newTags/newMentions are the week's new brand tags; tagCount and totalMentions add up daily snapshots and count a post up to 7 times, so never trend them.

list_agents

ChatGPT
List all available Olympus Pantheon agents with their specialties and data sources

list_metrics

ChatGPT
List the business metrics Olympus defines, outcome first (CM2: the one number that settles spend), then guardrails, then diagnostics. Call this to find a metric's name, then get_metric_definition before interpreting or quoting it.

query_source

ChatGPT
Row-level query over one source's COMPLETE stored data, run server-side: find, filter, sort and limit rows such as product variants, ads, campaigns or posts. Over a date range each row is tagged with its date; group_by + sum combines them (e.g. revenue per SKU over 30 days). Use it for "which / top / worst / how many" questions instead of reading whole files. For a metric over a window, use get_metric.

report_gap

ChatGPT
Call this once when the person asks something Olympus's tools can't answer, so the store can see what's missing. Describe what they wanted in one line, with no figures, names or customer details (for example "wanted profit by product variant"). Then tell the person it's been noted. Don't call it for questions you could answer.

whoami

ChatGPT
Who you're speaking with on the Acme Test Store team: their name, role and what they may see (their data access level), with any context about them. Call this at the start of every session. The server decides it from how they signed in, not from anything the app sends.

business_snapshot

Claude

convene_council

Claude

data_health

Claude

get_ad_changes

Claude

get_ads

Claude

get_bought_together

Claude

get_break_even

Claude

get_campaigns

Claude

get_current_data

Claude

get_customer_cohorts

Claude

get_daily_data

Claude

get_date_range

Claude

get_email

Claude

get_email_results

Claude

get_metric

Claude

get_metric_definition

Claude

get_organic_searches

Claude

get_page_funnel

Claude

get_price_test

Claude

get_product_funnel

Claude

get_product_margin

Claude

get_product_profit

Claude

get_search_queries

Claude

get_search_terms

Claude

get_specialist

Claude

get_timeline

Claude

get_weekly_data

Claude

list_agents

Claude

list_metrics

Claude

query_source

Claude

whoami

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/olympus-by-old-bones"><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/olympus-by-old-bones)