Every change Wellknown observed on this MCP server, newest first, with what it was before and what it became. Tool-surface changes carry the definition diff. Nothing here is edited after the fact.
Added "create_artifact", "create_insights_report", "edit_artifact" and 4 more; changed the definition of "query_replo_analytics" (77 tools before, 84 now)
⟨10 unchanged words⟩ traffic, conversion, revenue, and session-level questions. No saved Insights report is required. Use this for ad hoc questions or when list_insights_reports finds no relevant report; an empty report list does not mean analytics are unavailable. Queryable public tables are session_attribution, events_computed, currency_exchange_rates, ⟨84 unchanged words⟩
Create artifact — Create a saved Replo artifact from instructions, existing reports, analytics, or files. Starts an asynchronous internal-agent operation using normal Replo tools and connected integrations. Poll get_agent_session; its final message contains the saved result ID and link after validation. Use the same tool with sessionId for follow-up instructions. Reuse operationId only for an identical retry. Creation is private by default; sharing requires an explicit request. For artifacts, the result is a native HTML artifact in Files. Asking a question alone does not require creating anything.
Create Insights report — Create a saved Replo Insights report from instructions, existing reports, analytics, or files. Starts an asynchronous internal-agent operation using normal Replo tools and connected integrations. Poll get_agent_session; its final message contains the saved result ID and link after validation. Use the same tool with sessionId for follow-up instructions. Reuse operationId only for an identical retry. Creation is private by default; sharing requires an explicit request. For artifacts, the result is a native HTML artifact in Files. Asking a question alone does not require creating anything.
Edit artifact — Edit an existing saved artifact in place, preserving its identity and sharing. Requires write permission. Starts an asynchronous internal-agent operation using normal Replo tools and connected integrations; poll get_agent_session for progress, questions, failures, and the validated result link. Follow-up instructions use the same sessionId and target. Reuse operationId only for identical retries.
Edit Insights report — Edit an existing saved Insights report in place, preserving its identity and sharing. Requires write permission. Starts an asynchronous internal-agent operation using normal Replo tools and connected integrations; poll get_agent_session for progress, questions, failures, and the validated result link. Follow-up instructions use the same sessionId and target. Reuse operationId only for identical retries.
Get Insights report — Read an existing report's definition, formulas, SQL, data sources, permissions, and resolved default scope. Accepts a report ID from list_insights_reports or the final UUID in an Insights URL. This returns the definition, not executed data. Call query_insights_report for data and explain the results directly to the user.
List Insights reports — Discover accessible private, team-shared, and individually shared Insights reports in a project. Follow nextOffset until null, even after an empty page. If no relevant report exists, use query_replo_analytics to answer the question directly; a saved report is not required. Use get_insights_report for definitions and query_insights_report for current results.
Query Insights report — Execute saved report queries using the same formulas and scope compiler as the Insights UI. Optionally override dates, comparison, filters, or breakdown. Returns structured rows and individual query errors. Check integration status for external sources; missing data is not measured zero. Use these results to answer questions or create a native artifact with create_artifact. Reading or querying does not create a report or artifact.
Changed the definition of "get_integration_status" and "query_replo_analytics"
⟨16 unchanged words⟩ with a dashboard URL for setup when available. externalAnalytics lists supported SQL views and their maximum cache age, not proof the connection can fetch metrics. Check this before querying external metrics, including when a provider's tools are absent from your catalog. Analytics integration keys include triple-whale, contentsquare, intelligems, google-analytics, google-search-console, shopify, and converge. connectFailureMessage explains a failed connection attempt. isAlwaysAvailable identifies ⟨19 unchanged words⟩
⟨55 unchanged words⟩ see the Replo Public API analytics query docs. Also supports connected external metrics through the parameterized views listed in the query input schema. Check get_integration_status before querying; external data can be cached for eight hours and an empty result does not prove zero activity. Use provider tools for discovery or provider-native reports.
Unknown → Live
First tool surface recorded: 77 tools (server version 1.0.0)
https://api.replo.app/v1/mcp (mcp_streamable_http) — from mcp_registry, with the record
Showing the latest 5 events. The API returns up to 500 and filters by kind: ?kind=tool_surface_changed
⟨406 unchanged words⟩ Float64),\n unique_purchasing_sessions_state AggregateFunction(uniq, UUID)\n)\n```\n```\n\nExternal metrics (OAuth MCP and public API keys):\nParameterized views: triplewhale_metrics_daily, triplewhale_metrics_totals, triplewhale_metrics_list, contentsquare_metrics_daily, contentsquare_metrics_totals, contentsquare_metrics_list, mixpanel_metrics_daily, mixpanel_metrics_totals, mixpanel_metrics_list, intelligems_metrics_daily, intelligems_metrics_totals, intelligems_metrics_list, intelligems_experience_metrics_daily, intelligems_experience_metrics_totals, intelligems_experience_metrics_list, replo_roi_monthly, shopify_sales_monthly, google_analytics_report, google_search_console_report.\nUse named since/until dates (YYYY-MM-DD, inclusive). Google report and ROI views also require settings JSON; Intelligems experience views require experience_id. Credentials and project scope are injected server-side: never supply auth_token or project_id.\nIn MCP, call get_integration_status first for connection IDs, setup links, and supported views. Missing or misconfigured integrations can return zero rows: do not report that as measured zero activity. Use provider-specific tools for metric/property discovery and detailed provider-native reports.\nExternal results can be cached for up to eight hours. GA4 and Search Console report views cap provider results at 10,000 rows; narrow dates or dimensions if exceeded. Match currencies, reporting timezones, and attribution definitions before combining sources.","minLength":1,"type":"string"} ⟨5 unchanged words⟩