JP Agent Tracking Bridge MCP

The JP Agent Tracking Bridge MCP lets a compatible AI agent (Hermes, Claude, Codex) work with Google Analytics and Google Tag Manager through JP Agent Tracking Bridge — using your Google account, never a service account.

AI agent
   └─ jptb-google-tools (this MCP server)
        └─ HTTPS → JP Agent Tracking Bridge Google Tools gateway (jpro.studio)
                      ├─ validates your active Bridge session
                      ├─ uses YOUR Google OAuth connection (encrypted server-side)
                      └─ Google Analytics + Google Tag Manager

The agent never sees your Google tokens, your client secret, or any encryption key.

Requirements

• A licensed, installed JP Agent Tracking Bridge site (WordPress or Joomla).

• A Google account with access to the site's GA4 property and GTM container.

• A compatible agent (Hermes, Claude Desktop, or Codex).

No service account, no JSON credentials, no Google Cloud setup.

Related MCP server: Google Tag Manager MCP Server

The 5-step customer story

1. Install/register this MCP once (below).

2. Connect Google in the site's JP Agent Tracking Bridge admin.

3. Start Tagging to open a temporary agent connection.

4. Give the agent the connection (connection id + session token).

5. Talk to the agent normally — it inspects and configures tracking, and asks before publishing anything to GTM.

Installation

Install the MCP server once:

uvx --from 'git+https://github.com/joomlapro/jp-agent-tracking-bridge-mcp.git' jptb-google-tools

Then register it in your agent. See docs/HERMES.md, docs/CLAUDE.md, or docs/CODEX.md for the exact per-agent setup.

Configuration

The server needs two values for a given job (also passable per tool call):

export JPTB_CONNECTION_ID="<connection id from 'Connect Google'>"
export JPTB_SESSION_TOKEN="<session token from 'Start Tagging'>"

Both are shown/generated in the site's JP Agent Tracking Bridge admin and via the Bridge API. The session_token is revoked by Stop Tagging, which immediately blocks all Google operations through the MCP.

What the agent can do

• GTM read — list accounts/containers/workspaces/tags/triggers/variables/versions.

• GTM write — create/update JPTB tags, triggers, variables; create a container version.

• GTM publish — publish a prepared version (approval-gated; the agent asks first).

• GA4 read-only — list accounts/properties, property details, realtime and standard reports.

Security model

• Session-bound — Google access is tied to an active Bridge session; Stop Tagging revokes it.

• No secrets to the model — tokens, client secret, and the encryption key stay server-side.

• No service account — the customer's own Google OAuth authorization is the only credential.

License

MIT.