Give an approved AI client read-only analytics—not production authority.

The current remote MCP surface is site-bound GA4 reporting. Its bearer token can list property context and run authorized Analytics reports; approval, publishing, credentials and branch controls are deliberately absent.

Choose Growth Review Developer Workflows

Nothing publishes without approvalPaid product accessNo ranking guarantees

scope: ga4:read

tool: run_report

site: sf_site_•••

publish tools: none

Exact capability

Initialize an MCP session, list the GA4 reporting tools exposed by SEOForge and run reports against the site’s selected active GA4 connection.

Requested access

A separately issued SEOForge MCP bearer token with the single ga4:read scope; browser clients must also satisfy allowed-origin policy.

Cannot

Approve, merge, deploy, publish, retrieve credentials, bypass protection, switch to another site or access general SEOForge operations not exposed by the current GA4 server.

Token protection

Opaque, hashed and revocable.

Raw token is shown only when created
Only a keyed hash is stored
Token binds to one site and explicit scope
Provider OAuth grant never reaches the MCP client
Revocation invalidates the token immediately

Setup

Connect GA4 before issuing a client token.

01
Choose Growth or Agency capacity
Evidence, owner and next state remain visible.
02
Connect and select the site’s GA4 property
Evidence, owner and next state remain visible.
03
Create a labeled MCP token in settings
Evidence, owner and next state remain visible.
04
Configure the remote endpoint and bearer token
Evidence, owner and next state remain visible.
05
Run a bounded report and verify site context
Evidence, owner and next state remain visible.

Example workflow

An approved assistant compares landing-page observations.

The client calls run_report for organic sessions and key events across two declared date ranges. SEOForge executes against the site-bound GA4 grant and returns the provider result; the client receives no Google refresh token and cannot request a site change.

Limitations

This is not a general-purpose production MCP and currently exposes GA4 reporting only. GA4 data-quality, privacy and attribution constraints still apply. Token rotation and client-side secret storage remain the customer’s responsibility.

Questions

Know the boundary before connecting production.

Can the MCP client approve an SEO proposal?+

No. Production approval is intentionally unavailable through MCP.

Does the MCP token replace Google OAuth?+

No. The site must already have an active customer-owned GA4 connection.

Paid deployment · human authority

Use AI clients for scoped analysis, not hidden deployment.

Choose Growth or Agency, connect GA4 and issue only the site-bound token the client needs.

Choose Your Plan Book a Demo