Author-tested GTM intelligence, attribution, and activation platform spanning advertising, analytics, and marketing automation, with a first-party MCP surface.
Concrete capability record
A concrete inventory separated by evidence type: first-party product documentation, named connector documentation, and Harry Hawk’s direct MCP tool-catalog test.
Leads and contacts; accounts; opportunities; campaigns and spend; funnel stages and stage movement; journeys and touchpoints; meetings and engagement signals; attribution and conversion paths; pipeline and bookings; forecasts and pacing; propensity scores, personas, enrichment, and LinkedIn context; connector and synchronization state; Reverse ETL pipelines; and SQL-queryable reporting, entity, and attribution output tables.
The tested MCP catalog retrieves lead, account, opportunity, and visitor detail; entity journeys; meeting intelligence; engagement signals; funnel health and cohort movement; pipeline and booking trends; campaign metrics and attribution; conversion paths; incrementality and lift; campaign reallocation; marketing-mix contribution and response curves; buyer personas; prospects; and LinkedIn context. Separately, first-party documentation describes customer-accessible BigQuery reporting and attribution tables that can be queried by BI tools, plus Enterprise data-warehouse access including BigQuery and Snowflake. This is warehouse-mediated query access, not direct SQL access to RevSure's internal operational store.
The tested catalog includes LinkedIn connection, messaging, and post-engagement actions. Separately from MCP, RevSure documents governed writebacks and Reverse ETL for scores, enrichment, attribution outputs, entity and reporting tables, audiences, and activation data. Named destination classes include CRM and MAP systems, outreach and advertising platforms, warehouses and lakes, CDPs, object stores, on-premises SQL Server or Oracle through SSIS or JDBC, custom APIs, and webhooks. Do not infer that every platform writeback is exposed as an MCP tool in every tenant.
The MCP page documents scoped, revocable token authentication, role-based read/write scopes, PII masking, and an audit ledger. Connector documentation describes OAuth or key-based authentication with least-privilege scopes; the Claude setup guide documents OAuth client configuration.
The documented Safe Autonomy sequence is propose, approve, commit, and roll back. The MCP page says every read, write, and decision is logged. Connector documentation adds source-parity validation, connector health, last-sync time, rows processed, and error logs.
RevSure’s public MCP page describes capability and governance families but does not publish a canonical tool-name manifest. The 67-name catalog below is a tenant-specific direct-test snapshot from July 10, 2026; availability can vary by tenant, plan, configuration, role, and server release. Data-warehouse access and advanced Reverse ETL are plan and deployment dependent. Destination-specific scopes, field mappings, identity matching, cadence, deduplication, failure recovery, and whether an action is exposed through MCP, API, webhook, or a managed connector must be verified before implementation.
Direct MCP catalog observation
Observed mounted MCP catalog · captured Jul 10, 2026. The namespace was observed directly; this audit did not execute every tool. It is not a claim that public documentation publishes a permanent universal manifest.
account_detailsaccount_enrichmentaccount_journeyget_account_prospectsget_opportunity_contactslead_detailslead_enrichmentlead_journeyopportunity_detailsopportunity_journeyvisitor_detailsvisitor_journeyget_engagement_signalsget_meeting_detailsget_meetingsbooking_daily_trendscohort_movementcohort_stage_viewcohort_trenddaily_pacing_daily_breakdowndaily_pacing_stage_metricsfunnel_additionsfunnel_health_metricsopen_pipeline_trends_by_close_quarterpipeline_generation_trendspipeline_progression_trendsaggregate_journeyaggregate_journey_drilldownaggregate_journey_entitiesaggregate_touchpointaggregate_touchpoint_compositionaggregate_touchpoint_drilldowncampaign_metrics_with_attributioncampaign_metrics_without_attributionconversion_attributionconversion_pathdeep_funnel_creation_attributiondeep_funnel_leakage_attributiondrill_down_without_attributionacross_campaign_lift_analysiscampaign_reallocationconversion_lift_analysisincrementality_prepost_analysisindividual_campaign_lift_analysismmx_channel_bar_trendsmmx_channel_performance_comparisonmmx_channel_performance_trendsmmx_contribution_by_channelmmx_contribution_by_quartermmx_marketing_movementmmx_response_curve_analysisget_account_linkedin_dataget_buyer_personasget_person_linkedin_datalinkedin_connect_accountlinkedin_engage_with_postlinkedin_get_user_postslinkedin_send_connection_requestlinkedin_send_messageaccount_engagement_trendsfind_matching_dimensionsget_calendar_configget_funnel_stagesget_parameter_optionsinit_contextrecall_memoryremember_memoryFirst-party connector catalog
Connectors feed RevSure’s governed context layer. They are not automatically equivalent to individual MCP tools.
First-party access
Agent access
Role: provider
Read scope: Lead, account, opportunity, prioritization, journey, predictive and attribution context; policy-governed workflow activation and selected GTM writebacks through the RevSure Data Graph
Write scope: State-changing tools are present in the documented scope; review the official tool catalog and require confirmation for consequential actions.
Authentication: First-party product and setup pages confirm OAuth-connected MCP access and policy controls.
Approval boundary: First-party product and setup pages confirm OAuth-connected MCP access and policy controls.
Confirm the current tool catalog, plan, region, scopes, rate limits, terms, and write behavior before implementation.
Editorial assessment
A comparative architecture lens—not a quality score, market ranking, or buying recommendation. Scale: 1–5.
Proposed interfaces
These are design proposals derived from documented access—not claims that RevSure ships these experiences.
Evidence and dates
“Publisher updated” is shown only when the page exposes an update date. “BYO-UI reviewed” records when this research checked the reference. A missing publisher date is reported as missing—not replaced with the review date.
First-party product and setup pages confirm OAuth-connected MCP access and policy controls. Public documentation does not expose a complete canonical tool manifest, so operation-level claims should carry medium…
Targeted first-party MCP/agent-role review; broader API inventory retained
First-party product homepage used to confirm product identity and current positioning.
Inventory source: structurally normalized; content was not individually reopened in this pass.
REST API access with tenant and region-specific base URLs, API-token authentication, documented resources, errors, and examples.
Targeted first-party access review
Warehouse-mediated query access to customer-facing output tables; not direct SQL access to RevSure's internal operational store.
Targeted first-party access review
Enterprise plan evidence for Reverse ETL and BigQuery, Snowflake, and other data-warehouse access.
Targeted first-party access review
CRM, outreach, advertising, warehouse and lake, CDP, object-store, on-premises database, custom API, and webhook writeback evidence.
Targeted first-party access review
Partner-specific enrichment request and response webhooks with documented retries and provisioned endpoints.
Targeted first-party access review
Named CRM, MAP, advertising, analytics, warehouse, collaboration, intent, enrichment, and engagement integrations.
Targeted first-party connector review
Authentication, historical sync, writebacks, validation, connector health, rows processed, and errors.
Targeted first-party access review
Targeted first-party documentation review
Targeted first-party documentation review
Tied to the representative first-party source or targeted access review.
Official links recorded for deeper research but not necessarily reopened endpoint by endpoint.
System role, maturity interpretation, and architectural boundary.
Interface patterns and compositions—not vendor product claims.