Google tag manager MCP server: MCP server, setup and security

What Google tag manager MCP server does

According to its repository: “Interface to the Google Tag Manager API.”

An MCP server gives an AI agent extra tools it calls during the conversation: the agent reads their description, decides to use them and gets the result back. Google tag manager MCP server is listed under Marketing and SEO, a category of 63 servers in the directory, where it ranks #6 by stars.

Topics declared by the repository: gtm, gtm-server-side, stape.

Installing and connecting Google tag manager MCP server

No package or remote server is declared in the official MCP registry: you install it from source, following the repository README.

Like any MCP server, you declare it in your client's configuration (Claude Desktop, Claude Code, Cursor, VS Code, Codex…): a name, the command that starts it or its URL, and any environment variables. The client then starts it and lists its tools. Project language: TypeScript.

Security: what to check

An MCP server runs code with the rights you give it, and the model reads its tool descriptions: a malicious or compromised server can hijack the agent. Read the code, or pick a maintained and widely used server, before connecting it.

None of the risk signals we track (system access, secrets, missing licence, abandonment) applies to Google tag manager MCP server. That does not replace reading the code.

Good practice: grant only the rights needed (least privilege), require human approval for irreversible actions, and run the AI agent security check.

Project activity and maintenance

Created on April 16, 2025, the stape-io/google-tag-manager-mcp-server repository has 238 stars and 65 forks, with 0 open issues. It has more stars than 80% of the servers in the directory. It received changes this month.

Stars measure attention, not quality: a recent, heavily promoted project can collect them fast, while a useful but niche server will have few.