GTM MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GTM_TRANSPORT | No | `streamable-http` for remote hosting | stdio |
| GTM_LOG_FORMAT | No | `console` for readable local development logs | json |
| GTM_DATABASE_URL | No | Mock CRM connection | postgresql+asyncpg://gtm:gtm@localhost:5432/gtm |
| GTM_DRY_RUN_WRITES | No | `true` validates and audits without persisting | false |
| GTM_ENABLE_WRITE_TOOLS | No | `false` runs a strictly read-only deployment | true |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| server_infoA | Report which GTM capabilities this server can currently perform. Call this first when you are unsure whether a GTM capability is available, or when a data-modifying call has failed and you need to know whether writes are disabled. It takes no arguments, reads no customer data, and changes nothing. Returns which tools are implemented versus merely planned, whether the CRM database is reachable, and whether write tools are permitted to modify data. Do not call tools listed under planned capabilities; they are not registered and the call will fail. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only one tool, there is no possibility of confusion between tools. The server_info tool has a clear and singular purpose, so disambiguation is trivially perfect.
The single tool is named server_info, which follows a clear noun_noun pattern. With only one tool there are no inconsistencies to evaluate, so naming is internally consistent.
A server titled 'GTM MCP Server' would be expected to expose a range of GTM operations, but it exposes only a single information reporting tool. This falls at the 'too few' end of the scale for the apparent scope.
The server provides no tools for actual GTM management—no operations for tags, triggers, variables, containers, or any data modification. It only reports capabilities, leaving the domain severely uncovered.