Built-in Workspace Features: Tracking Snippet, REST API and MCP
A single dashboard cannot do everything. EndFrame's read-only REST API and MCP server, switched on from the dashboard, connect your conversion tracking data to the rest of your stack.
In short
EndFrame's built-in workspace features are the tracking snippet, a read-only MCP server for AI agents, and a read-only REST API for external systems. The snippet collects whenever it is installed on your site; to stop collection, remove it. The REST API and MCP server switch on and off from the dashboard without engineering work, and switching one off rejects its requests. Both are governed by the same roles and API keys as everything else. There are no paid add-ons, and the REST API and MCP server work on paid plans.
Every team's stack is different. Some run everything through a BI tool. Others have AI agents pulling data from a dozen sources. A single dashboard trying to be everything to everyone ends up being mediocre at all of it. The better model is a focused core product with a clear way to get data out of it.
Why extensibility matters for conversion tracking
Conversion tracking platforms sit at the center of a marketing team's data flow. Data comes in from campaigns and tracking. Insights go out to reports, BI dashboards, AI agents, and operational tools. If the tracking platform is a dead end with no way to get data out programmatically, it becomes a silo, which is exactly the problem it was supposed to solve.
How built-in features work
The dashboard lists the workspace's built-in features with a toggle for each. Each one extends your workspace in a specific direction without requiring engineering work or custom integration code. Enable the REST API or MCP server and it accepts requests immediately. Disable it and its requests are rejected, the sidebar adjusts, and the feature is removed from view. The tracking snippet keeps collecting wherever it is installed.
What is available today
- 1MCP Server: Exposes 8 read-only JSON-RPC tools so AI agents can query your campaigns, domains, goals, conversions, visits, and analytics directly using the Model Context Protocol.
- 2Tracking snippet: The EndFrame JavaScript snippet that records page views, sessions, clicks, form submissions, and custom events on your website. It runs in a web page, so it cannot track email opens.
- 3REST API: Read-only programmatic access to your EndFrame workspace — pull analytics, list campaigns and domains, and read goals and conversions for BI tools or custom dashboards.
A workspace that adapts
These features are not bolted on. The workspace knows which ones are enabled and adapts accordingly: the sidebar shows navigation only for the features that are switched on, and API keys for the REST API and MCP server are managed on the Developers page. The workspace stays focused, so teams that switch a feature off do not see it cluttering their sidebar, while teams that rely on it get first-class access to its controls.
The best platform is not the one that does everything built-in. It is the one that does its core job well and gets out of the way when you need to connect it to something else.
Extending without overcomplicating
The pattern stays the same for every feature: toggle it on, configure it from the dashboard, and start using it. No vendor calls, no custom development, no waiting. Conversion data should flow wherever your team needs it, and these switches are how EndFrame makes that possible without turning the core product into something bloated.
Frequently asked questions
Which built-in features can I switch on?
The tracking snippet that collects visits and events on your site, a read-only MCP server for AI agent integration, and a read-only REST API for programmatic access to analytics, campaigns, domains, goals, and conversions. Server-side destinations for Meta, GA4, TikTok, and webhooks are configured on the Server-side Pixels page.
Do these features cost extra?
No. There are no paid add-ons. The REST API and MCP server authenticate with API keys and work on paid plans; the free trial does not include API access. Check the pricing page for current plan limits.
Can I turn these features on and off?
The REST API and MCP server can. Switch one off and its requests are rejected and the sidebar adapts. The tracking snippet is different: it keeps collecting for as long as it is installed on your site, so remove it from the site to stop collection.
Try EndFrame
Add a server-side path for your conversions.
EndFrame collects events first-party and forwards conversions server-side to Meta, GA4, TikTok, and webhooks with event-ID deduplication — then credits each conversion to its campaign, with the visit-to-conversion path you can audit.
No credit card required