Reference
MCP reference
Every capability is an MCP tool. Your agent discovers and calls them directly.
Registry (design-time)
register_metric(project, { key, name, purpose, category, tags?, type, source })
update_metric(project, key, patch) // including activation { status: 'active' }
delete_metric(project, key) // refused while a funnel references it
list_metrics(project, { status?, category? })
register_entity_type(project, { name, description, prop_schema? })
define_funnel(project, { key, name, goal, steps, window_seconds })
list_funnels(project)
delete_funnel(project, key)
Analysis (query-time)
query_trend(project, { metric, date_from, date_to?, interval, breakdown?, env? })
query_funnel(project, { funnel | steps, date_from, date_to?, env? })
query_retention(project, { start_metric, return_metric?, interval, periods, date_from, env? })
query_lifecycle(project, { metric, interval, date_from, env? })
query_stickiness(project, { metric, interval, date_from, env? })
query_entities(project, { entity_type, filters?, limit, order_by? })
get_person(project, { distinct_id, env? })
Operations
sample_events(project, { event?, registered?, distinct_id?, limit })
list_ingest_warnings(project, { env?, kind? }) // rejected / unregistered / clock_skew
create_insight(project, { title, body, query })
Browser Experience
create_experience_surfacedeclares an active, purpose-tagged surface.list_experience_surfacesandarchive_experience_surfacemanage its lifecycle.query_interaction_mapaggregates labelled click cells for a safe route key.get_experience_sessionreturns one known consented session timeline.
These tools expose labelled interactions, normalized coordinates, scroll milestones, safe route keys, and coarse error types. They do not expose DOM snapshots, input values, raw URLs, cursor recordings, gaze, stack traces, or error messages.
Keys
pk_— ingest, write-only, safe in client code (encodes project + env).sk_— secret, scoped to one project, read + manage.pt_— personal, org-wide, for MCP.