OverviewTool Reference

Tool Reference

Every tool the Mythic MCP server exposes — 197 tools across 25 scope families — with the scope each one needs and the API route it proxies.

About this reference

All 197 tools the Settings Server registers, grouped by the scope family that grants them. Each tool is a thin proxy over the HTTP API: the Proxies column names the route it calls, so anything you can do here you can also do over HTTP, and both answer from the same implementation.

Tools are gated by the scopes on your mcp_ key. Only tools within the key's scopes are listed; calling any other tool by name answers insufficient_scope with the scope to request, so an agent can tell you exactly what to add. A :write scope implies the matching :read. The same scope authorizes the Proxies route when the key is used directly over HTTP.

Client-scoped tools operate on the selected client — see the select-a-client flow.

Session

No scope needed. list_clients and select_client register for every agency-wide key (list_clients also fronts the roster route over HTTP, where it takes agency:read); whoami and search_docs register for every key.

ToolScopeWhat it doesProxies
list_clients
List Clients
List the clients (locations) this agency key can operate on.GET /builder/locations
GET /client/v1/agency/locations
select_client
Select Client
Set the active client for this session by id (from list_clients).
whoami
Who Am I
Describe this connection: key type (agency-wide or bound to one client), the pinned client if any, the scopes held, and per family whether this key can read, write, or nothing.
search_docs
Search Documentation
Search the public Mythic Analytics documentation (docs.mythicdata.io): API routes, tool behaviour, scopes, error codes, SDK setup.

People

Person profiles, identities, merges and merge warnings.

ToolScopeWhat it doesProxies
list_people
List People
people:readResolved person profiles for this client, most recently seen first — display name, email, company, session counts, first/last channel and UTMs per row, so rows are labelable without a per-person fetch.GET /client/v1/data/people
get_person
Get Person
people:readOne full person profile: properties, all linked identities, first/last seen, session and device counts, first-touch geo/browser/OS.GET /client/v1/data/people/:personId
get_person_summary
Get Person Summary
people:readCompact profile card for one person: properties, identities, first/last seen, plus a metrics block (session/device counts, first-touch landing page, UTMs, referrer, geo).GET /client/v1/data/people/:personId/summary
get_person_activity
Get Person Activity
people:readOne person's raw event stream, newest first.GET /client/v1/data/people/:personId/activity
get_person_attribution
Get Person Attribution
people:readOne person's marketing attribution: first-touch and last-touch channel/UTMs/referrer with first/last seen timestamps.GET /client/v1/data/people/:personId/attribution
list_identities
List Identities
people:readBulk identity mappings (identity_value -> canonical person_id) for agencies maintaining their own identity graph.GET /client/v1/data/identities
list_merges
List Person Merges
people:readAuthoritative person-merge history for this client (source_person_id merged into target_person_id, with reason and timestamp), oldest first.GET /client/v1/data/merges
get_person_merges
Get Person Merges
people:readMerge history touching ONE person — every merge where they were the source or the target, oldest first.GET /client/v1/data/people/:personId/merges
list_merge_warnings
List Merge Warnings
people:readMerges the identity processor REFUSED or flagged as suspicious — each row names the event, the identity value, and the reason.GET /client/v1/data/merge-warnings

Events & Explore

Event volumes, trends, breakdowns, property discovery, self-serve trend/funnel queries, tracking coverage and Core Web Vitals.

ToolScopeWhat it doesProxies
list_events
List Events
events:readEvery event name this client actually sends, with volumes, over a date range.GET /client/v1/data/events/summary
get_event_volume_daily
Get Daily Event Volume
events:readEvent counts per day (optionally for one event name via event_type).GET /client/v1/data/events/daily
get_event_trend
Get Event Trend
events:readOverall event-volume trend over a window — defaults to the last 14 days (days), or pass explicit start_date/end_date.GET /client/v1/data/events/trend
get_event_breakdown
Get Event Breakdown
events:readTraffic volume broken down by ONE dimension — top pages, referrers, devices, geo, or UTM values.GET /client/v1/data/events/breakdown
list_event_properties
List Event Properties
events:readProperty catalog for this client: every event-property or person-property key ever observed, with an inferred type, a masked sample value, how often it appears and first/last seen.GET /client/v1/data/properties
query_events
Query Events (trend / funnel)
events:readSelf-serve analytics over the event stream in ONE call, sub-second: a TREND (1–5 series, each an event × math such as total/dau/unique_sessions/sum/p95, bucketed by hour/day/week/month or as a single number,…POST /client/v1/data/query
list_property_values
List Property Values
events:readTop values of ONE event property over the last N days (default 30), with counts — the picker behind query_events filters and breakdowns.GET /client/v1/data/query/values
get_commerce_summary
Get Commerce Summary
events:readDaily ecommerce totals — orders, revenue, average order value, units, buyers — for clients emitting the Mythic commerce spec (Shopify does automatically).GET /client/v1/data/commerce/summary
get_commerce_items
Get Commerce Items
events:readTop products by revenue, units or orders — grouped by product id, SKU, variant, name, category or brand.GET /client/v1/data/commerce/items
explain_tracking_coverage
Explain Tracking Coverage
events:readCan a "why is this page losing people" question be answered from the data we have for it? Run this BEFORE any behavioural analysis of a page and take the verdict at face value — it reports session volume, wh…GET /client/v1/data/explain/coverage
get_core_web_vitals
Get Core Web Vitals
events:readCore Web Vitals measured on this client's site (lcp, fcp, cls, ttfb, fid, inp).GET /client/v1/performance/cwv

Sessions

Session analytics — durations, engagement, breakdowns.

ToolScopeWhat it doesProxies
list_sessions
List Sessions
sessions:readOne row per website session, most recent first — landing/exit page, duration, pageviews, device/browser/geo, UTMs, engagement and bounce flags, identity link.GET /client/v1/data/sessions
get_sessions_breakdown
Get Sessions Breakdown
sessions:readSession aggregates grouped by ONE dimension — sessions, engagement, bounce rate etc.GET /client/v1/data/sessions/breakdown

Session Replays

Compact, LLM-ready timelines of recorded visitor sessions (no PII).

ToolScopeWhat it doesProxies
list_replays
List Replays
replays:readIndex of sessions that have a screen recording, with interaction counters merged in where available (duration, clicks, keypresses, console_errors, network_count, last_url).GET /client/v1/data/replays
get_session_timeline
Get Session Timeline
replays:readCompact, chronological timeline of one visitor session for the active client — page journey, dwell time, form submissions, field inputs, identify, custom events and errors.GET /client/v1/data/replays/:sessionId/timeline

Error Tracking

Grouped JavaScript exceptions, occurrences and digests.

ToolScopeWhat it doesProxies
list_exception_issues
List Exception Issues
exceptions:readGrouped JavaScript error issues — one row per fingerprinted issue (stable issue_id from error type + normalized message) with occurrence/session/user counts and a volume sparkline.GET /client/v1/data/exceptions/issues
get_exception_issue
Get Exception Issue
exceptions:readDetail header for ONE grouped error issue by its stable issue_id (from list_exception_issues): counts, first/last seen and volume series over the window.GET /client/v1/data/exceptions/issues/:id
list_exception_occurrences
List Exception Occurrences
exceptions:readRaw occurrences of ONE error issue — individual events with parsed stack frames, page URL and session_id, newest first.GET /client/v1/data/exceptions/issues/:id/occurrences
get_exception_digest
Get Exception Digest
exceptions:readWeekly error digest in one call: summary with week-over-week deltas, a daily bar series, the top issues, and issues NEW this week (new = not seen in the preceding new_lookback_days, default 90).GET /client/v1/data/exceptions/digest

Heatmaps

Click cells and scroll depth per page.

ToolScopeWhat it doesProxies
get_heatmap
Get Heatmap
heatmaps:readAggregated click grid for one page.GET /client/v1/data/heatmap
list_heatmap_pages
List Heatmap Pages
heatmaps:readPages that actually have heatmap data for this client, busiest first — START HERE before get_heatmap or get_heatmap_scroll.GET /client/v1/data/heatmap/pages
get_heatmap_facets
Get Heatmap Facets
heatmaps:readFilter values that exist for one page (device_type, utm_source, utm_medium, each with session counts), scoped to sessions that actually left heatmap points there — so every value returned yields a non-empty…GET /client/v1/data/heatmap/facets
get_heatmap_scroll
Get Heatmap Scroll Depth
heatmaps:readCumulative scroll-depth curve for one page: bands of band px with how many sessions reached at least that depth.GET /client/v1/data/heatmap/scroll

BigQuery Export

Export status and schema for the agency or one location.

ToolScopeWhat it doesProxies
get_bigquery_export_schema
Get BigQuery Export Schema
bigquery_export:readThe static semantic catalog of the BigQuery export: every table with its columns, types and descriptions.GET /client/v1/data/export/schema
get_bigquery_export
Get BigQuery Export
bigquery_export:readThis client's BigQuery export handle: the fully-qualified dataset (mythic-data.<name>), its table ids, provisioning status and timestamps.GET /client/v1/data/export

Insights

Saved analytics queries and their results.

ToolScopeWhat it doesProxies
list_insights
List Insights
insights:readList insights for the active client.GET /builder/insights
get_insight
Get Insight
insights:readGet a single insight by ID, including its full config (config.query is the explore spec it runs).GET /builder/insights/:id
run_insight
Run Insight
insights:readExecute a STORED insight and return its series/buckets (trend) or steps (funnel) — the same shape query_events returns.POST /builder/insights/:id/query
preview_insight
Preview Insight
insights:readExecute an insight CONFIG without saving it — the same { insight_type, config } shape create_insight stores, run in-memory and never persisted.POST /builder/insights/preview
create_insight
Create Insight
insights:writeCreate a new insight for the active client: a saved explore spec (config.query) drawn as insight_type.POST /builder/insights
update_insight
Update Insight
insights:writeUpdate an existing insight.PATCH /builder/insights/:id
delete_insight
Delete Insight
insights:writePermanently delete an insight by ID.DELETE /builder/insights/:id

Dashboards

Collections of insights arranged into dashboards.

ToolScopeWhat it doesProxies
list_dashboards
List Dashboards
dashboards:readList all dashboards, optionally filtered by location_id.GET /builder/dashboards
get_dashboard
Get Dashboard
dashboards:readGet a dashboard by ID, including all its insight items with layout and insight details.GET /builder/dashboards/:id
create_dashboard
Create Dashboard
dashboards:writeCreate a new dashboard for the active client.POST /builder/dashboards
update_dashboard
Update Dashboard
dashboards:writeUpdate dashboard metadata.PATCH /builder/dashboards/:id
delete_dashboard
Delete Dashboard
dashboards:writePermanently delete a dashboard and all its insight associations.DELETE /builder/dashboards/:id
add_insight_to_dashboard
Add Insight to Dashboard
dashboards:writeAdd an insight to a dashboard with responsive grid layout positions.POST /builder/dashboards/:id/insights
remove_insight_from_dashboard
Remove Insight from Dashboard
dashboards:writeRemove an insight from a dashboard.DELETE /builder/dashboard-insights/:id

Canvases

Freeform node/edge canvases with attached events.

ToolScopeWhat it doesProxies
list_canvases
List Canvases
canvases:readList all canvases (visual tag management configurations), optionally filtered by tenant_key.GET /builder/canvases
get_canvas
Get Canvas
canvases:readGet a canvas with all its nodes, edges, node URLs, and node events.GET /builder/canvases/:id
create_canvas
Create Canvas
canvases:writeCreate a new canvas for visual tag management for the active client.POST /builder/canvases
update_canvas
Update Canvas
canvases:writeUpdate canvas metadata.PATCH /builder/canvases/:id
delete_canvas
Delete Canvas
canvases:writePermanently delete a canvas and all its nodes, edges, and events (cascading).DELETE /builder/canvases/:id
add_canvas_node
Add Canvas Node
canvases:writeAdd a node (page, action, decision, or offsite) to a canvas.
update_canvas_node
Update Canvas Node
canvases:writeUpdate a canvas node's properties.
delete_canvas_node
Delete Canvas Node
canvases:writeDelete a canvas node and its associated URLs, events, and edges (cascading).
add_canvas_edge
Add Canvas Edge
canvases:writeConnect two canvas nodes with an edge (defines flow between pages/actions).
delete_canvas_edge
Delete Canvas Edge
canvases:writeRemove an edge between two canvas nodes.
add_node_event
Add Node Event
canvases:writeAdd a tracking event to a canvas node (e.g., fire a Meta Pixel event on page load).POST /builder/canvases/:id/nodes/:nodeId/events
delete_node_event
Delete Node Event
canvases:writeRemove a tracking event from a canvas node.DELETE /builder/canvases/:id/events/:eventId

Segments

Stored person segments — definitions, live counts, membership.

ToolScopeWhat it doesProxies
list_segments
List Segments
segments:readEvery stored segment for this client — reusable audience definitions over person profiles.GET /builder/segments
get_segment
Get Segment
segments:readOne segment by id, including its full filter definition.GET /builder/segments/:id
get_segment_count
Get Segment Count
segments:readLive person count for a segment — how many people match its definition right now.GET /builder/segments/:id/count
list_segment_members
List Segment Members
segments:readThe people currently matching a segment, resolved live, with pagination.GET /builder/segments/:id/members
create_segment
Create Segment
segments:writeCreate a segment from a filter definition.POST /builder/segments
update_segment
Update Segment
segments:writeUpdate a segment.PATCH /builder/segments/:id
delete_segment
Delete Segment
segments:writePermanently delete a segment.DELETE /builder/segments/:id

Constraint Finder

End-to-end paid funnel analysis and its stored benchmarks.

ToolScopeWhat it doesProxies
find_constraint
Find Funnel Constraint
constraints:readEnd-to-end paid-funnel analysis (Meta spend → pixel sessions → conversions) per campaign/adset/ad: impressions→clicks (ad), clicks→sessions (tracking), sessions→leads (landing), leads→conversions (sales) — w…GET /client/v1/constraints
list_constraint_events
List Constraint-Eligible Events
constraints:readWhich events can serve as lead_event / conversion_event for the constraint finder, and — the part no other endpoint reports — what share of each actually carries a session.GET /client/v1/constraints/events
get_constraint_audit
Constraint Tracking Audit
constraints:readTracking hygiene per campaign: WHICH campaigns are measurable at all, and WHERE the ad clicks that reached no campaign went.GET /client/v1/constraints/audit
get_constraint_options
Constraint Finder Options
constraints:readThe constraint finder vocabulary — valid group_by/attribution values, benchmark steps and their precedence chain, defaults, and usage hints.GET /client/v1/constraints/options
get_constraint_benchmarks
Get Stored Constraint Benchmarks
constraints:readThe standing benchmark targets on file for this location: the account-wide default plus per-campaign targets, applied automatically to every find_constraint call.GET /client/v1/constraints/benchmarks
set_constraint_benchmarks
Set Constraint Benchmarks
constraints:writeStore standing benchmark targets for ONE scope — a campaign (by id or name) or, with campaign omitted, the account-wide default.PUT /client/v1/constraints/benchmarks
delete_constraint_benchmarks
Delete Constraint Benchmarks
constraints:writeClear stored benchmark targets for ONE scope, or one step of it.DELETE /client/v1/constraints/benchmarks

Correlation

Pairwise and rolling metric correlation with lead/lag scan.

ToolScopeWhat it doesProxies
get_correlation
Correlate Metrics
correlation:readTrend of 2-5 metrics over day/week/month buckets with every pairwise Pearson AND Spearman coefficient, a rolling correlation folded into the series rows (corr:<x>~<y>, plottable on the same axis), and a le…GET /client/v1/correlation
list_correlation_metrics
List Correlatable Metrics
correlation:readReal discovery of what can be correlated for THIS client, not a static list: event families list the event names actually captured in the window, Meta metrics are marked unavailable when the client has no ad…GET /client/v1/correlation/metrics
get_correlation_options
Correlation Options
correlation:readThe correlation vocabulary at no query cost: grains, the fixed metric registry, the metric-family grammar (family:<event_name>), and every query param with its bounds and defaults.GET /client/v1/correlation/options

Incrementality

Geo-holdout experiments, iROAS and coefficients.

ToolScopeWhat it doesProxies
list_incrementality_markets
List Incrementality Markets
incrementality:readDaily revenue by geographic region over a lookback, with candidate CONTROL markets ranked by Pearson correlation against a proposed test set.GET /client/v1/incrementality/markets
get_incrementality_eligibility
Incrementality Eligibility
incrementality:readPre-flight before designing any geo experiment: geo coverage of revenue, history depth, matchable market count, and the daily budget the client's noise floor implies for a conclusive 30-day test.GET /client/v1/incrementality/eligibility
list_incrementality_experiments
List Incrementality Experiments
incrementality:readEvery geo-holdout experiment for this client with definition, design (power analysis), result, and derived lifecycle progress (pending/running/cooldown/complete).GET /client/v1/incrementality/experiments
get_incrementality_experiment
Get Incrementality Experiment
incrementality:readOne experiment by id: definition, design, stored result (normalized on read), and lifecycle progress.GET /client/v1/incrementality/experiments/:id
get_incrementality_launch_plan
Incrementality Launch Plan
incrementality:readThe exact Meta ad-side recipe for conducting the holdout: control regions resolved to Meta targeting keys, apply/revert dates, paste-ready API calls.GET /client/v1/incrementality/experiments/:id/launch-plan
validate_incrementality_experiment
Validate Incrementality Experiment
incrementality:readTwo modes, chosen by phase.GET /client/v1/incrementality/experiments/:id/validate
get_incrementality_coefficients
Get Incrementality Coefficients
incrementality:readThe progressive truth: computed experiments pooled by coefficient series (channel + revenue definition + spend scope — only same-estimand experiments pool) into an inverse-variance weighted median.GET /client/v1/incrementality/coefficients
get_incrementality_coefficients_history
Incrementality Coefficient History
incrementality:readThe progressive truth over time: every computed experiment's coefficient in sequence plus the running weighted median at each point, per coefficient series.GET /client/v1/incrementality/coefficients/history
create_incrementality_experiment
Create Incrementality Experiment
incrementality:writeCreate a geo-holdout experiment (status draft).POST /client/v1/incrementality/experiments
delete_incrementality_experiment
Delete Incrementality Experiment
incrementality:writeDelete an experiment.DELETE /client/v1/incrementality/experiments/:id
compute_incrementality
Compute Incrementality
incrementality:writeRun the iROAS computation for an experiment: weighted-synthetic-control diff-in-diff over pre vs test+cooldown, folded with the Meta spend row, stored as the experiment result (status becomes computed).POST /client/v1/incrementality/experiments/:id/compute

Event Contracts

Declared per-event property schemas and their violation reports.

ToolScopeWhat it doesProxies
list_event_contracts
List Event Contracts
contracts:readThe event contracts stored for this client — each one an event name plus the properties it is declared to carry, their types, and which are required.GET /client/v1/contracts
check_event_contracts
Check Event Contracts
contracts:readDiff every stored contract (or one, with event) against live traffic and report violations, worst first.GET /client/v1/contracts/violations
get_contract_samples
Get Contract Violation Samples
contracts:readThe actual offending events behind ONE violation from check_event_contracts — up to 50 raw examples with session_id and $current_url, so you can see where the bad data comes from.GET /client/v1/contracts/samples
suggest_event_contract
Suggest Event Contract
contracts:readInfer a contract for one event from its live traffic — the fastest way to author one.GET /client/v1/contracts/suggest
list_contract_presets
List Contract Presets
contracts:readThe built-in contract packs and every contract in them.GET /client/v1/contracts/presets
set_event_contract
Set Event Contract
contracts:writeCreate or replace the contract for ONE event.PUT /client/v1/contracts
delete_event_contract
Delete Event Contract
contracts:writeRemove one event contract.DELETE /client/v1/contracts/:event
apply_contract_preset
Apply Contract Preset
contracts:writeApply a built-in contract pack to a client in one call.POST /client/v1/contracts/presets/:preset

Destinations

Activation destinations events are forwarded to, their credentials and deliveries.

ToolScopeWhat it doesProxies
list_destinations
List Destinations
destinations:readList activation destinations for the active client (webhook, Meta CAPI, Google Ads).GET /client/v1/destinations
get_destination
Get Destination
destinations:readGet a single activation destination by ID, including its full action_config and trigger_rules.GET /client/v1/destinations/:id
list_destination_credentials
List Destination Credentials
destinations:readWhich destination credentials are stored for this client — METADATA ONLY (id, destination_type, credential_name, created/updated timestamps).GET /client/v1/destinations/credentials
get_destination_oauth_client
Get Destination OAuth Client
destinations:readWhich Google OAuth client this agency's consent flows run as: has_client (agency registered its own), source ('agency' or the platform default), the client_id (not a secret — what you check against the Cloud…GET /client/v1/destinations/oauth/client
list_destination_deliveries
List Destination Deliveries
destinations:readDelivery log for this client's destinations, newest first — one row per delivery attempt with status (success|failed|retrying|skipped|test), response status, error, and timing.GET /client/v1/destinations/deliveries
GET /client/v1/destinations/:id/deliveries
get_destination_delivery
Get Destination Delivery
destinations:readFull detail for ONE delivery (destination + source event uuid from list_destination_deliveries): the request actually sent (body + headers), the destination's response, attempt counts, field warnings/violati…GET /client/v1/destinations/:id/deliveries/:eventUuid
get_destination_delivery_status
Get Destination Delivery Status
destinations:readWhat Google did with a delivery AFTER accepting it — google_ads / google_analytics destinations only.GET /client/v1/destinations/:id/deliveries/:eventUuid/status
get_destination_health
Get Destination Health
destinations:readPer-destination delivery health rollup over a recent window: success/failure/skip counts, success rate, latency (avg + p95), queue lag, last error, and a credential_ok flag (false when the most recent failur…GET /client/v1/destinations/health
verify_destination
Verify Destination
destinations:readDid deliveries actually COUNT downstream? convert_experiments destinations only.GET /client/v1/destinations/:id/verification
list_platform_integrations
List Platform Integrations
destinations:readShow the managed Meta / Google Ads integrations for the active client: which halves are connected (browser pixel tag, server destination) and whether the delivery credential is stored.GET /client/v1/destinations/integrations
create_destination
Create Destination
destinations:writeCreate an activation destination for the active client.POST /client/v1/destinations
update_destination
Update Destination
destinations:writeUpdate an existing destination.PATCH /client/v1/destinations/:id
delete_destination
Delete Destination
destinations:writePermanently delete an activation destination by ID.DELETE /client/v1/destinations/:id
set_destination_credential
Set Destination Credential
destinations:writeStore (or rotate — same type+name overwrites) the credential one destination type delivers with.PUT /client/v1/destinations/credentials/:type
delete_destination_credential
Delete Destination Credential
destinations:writeDelete stored credential(s) for one destination type.DELETE /client/v1/destinations/credentials/:type
set_destination_oauth_client
Set Destination OAuth Client
destinations:writeRegister the agency's OWN Google OAuth client for destination consent flows (their brand on the consent screen, their API quota) instead of the platform default.PUT /client/v1/destinations/oauth/client
delete_destination_oauth_client
Delete Destination OAuth Client
destinations:writeRemove the agency's registered Google OAuth client; future consent flows fall back to the platform default (Mythic's brand and quota).DELETE /client/v1/destinations/oauth/client
initiate_destination_oauth
Initiate Destination OAuth
destinations:writeStart the Google consent flow that stores a google_ads / google_analytics credential WITHOUT anyone handling a refresh token.POST /client/v1/destinations/oauth/initiate
test_destination
Test Destination
destinations:writeFire a REAL test delivery through one destination — this sends an actual event to the live ad platform using the stored credential, and the attempt lands in the delivery log (status "test").POST /client/v1/destinations/:id/test
connect_meta_integration
Connect Meta Integration
destinations:writeOne-click Meta tracking: creates the managed Meta Pixel browser tag AND the Meta CAPI server destination.POST /client/v1/destinations/integrations/meta
connect_google_ads_integration
Connect Google Ads Integration
destinations:writeOne-click Google Ads tracking: creates the Google Ads (Data Manager) server destination, plus a managed gtag browser tag when any event has a conversion_label.POST /client/v1/destinations/integrations/google_ads
connect_google_analytics_integration
Connect GA4 Integration
destinations:writeOne-click GA4 measurement with NO page tag: creates the GA4 (Data Manager) server destination mapped to the commerce spec.POST /client/v1/destinations/integrations/google_analytics
connect_openai_ads_integration
Connect OpenAI Ads Integration
destinations:writeOne-click OpenAI Ads conversions: creates the OpenAI Ads server destination mapped from the commerce spec to OpenAIu2019s event taxonomy.POST /client/v1/destinations/integrations/openai_ads
delete_platform_integration
Delete Platform Integration
destinations:writeDisconnect a managed integration (Meta, Google Ads, GA4, OpenAI Ads): detaches the managed browser tag where there is one and removes the managed destination (and its stored credential when nothing else uses…DELETE /client/v1/destinations/integrations/:platform

Tracking Settings

Per-location ingestion controls: allowed origins, autocapture, heatmaps, experiments, conversions, contract alerts — and the ingestion on/off switch.

ToolScopeWhat it doesProxies
get_tracking_settings
Get Tracking Settings
settings:readRead this client's per-location tracking settings.GET /client/v1/settings/allowed-origins
GET /client/v1/settings/autocapture
GET /client/v1/settings/ip-geo-enrichment
GET /client/v1/settings/heatmaps
GET /client/v1/settings/experiments
GET /client/v1/settings/conversions
GET /client/v1/settings/session-replay
GET /client/v1/settings/contract-alerts
get_client_status
Get Client Status
settings:readWhether this client (location) is active — an inactive client's events are rejected at ingestion.GET /client/v1/status
update_tracking_setting
Update Tracking Setting
settings:writeUpdate ONE tracking setting for this client.PUT /client/v1/settings/allowed-origins
PUT /client/v1/settings/autocapture
PUT /client/v1/settings/ip-geo-enrichment
PUT /client/v1/settings/heatmaps
PUT /client/v1/settings/experiments
PUT /client/v1/settings/conversions
PUT /client/v1/settings/session-replay
PUT /client/v1/settings/contract-alerts
set_client_status
Set Client Status
settings:writeActivate or deactivate this client.POST /client/v1/status

Client Provisioning

Create new clients under the agency. Agency-wide by nature: a client-scoped key must not be able to create siblings.

Agency-wide keys only — a key bound to one client cannot hold this scope.

ToolScopeWhat it doesProxies
create_location
Create Location
provisioning:writeProvision a new client (location) under your agency.POST /client/v1/locations

Client Setup

One client’s own setup — details, install snippet, custom tracking hostname and install verification.

ToolScopeWhat it doesProxies
get_location
Get Location
locations:readThis client's provisioning details: id, name, publishable key, secret key, domain, contact fields, timezone, SDK global name, and whether tracking is currently enabled.GET /client/v1/locations/details
get_location_loader
Get Install Snippet
locations:readThe tracking snippet to paste into this client's site, plus the publishable key, API host and SDK global name it uses.GET /client/v1/locations/loader
get_location_hostname
Get Custom Tracking Hostname
locations:readThis client's custom tracking hostname and its validation state (Cloudflare hostname status and SSL status), or null when none is attached.GET /client/v1/locations/hostname
get_location_last_event
Check Tracking Is Live
locations:readEvent count and the most recent event timestamp for this client.GET /client/v1/locations/last-event
list_location_events
List Raw Events
locations:readIndividual events for this client, newest first — the debugging view for confirming an install or chasing a missing property.GET /client/v1/locations/events
update_location
Update Location
locations:writeUpdate a client's own details — name, domain, email, phone, website, timezone or global_name.PATCH /client/v1/locations/details
set_location_hostname
Set Custom Tracking Hostname
locations:writeAttach a first-party tracking hostname (e.g.PUT /client/v1/locations/hostname
delete_location_hostname
Remove Custom Tracking Hostname
locations:writeDetach this client's custom tracking hostname and stop routing events for it.DELETE /client/v1/locations/hostname

Link redirects, click analytics, link webhooks and uptime.

ToolScopeWhat it doesProxies
list_links
List Links
links:readThis client's link redirects, newest first, each enriched with its all-time click_count.GET /client/v1/links
get_link_analytics
Get Link Analytics
links:readAggregated click analytics per link (totals by slug), optionally narrowed to one slug, a date range, or specific UTM values.GET /client/v1/links/analytics
get_link_trend
Get Link Click Trend
links:readClick counts over time for link redirects — the time-series companion to get_link_analytics.GET /client/v1/links/trend
get_link_click_stream
Get Link Click Stream
links:readIndividual recent link clicks (real-time stream), newest first — who clicked what, with UTM detail.GET /client/v1/links/stream
list_link_utm_values
List Link UTM Values
links:readDistinct UTM values seen on link clicks — use to discover what to pass as UTM filters to the analytics/trend/stream tools.GET /client/v1/links/utm-values
list_link_webhooks
List Link Uptime Webhooks
links:readThe uptime notification webhooks for this client — each fires on link_down and/or link_up when a monitored link destination goes down or recovers.GET /client/v1/links/webhooks
get_link_uptime
Get Link Uptime
links:readCurrent up/down status of each monitored link destination (or one, with slug).GET /client/v1/links/uptime
get_link_uptime_history
Get Link Uptime History
links:readUptime check time-series for monitored link destinations — status codes and response times over a date range.GET /client/v1/links/uptime/history
create_link
Create Link
links:writeCreate a link redirect.POST /client/v1/links
update_link
Update Link
links:writeUpdate fields on an existing link redirect (partial update — only the fields you pass change).PATCH /client/v1/links/:linkId
delete_link
Delete Link
links:writePermanently delete a link redirect.DELETE /client/v1/links/:linkId
create_link_webhook
Create Link Uptime Webhook
links:writeCreate a webhook that is called when a monitored link destination goes down (link_down) or recovers (link_up).POST /client/v1/links/webhooks
update_link_webhook
Update Link Uptime Webhook
links:writeUpdate an uptime webhook (partial — only the fields you pass change).PATCH /client/v1/links/webhooks/:webhookId
delete_link_webhook
Delete Link Uptime Webhook
links:writePermanently delete an uptime webhook.DELETE /client/v1/links/webhooks/:webhookId

Tags

GTM-like tags fired by the SDK.

ToolScopeWhat it doesProxies
list_tags
List Tags
tags:readList tag assignments (tenant_tags) for the active client.GET /client/v1/config/tags
create_tag
Create Tag Assignment
tags:writeAssign a tag to the active client (tenant_tags row).POST /client/v1/config/tags
update_tag
Update Tag Assignment
tags:writeUpdate a tag assignment for the active client.PATCH /client/v1/config/tags/:tagId
delete_tag
Delete Tag Assignment
tags:writeRemove a tag assignment from the active client.DELETE /client/v1/config/tags/:tagId

Snippets

Custom code snippets injected by the SDK.

ToolScopeWhat it doesProxies
list_snippets
List Snippets
snippets:readList custom code snippets (tenant_snippets) for the active client.GET /client/v1/config/snippets
get_snippet
Get Snippet
snippets:readGet a single code snippet by ID, including its full code.GET /client/v1/config/snippets/:id
create_snippet
Create Snippet
snippets:writeCreate a custom code snippet for the active client.POST /client/v1/config/snippets
update_snippet
Update Snippet
snippets:writeUpdate a code snippet.PATCH /client/v1/config/snippets/:id
delete_snippet
Delete Snippet
snippets:writePermanently delete a code snippet by ID.DELETE /client/v1/config/snippets/:id

Transformers

Event transformers applied during ingestion.

ToolScopeWhat it doesProxies
list_transformers
List Transformers
transformers:readList event enrichment transformers for the active client.GET /client/v1/config/transformers
get_transformer
Get Transformer
transformers:readGet a single transformer by ID, including its full config.GET /client/v1/config/transformers/:id
create_transformer
Create Transformer
transformers:writeCreate an event enrichment transformer for the active client.POST /client/v1/config/transformers
update_transformer
Update Transformer
transformers:writeUpdate a transformer.PATCH /client/v1/config/transformers/:id
delete_transformer
Delete Transformer
transformers:writePermanently delete a transformer by ID.DELETE /client/v1/config/transformers/:id

Airbyte Sync

Agency-grain sync orchestration: connections, schedules, pipelines, sync history.

Agency-wide keys only — a key bound to one client cannot hold this scope.

ToolScopeWhat it doesProxies
list_airbyte_platforms
List Airbyte Platforms
airbyte:readThe ad/CRM platforms Mythic can connect through Airbyte (google_ads, meta_ads, bing_ads, tiktok_ads, salesforce, …) with their default streams, sync options and whether they support the OAuth consent flow.GET /client/v1/airbyte/platforms
get_airbyte_config
Get Airbyte Config
airbyte:readThis agency's Airbyte workspace configuration and provisioning status.GET /client/v1/airbyte/config
list_airbyte_webhooks
List Airbyte Webhook Subscriptions
airbyte:readThe agency's sync-notification relay subscriptions.GET /client/v1/airbyte/webhooks
list_airbyte_connections
List Airbyte Connections
airbyte:readEvery Airbyte connection this agency owns, optionally filtered.GET /client/v1/airbyte/connections
get_airbyte_connection
Get Airbyte Connection
airbyte:readOne connection by its Mythic id — platform, client, enabled streams, schedule, sync_dow, last sync.GET /client/v1/airbyte/connections/:id
list_airbyte_jobs
List Airbyte Jobs
airbyte:readA connection's recent sync jobs, fetched live from Airbyte.GET /client/v1/airbyte/connections/:id/jobs
list_airbyte_sync_events
List Airbyte Sync Events
airbyte:readSync history as received from Airbyte's notifications, newest first.GET /client/v1/airbyte/sync-events
get_airbyte_stats
Get Airbyte Stats
airbyte:readAggregate sync statistics across all of this agency’s connections (volumes, success rates).GET /client/v1/airbyte/stats
get_airbyte_health
Get Airbyte Health
airbyte:readPer-connection health: latest sync plus the consecutive-failure streak.GET /client/v1/airbyte/health
get_airbyte_pipeline
Get Airbyte Pipeline
airbyte:readOne client's pipeline config: the connections in scope, enabled flag, run_hour_utc, and completion-webhook settings (the secret is never returned — only has_webhook_secret).GET /client/v1/airbyte/pipelines/:clientId
list_airbyte_pipeline_candidates
List Airbyte Pipeline Candidates
airbyte:readThis client's connections annotated with in_scope (already in the pipeline) and suggested (currently active — a reasonable default).GET /client/v1/airbyte/pipelines/:clientId/candidates
list_airbyte_pipeline_runs
List Airbyte Pipeline Runs
airbyte:readRecent pipeline runs for a client, newest first.GET /client/v1/airbyte/pipelines/:clientId/runs
get_airbyte_pipeline_run
Get Airbyte Pipeline Run
airbyte:readOne pipeline run with its per-connection steps — what synced, what failed and why, and whether the completion webhook was delivered.GET /client/v1/airbyte/pipelines/:clientId/runs/:runId
update_airbyte_config
Update Airbyte Config
airbyte:writeSet the origins the OAuth consent flow may redirect the browser back to (replaces the stored list).PATCH /client/v1/airbyte/config
provision_airbyte
Provision Airbyte Workspace
airbyte:writeProvision (or adopt) this agency's Airbyte workspace.POST /client/v1/airbyte/config/provision
register_airbyte_notifications
Register Airbyte Notifications
airbyte:writePoint this agency's Airbyte workspace at Mythic's sync-notification receiver.POST /client/v1/airbyte/config/notifications
create_airbyte_webhook
Create Airbyte Webhook Subscription
airbyte:writeSubscribe an agency URL to relayed sync notifications (Mythic keeps Airbyte's single webhook slot and forwards).POST /client/v1/airbyte/webhooks
delete_airbyte_webhook
Delete Airbyte Webhook Subscription
airbyte:writeRemove one relay subscription.DELETE /client/v1/airbyte/webhooks/:id
create_airbyte_connection
Create Airbyte Connection
airbyte:writeCreate a source + connection for one client.POST /client/v1/airbyte/connections
replace_airbyte_connection
Replace Airbyte Connection Settings
airbyte:writePUT a connection's settings: every field you send replaces what is stored, and streams in particular replaces the ENTIRE enabled-stream list — a stream you leave out stops syncing, so send the complete set…PUT /client/v1/airbyte/connections/:id
delete_airbyte_connection
Delete Airbyte Connection
airbyte:writeDelete a connection (and its Airbyte source).DELETE /client/v1/airbyte/connections/:id
trigger_airbyte_sync
Trigger Airbyte Sync
airbyte:writeStart a sync job on one connection now, regardless of its schedule.POST /client/v1/airbyte/connections/:id/sync
set_airbyte_schedule
Set Airbyte Schedule
airbyte:writeChange one connection's own Airbyte schedule.PATCH /client/v1/airbyte/connections/:id/schedule
initiate_airbyte_oauth
Initiate Airbyte OAuth
airbyte:writeStart the OAuth handoff for an OAuth-capable platform.POST /client/v1/airbyte/oauth/initiate
set_airbyte_pipeline
Set Airbyte Pipeline
airbyte:writeCreate or update a client's pipeline (orchestrated daily sync of a set of connections, driven by Mythic's cron, with a signed completion webhook once the whole set is done).PUT /client/v1/airbyte/pipelines/:clientId
start_airbyte_pipeline_run
Start Airbyte Pipeline Run
airbyte:writeStart a pipeline run now instead of waiting for run_hour_utc.POST /client/v1/airbyte/pipelines/:clientId/runs
airbyte_pipeline_run_action
Airbyte Pipeline Run Action
airbyte:writeAct on one pipeline run.POST /client/v1/airbyte/pipelines/:clientId/runs/:runId/retry
POST /client/v1/airbyte/pipelines/:clientId/runs/:runId/force
POST /client/v1/airbyte/pipelines/:clientId/runs/:runId/redeliver

Agency Rollups

The client roster and cross-location stats, usage, quota, destination health and contract summaries.

Agency-wide keys only — a key bound to one client cannot hold this scope.

ToolScopeWhat it doesProxies
get_agency_stats
Get Agency Stats
agency:readCross-location rollup for the whole agency: one row per location with event volume, unique users, unique sessions over a date window, plus the all-time live person count.GET /client/v1/agency/stats
get_agency_destination_health
Get Agency Destination Health
agency:readDelivery health of every location's activation destinations over a trailing window — one row per (location, destination) with success rate, failure counts, and the last error.GET /client/v1/agency/destinations/health
get_agency_contracts_summary
Get Agency Contracts Summary
agency:readPer location: how many event contracts are declared, whether the daily contract-alert webhook is configured, and when the last alert fired.GET /client/v1/agency/contracts/summary
get_agency_usage
Get Agency API Usage
agency:readThe agency's own API + MCP usage, daily per location/surface/route: request counts, auth failures, rate-limited and error counts, and latency.GET /client/v1/agency/usage
get_agency_quota
Get Agency Plan & Event Quota
agency:readThe agency's plan, the features it includes, and month-to-date ingested events against the quota.GET /client/v1/agency/quota