Gtm MCP Server

MCPAI代理

提供方 未标注

AI代理 HTTP · 远程 OAuth 授权 社区 / 第三方

全面解析Gtm MCP ServerMCP Server的核心功能、安装配置和实用案例。作为顶级Model Context Protocol服务器,Gtm MCP Server能让AI助手访问实时数据、执行操作,为您提供更智能的工作体验和自动化解决方案。

一句话选型结论

按资料字段整理

Gtm MCP Server 属于AI代理类 MCP 服务器,HTTP · 远程,OAuth 授权,没有现成安装命令,需按官方文档接入。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类AI代理 传输方式HTTP · 远程 鉴权OAuth 授权 部署方式远程部署
GitHub 星标 未标注 仓库热度,无公开仓库时显示未标注
工具数 未标注 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

AI代理
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量未标注暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

安装与配置

HTTP · 远程 OAuth 授权
连远程 HTTPS 端点,通常为 Streamable HTTP
  1. 1
    准备运行环境

    确认你的客户端支持远程端点,并拿到服务地址。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后随便调一个只读工具,确认能返回结果,再接入正式流程。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
给代理接外部能力

让代理在任务中途调用搜索、数据库等真实工具。

多步任务编排

把一串操作拆成步骤,由代理按顺序执行。

自动化重复流程

把固定流程交给代理跑,减少手工操作。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 基础信息齐全,可以先按官方文档接入试跑。

先想清楚的地方

  • 远程端点依赖网络与服务方可用性,注意密钥与调用额度。
  • 没有现成安装命令,需要按官方文档自己填启动命令和参数。
  • 使用前要准备好OAuth 授权对应的凭据,并按最小权限配置。
  • 资料没标注工具数量,实际能力要装好后确认。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在AI代理场景里让模型直接调用外部能力的人。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 不方便管理密钥或第三方授权的人。
  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
Gtm MCP Server当前 未标注 HTTP · 远程 远程部署 无 2026-05-17
Filesystem 560c4363 13 未标注 本地部署 无 2026-05-17
Server Everything (everything) 11 stdio · 本地进程 本地部署 有 2026-05-17
Time 7365cb6d 2 SSE · 服务端推送 远程部署 有 2026-05-18
Everything Claude Code 未标注 stdio · 本地进程 本地部署 有 2026-05-17
Openmemory 557e1585 未标注 stdio · 本地进程 本地部署 有 2026-05-17

服务器档案

AI代理
字段来自项目仓库与公开索引,中文说明由本站标注
提供方未标注上游标注的维护方 未标注
分类AI代理本站按上游分类展示
连接方式HTTP · 远程连远程 HTTPS 端点,通常为 Streamable HTTP
鉴权方式OAuth 授权远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时未标注 · 未标注本地安装时用到的包标识与运行时
部署类型远程部署上游给出的部署形态
最近核验2026-05-17上游最后核验时间

详细介绍

23.6 KB
来自项目仓库与上游目录的原文,未做删改

GTM MCP Server


> [!IMPORTANT]
> The hosted instance at https://mcp.gtmeditor.com will be shut down on November 30, 2026. See #139 for details. Thanks to everyone who used it!


GTM MCP Server connects MCP clients to the Google Tag Manager API. It can
inspect containers, create and update workspace entities, create versions, and
publish a selected version after explicit confirmation.

Use the hosted server at:```text
https://mcp.gtmeditor.com


The server supports browser-based Google OAuth for individual users and
service-account authentication for self-hosted automation.

## Project status

| Item | Current state |
|---|---|
| Version in `server.json` | `1.13.0` |
| Transport | MCP Streamable HTTP, or stdio for local service-account use |
| Runtime tools | 64 GTM tools by default; 94 with `GTM_TOOL_GROUPS=all`, plus 2 utility tools |
| MCP resources | 8 resource definitions |
| MCP prompts | 6 prompts |
| Official GTM API coverage | 101 of 106 methods |
| Hosted endpoint | `https://mcp.gtmeditor.com` |

The project implements 101 methods from Google's 106-method GTM v2 discovery surface. The five `accounts.user_permissions` methods are intentionally excluded because granting and revoking GTM access are security-related and it shouldn't be manager by an LLM.

## Connect an MCP client

Add the hosted URL as a remote HTTP MCP server. The client should discover the OAuth metadata, open Google sign-in, and reconnect with the issued bearer
token.

### Claude Code```bash
claude mcp add --transport http gtm https://mcp.gtmeditor.com

Gemini CLI```bash

gemini mcp add --transport http gtm https://mcp.gtmeditor.com


Gemini CLI can also use this `settings.json` entry:```json
{
  "mcpServers": {
    "gtm": {
      "httpUrl": "https://mcp.gtmeditor.com"
    }
  }
}

Cursor

Add the following to .cursor/mcp.json:```json
{
"mcpServers": {
"gtm": {
"url": "https://mcp.gtmeditor.com"
}
}
}


### ChatGPT, Codex, and Claude web

Add a custom or remote MCP connection in the client and use
`https://mcp.gtmeditor.com` as the server URL. Product menus change more often
than this server, so refer to the client's current MCP connection instructions
if the label differs.

After connecting, try:```text
List my GTM accounts, containers, and workspaces. Do not make changes.

The Google account used during OAuth determines which GTM accounts the server
can access.

Typical workflow

  1. Call list_accounts, list_containers, and list_workspaces to discover
    IDs. Do not guess IDs.
  2. Inspect the workspace with list/get tools or the audit_container prompt.
  3. Create or update tags, triggers, variables, templates, clients, or
    transformations in the selected workspace.
  4. Call get_workspace_status and resolve conflicts before versioning.
  5. Call create_version to snapshot the workspace.
  6. Inspect the saved version with get_version.
  7. Call publish_version with confirm: true only when the selected version
    is ready to go live.
  8. Verify the published state with get_live_version.

Example requests:

  • "Audit this workspace for duplicate tags and unused triggers."
  • "Create a GA4 purchase event tag, but do not publish it."
  • "Show the difference between the latest saved version and the live version."
  • "Generate a Markdown tracking plan from this workspace."
  • "Import the iubenda template from the Community Template Gallery."

Tools

All GTM tools use the authenticated Google identity from the current MCP
request. Inputs and outputs are structured JSON.

Utility

Tool Purpose
ping Test MCP connectivity
auth_status Check whether the current request is authenticated

Accounts and containers

Tool Purpose
list_accounts List accessible GTM accounts
update_account Rename an account
list_containers List containers and their public IDs and settings
lookup_container Find a container by destination ID or GTM public tag ID
get_container_snippet Get a web install snippet or server-container configuration
create_container Create a web, app, AMP, or server container
update_container Rename a container while preserving its other settings
delete_container Permanently delete a container; requires confirm: true
combine_containers Merge a source container into a target; requires confirm: true
move_tag_id Move a tag ID into a new container; requires confirmation and terms acceptance

Workspaces

Tool Purpose
list_workspaces List workspaces in a container
create_workspace Create a workspace
get_workspace Get workspace metadata and its current fingerprint
update_workspace Update selected workspace fields
delete_workspace Delete a workspace; requires confirm: true
quick_preview_workspace Compile an ephemeral preview without saving or publishing
get_workspace_status Show pending changes and merge conflicts
bulk_update_workspace Apply multiple entity changes; requires confirm: true
resolve_workspace_conflict Replace a conflict with a resolved entity; requires confirm: true
sync_workspace Synchronize with the latest container version; requires confirm: true

Bulk update and conflict resolution accept raw GTM Entity JSON so every entity
type supported by the official API remains available.

Tags

Tool Purpose
list_tags List workspace tags
get_tag Get complete tag details
create_tag Create a tag
update_tag Update a tag with fingerprint-based concurrency control
delete_tag Delete a tag; requires confirm: true

Triggers

Tool Purpose
list_triggers List workspace triggers
get_trigger Get complete trigger details
create_trigger Create a trigger
update_trigger Update a trigger with fingerprint-based concurrency control
delete_trigger Delete a trigger; requires confirm: true

For update_trigger, omit filterJson, customEventFilterJson,
autoEventFilterJson, or parameterJson to preserve the current field. Pass
the JSON string "[]" to clear a field, or a non-empty JSON array to replace
it. For click, link-click, and form-submission triggers, use filterJson because
GTM drops autoEventFilter for those trigger types.

Variables

Tool Purpose
list_variables List workspace variables
get_variable Get complete variable details
create_variable Create a variable
update_variable Update a variable with fingerprint-based concurrency control
delete_variable Delete a variable; requires confirm: true

Folders and built-in variables

Tool Purpose
list_folders List workspace folders
get_folder Get complete folder metadata
create_folder Create a folder
update_folder Update a folder with fingerprint protection
delete_folder Delete a folder; requires confirm: true
get_folder_entities List tags, triggers, and variables assigned to a folder
move_entities_to_folder Move tags, triggers, and variables; requires confirm: true
revert_folder Discard workspace folder changes; requires confirm: true
list_built_in_variables List enabled built-in variables
enable_built_in_variables Enable built-in variable types
disable_built_in_variables Disable built-in variable types; requires confirm: true

Use revert_workspace_entity to discard changes to a built-in variable.

Zones

Tool Purpose
list_zones List all zones across every result page
get_zone Get boundary, child-container, and type-restriction configuration
create_zone Create a workspace zone
update_zone Update selected fields with fingerprint concurrency control
delete_zone Delete a zone; requires confirm: true

Use revert_workspace_entity to discard changes to a zone.

Environments

The environments tool group is optional. Enable it with
GTM_TOOL_GROUPS=all or add environments to an explicit group list.

Tool Purpose
list_environments List all container environments across every result page
get_environment Get environment configuration and authorization metadata
create_environment Create a user environment
update_environment Update selected fields with fingerprint concurrency control
reauthorize_environment Rotate the authorization code; requires confirm: true
delete_environment Delete a user environment; requires confirm: true

The Live and Latest environments are managed by GTM. Creation and deletion
apply to user environments; GTM permits URL and debug updates on other types.

Destinations and Google tag configurations

These tools are in the optional destinations and gtag groups.

Tool Purpose
list_destinations List Google tag destinations linked to a container
get_destination Get a destination by its link ID
link_destination Move a destination to a container; requires confirm: true
list_google_tag_configs List Google tag configurations in a workspace
get_google_tag_config Get a Google tag configuration
create_google_tag_config Create a Google tag configuration
update_google_tag_config Update a configuration with fingerprint protection
delete_google_tag_config Delete a configuration; requires confirm: true

Container combine, tag-ID move, and destination link operations do not copy or
enable user permissions. Account permission management remains outside the
current parity target.

Custom templates

Tool Purpose
list_templates List custom templates
get_template Get template metadata and template code
create_template Create a custom template from .tpl code
update_template Update template code
delete_template Delete an unused template; requires confirm: true
import_gallery_template Import a Community Template Gallery template
get_tag_templates Return compact GA4 and Custom HTML input examples
get_trigger_templates Return compact trigger input examples

The full JSON examples live in the
gtm://best-practices/tool-input-formats resource so every tool listing does
not repeat them.

Server-side containers

Tool Purpose
list_clients List server-container clients
get_client Get a client
create_client Create a client
update_client Update a client
delete_client Delete a client; requires confirm: true
list_transformations List transformations
get_transformation Get a transformation
create_transformation Create a transformation
update_transformation Update a transformation
delete_transformation Delete a transformation; requires confirm: true

Use revert_workspace_entity to discard changes to a client or transformation.

Versions and publication

Tool Purpose
list_versions List all saved version headers across every result page
get_latest_version_header Get the latest saved header, which may differ from live
get_version Get a saved version and its complete entity collections
get_live_version Get the currently published version and its entities
create_version Create a version from a conflict-free workspace
publish_version Publish a selected version; requires confirm: true
update_version Update a saved version's name or description
delete_version Soft-delete a version; requires confirm: true
undelete_version Restore a soft-deleted version; requires confirm: true
set_latest_version Make a version Latest without publishing; requires confirm: true

Workspace reverts

Tool Purpose
revert_workspace_entity Discard workspace changes to a built-in variable, client, tag, template, transformation, trigger, variable, or zone; requires confirm: true

The tool fetches the current entity fingerprint before calling the matching
official revert method. A successful result can have existsAfterRevert: false
when the entity does not exist in the latest container version.

Safety model

  • Delete operations, publication, and disabling built-in variables require
    confirm: true.
  • Update operations fetch the current resource fingerprint and use Google's
    optimistic concurrency checks.
  • create_version first checks that the workspace has changes and no merge
    conflicts.
  • Read tools distinguish latest saved state from published live state.
  • Google API errors are mapped to clearer not-found, permission, conflict, and rate-limit failures. Retryable API failures use bounded backoff.
  • MCP request bodies are limited to 5 MiB. OAuth and dynamic registration
    endpoints have stricter rate and body limits.

Most entity edits affect a workspace and are not live until a version is
published. Account and container operations act directly on those resources.
Always review the target IDs and the generated version before publication.

Resources

The server exposes two concrete resources and six URI templates:

URI Content
gtm://accounts Accessible accounts
gtm://accounts/{accountId}/containers Containers
gtm://accounts/{accountId}/containers/{containerId}/workspaces Workspaces
gtm://accounts/{accountId}/containers/{containerId}/workspaces/{workspaceId}/tags Tags
gtm://accounts/{accountId}/containers/{containerId}/workspaces/{workspaceId}/triggers Triggers
gtm://accounts/{accountId}/containers/{containerId}/workspaces/{workspaceId}/variables Variables
gtm://best-practices Best-practice topic index
gtm://best-practices/{topic} One embedded guidance document

Best-practice topics include naming and organization, safe edits, GA4 and
consent, server-side containers, and detailed tool input formats.

Prompts

Prompt Purpose
audit_container Review tags, triggers, and variables for quality problems
generate_tracking_plan Build a Markdown tracking plan from a workspace
suggest_ga4_setup Recommend a GA4 structure from stated goals
find_gallery_template Guide Community Gallery discovery and import
best_practices_review Score a workspace against embedded guidance
plan_safe_edit Produce a staged edit/version/publish plan

Prompts prepare context and instructions for the model. They do not bypass tool authentication or mutation safeguards.

Authentication

Hosted OAuth

The hosted server implements MCP OAuth discovery and Google authorization. It
supports PKCE, Dynamic Client Registration, Client ID Metadata Documents,
authorization-server metadata, and protected-resource metadata.

The server never receives a Google password. It receives Google OAuth tokens
after consent. A self-hosted operator can keep issued MCP and Google tokens
across restarts by setting TOKEN_STORE_PATH; without that setting they remain in memory and disappear when the process stops.

Expired MCP access tokens can be renewed transparently while their Google
refresh credentials remain valid. AUTH_AUTO_REFRESH_MAX_AGE limits how long
one bearer can be silently extended; its default is seven days.

Service-account mode

Service-account mode gives every holder of one server API key the GTM access
granted to the configured Google service account.

  1. Create a Google service account.
  2. Add its email address to the required GTM account with only the permissions
    it needs.
  3. Set a strong SERVICE_ACCOUNT_API_KEY on this server.
  4. Set GOOGLE_SERVICE_ACCOUNT_KEY_JSON to the key JSON, or use Application
    Default Credentials on Google Cloud.
  5. Configure the MCP client to send
    Authorization: Bearer.

OAuth and service-account mode can run together. Requests with the configured
API key use the service account; OAuth users keep their own Google identity and GTM permissions.

Stdio mode

For a single local MCP client, the server can run over stdin/stdout instead of
HTTP. The client starts the process when it needs GTM and stops it when the
session ends, so no long-running server or API key is required. Stdio mode
always uses service-account credentials:```sh
GOOGLE_APPLICATION_CREDENTIALS=/path/to/sa.json gtm-mcp-server --stdio


Claude Code example (`.mcp.json`):```json
{
  "mcpServers": {
    "gtm": {
      "command": "/usr/local/bin/gtm-mcp-server",
      "args": ["--stdio"],
      "env": {
        "GOOGLE_APPLICATION_CREDENTIALS": "/path/to/sa.json",
        "GTM_TOOL_GROUPS": "all"
      }
    }
  }
}

MCP_TRANSPORT=stdio is equivalent to the --stdio argument. Logs go to
stderr; stdout carries only MCP messages.

Self-hosting

Requirements

  • Go 1.26 or Docker
  • A Google Cloud project with the Tag Manager API enabled
  • A Google OAuth web client for user OAuth, or a Google service account for S2S
  • HTTPS and a stable public URL for remote OAuth deployments

Google OAuth setup

Create an OAuth 2.0 Web application in Google Cloud and add this authorized
redirect URI:```text
https://your-host.example/oauth/callback


The scheme and host must match `BASE_URL` exactly. For local development, use:```text
http://localhost:8080/oauth/callback

Run from source```bash

git clone https://github.com/paolobietolini/gtm-mcp-server.git
cd gtm-mcp-server

cat > .env <<'EOF'
BASE_URL=http://localhost:8080
GOOGLE_CLIENT_ID=your-client-id.apps.googleusercontent.com
GOOGLE_CLIENT_SECRET=your-client-secret
TOKEN_STORE_PATH=./data/tokens.json
EOF

go run .


The repository reads `.env` and then `.env.local`; `.env.local` overrides
`.env`. Both are ignored by Git.

### Run with Docker```bash
docker build -t gtm-mcp-server .

docker run --rm \
  --name gtm-mcp-server \
  -p 8080:8080 \
  --env-file .env \
  -v gtm-mcp-tokens:/data \
  gtm-mcp-server

When using the named volume, set TOKEN_STORE_PATH=/data/tokens.json in
.env.

Configuration

Variable Default Purpose
PORT 8080 HTTP listen port
BASE_URL http://localhost:8080 Canonical public URL used by OAuth metadata and callbacks
MCP_TRANSPORT http http (Streamable HTTP) or stdio; the --stdio argument overrides it
MCP_STATELESS_HTTP true Disable in-memory MCP HTTP sessions; required for MCP 2026-07-28
DASHBOARD_ENABLED false Expose the public connection setup page at /dashboard/
GOOGLE_CLIENT_ID empty Google OAuth web-client ID
GOOGLE_CLIENT_SECRET empty Google OAuth web-client secret
ACCESS_TOKEN_TTL 8h Lifetime of MCP access tokens
AUTH_AUTO_REFRESH_MAX_AGE 168h Maximum silent-renewal chain age
TOKEN_STORE_PATH empty Optional persisted token-store file
SERVICE_ACCOUNT_API_KEY empty Bearer API key that enables S2S mode
GOOGLE_SERVICE_ACCOUNT_KEY_JSON empty Service-account JSON; omit when ADC is available
ALLOWED_HOSTS empty Additional trusted hosts for Docker/internal URL resolution
TRUST_PROXY false Trust the rightmost X-Forwarded-For hop for rate limiting
LOG_LEVEL info Set debug for additional structured logs
GTM_TOOL_GROUPS current groups Comma-separated tool families advertised through MCP

If OAuth and service-account credentials are both absent, the server starts in
open mode. Use open mode only for isolated local development.

Streamable HTTP is stateless by default: the server keeps no in-memory MCP
session and ignores Mcp-Session-Id, so requests can reach any replica or
survive a restart. This is required for MCP 2026-07-28 tool requests; legacy
MCP 2025-11-25 clients remain supported. Stateless mode does not disable
authentication: send credentials on every MCP request. Set
MCP_STATELESS_HTTP=false only if a client depends on HTTP sessions or the
GET event stream; this server makes no server-to-client requests.

TRUST_PROXY=true is appropriate only when a trusted reverse proxy overwrites
or appends X-Forwarded-For. The implementation uses the rightmost value. With
multiple proxy hops, configure and test the trust boundary before relying on
per-client rate limits.

ALLOWED_HOSTS is a comma-separated allowlist used when the same server is
reached through trusted internal Docker hostnames. Do not add arbitrary public hosts.

GTM_TOOL_GROUPS controls schema size for clients that need only part of the
API. Available groups are accounts, workspaces, tags, triggers,
variables, folders, builtins, zones, templates, server, guidance,
environments, destinations, gtag, container-admin, folder-admin, and
workspace-admin, version-admin, and reverts. Leaving it unset preserves
the established 64-tool surface. New parity groups are opt-in. Use all to
include every current and future parity family, or select a subset:```text
GTM_TOOL_GROUPS=accounts,workspaces,tags,triggers,variables


The two connection utility tools remain available regardless of this setting.

### Optional setup dashboard

Set `DASHBOARD_ENABLED=true` and restart the server to expose `/dashboard/`.
The page shows the canonical MCP endpoint, server version, authentication setup status, and connection instructions. It is disabled by default.

The dashboard is public when enabled. It deliberately excludes tokens, sessions, account names, container data, and other GTM content. It reports server configuration only and does not verify the visitor&#x27;s Google session.

## Releases and deployment

`server.json` is the source of truth for the runtime version. It is embedded in the Go binary and returned by `/health`; there is no second version constant in Go code.

To publish a release:

1. Update `server.json`.
2. Commit the release changes.
3. Push a matching tag such as `v1.11.0`.

The release workflow rejects a tag that does not match `server.json`, creates
cross-platform archives with GoReleaser, and then deploys the tagged source to the production VPS. The deployment uses the GitHub environment
`auto-deployment` and expects these secrets:

- `SSH_PRIVATE_KEY`
- `VPS_KNOWN_HOSTS`
- `VPS_HOST`
- `VPS_USER`

The workflow preserves server-only `.env`, `docker-compose.yml`, and token data, keeps a rollback image, rebuilds the service, and waits until `/health`reports the expected version.

Recent commits on `main` can be newer than the latest tagged release. Check the release page when you need a reproducible published artifact.

## Development```bash
go test ./... -count=1
go vet ./...
staticcheck ./...
go run ./cmd/tool-schema-report
go run ./cmd/tool-schema-report -groups tags,zones

The schema report prints the GTM tool count, serialized tools/list size, token
estimate, and largest definitions. The default GTM tool surface serializes to
78,734 bytes for 64 tools. A regression test enforces an 80,000-byte ceiling so
new parity work does not silently consume unlimited model context. The all
group exposes 94 GTM tools and serializes to 115,748 bytes.

Pull requests run govulncheck, gosec, Gitleaks, Trivy, staticcheck, and
CodeQL. Request-level GTM tests use local fake Google endpoints. Mutating live
tests must use a disposable container and clean up their entities.

See ARCHITECTURE.md for package boundaries, request flow,
authentication internals, token persistence, and security invariants.

For a deep dive into the Google Tag Manager MCP server, read the Deep Wiki.

Additional context

  • llms.txt is served at
    https://mcp.gtmeditor.com/llms.txt.
  • skills/gtm-mcp/gtm-mcp.md contains a Claude
    Code skill with workflow guidance.
  • examples/gtm_agent.py demonstrates a programmatic
    MCP client.
  • Google Tag Manager API v2 reference
  • Model Context Protocol

License

BSD 3-Clause. See LICENSE.

Maintained by Paolo Bietolini.

常见问题

7 问
答案由本站依据条目字段整理,不引用上游原文
Gtm MCP Server 怎么安装?

资料没有给出安装命令,请到官方仓库或文档按说明接入;这类条目多数是生态应用,或尚未发布可安装包。

Gtm MCP Server 怎么在客户端里配置?

它的传输方式未标注,在客户端 MCP 配置里按官方文档填写启动命令和参数,保存后重启客户端生效。

Gtm MCP Server 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

Gtm MCP Server 需要 API Key 吗?

资料标注需要OAuth 授权认证,使用前准备好对应凭据,并按最小权限配置。

Gtm MCP Server 能提供哪些能力?

资料显示能力标签包括 标签管理、AI自动化、OAuth认证。具体工具清单以官方文档为准。

Gtm MCP Server 需要什么运行环境?

属于远程端点,不需要在本地装运行时。

Gtm MCP Server 是本地还是远程?

它是远程端点,连服务地址即可。传输方式为HTTP · 远程。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 2026-05-17。