Connect your AI assistant to SGTM.space (MCP)

Once connected, the assistant picks the SGTM.space tools by itself when your question needs them. It works with your access, in every organization you belong to, the same as you in the app.

• List your containers with their website, plan and status.
• Read a container's setup: DNS records, Better Loader, the tagging server, add-ons and the setup steps that are still open.
• Start a website audit of a page on the container's site and explain every finding with its fix.

• Start and stop a Live Logs session, read what it recorded and explain the problems it found.
• Switch Live Logs Enhance on or off and check its web and server tags.

What it cannot do: change your plan, billing or payment details, delete containers or your account, invite, remove or change members, or see containers of organizations you do not belong to. Nothing it does changes your Google Tag Manager containers: it explains what to change there, and you make the change.

• You sign in to SGTM.space in your own browser (OAuth). The AI app never sees your password and needs no API key.
• Every app asks for your consent. The consent screen names the app, says where it returns to and lists what it will be able to do. Nothing happens until you press Allow.
• It acts as you. It reaches the same containers and features as you, and loses an organization the moment you leave it.
• You can disconnect it at any time. In Settings, AI apps, Disconnect ends its access at once. The app renews its sign-in by itself while you use it; only if that lapses, or after a disconnect, does it ask you to sign in and allow it again.
• Where the answers go. What the tools answer goes to the AI app you connected and its provider, under that provider's terms. SGTM.space logs which tool was called and when, never your questions or the answers.

Every app needs the same server address. Pick your app for its exact steps.

https://sgtm.space/mcp

claude mcp add --transport http sgtm https://sgtm.space/mcp

Set up the SGTM.space MCP server in Claude Code for me. It uses OAuth, so never ask me for a password or an API key.

1. Run `claude mcp add --transport http --scope user sgtm https://sgtm.space/mcp`. Add no API key or header.
2. Run `claude mcp get sgtm` to check that it was added.
3. Ask me to type `/mcp` in this session, choose sgtm and sign in to SGTM.space in the browser that opens, pressing Allow. If sgtm is not listed there, ask me to restart Claude Code first. Wait until I say I am done.
4. Then call the list_containers tool of the sgtm server and show me the names of my containers, to confirm the connection works. If its tools are not available in this session, tell me to restart Claude Code and ask there: List my SGTM.space containers.

{
    "mcpServers": {
        "sgtm": {
            "url": "https://sgtm.space/mcp"
        }
    }
}

Set up the SGTM.space MCP server in Cursor for me. It uses OAuth, so never ask me for a password or an API key.

1. Add a server named sgtm under `mcpServers` in `~/.cursor/mcp.json`: `"sgtm": { "url": "https://sgtm.space/mcp" }`. Create the file if it does not exist and keep every other server in it. Add no type, header or API key: it signs in with OAuth.
2. Ask me to open Cursor's MCP settings and connect sgtm, then sign in to SGTM.space in the browser that opens, pressing Allow. Wait until I say I am done.
3. Then call the list_containers tool of the sgtm server and show me the names of my containers, to confirm the connection works. If its tools are not available in this session, tell me to open a new chat and ask there: List my SGTM.space containers.

{
    "servers": {
        "sgtm": {
            "type": "http",
            "url": "https://sgtm.space/mcp"
        }
    }
}

Set up the SGTM.space MCP server in VS Code for me. It uses OAuth, so never ask me for a password or an API key.

1. Add a server named sgtm under `servers` in this workspace's `.vscode/mcp.json`: `"sgtm": { "type": "http", "url": "https://sgtm.space/mcp" }`. Create the file if it does not exist and keep every other server in it. Add no header or API key: it signs in with OAuth.
2. Ask me to start sgtm, with Start above it in `mcp.json` or through MCP: List Servers, then sign in to SGTM.space in the browser that opens, pressing Allow. Wait until I say I am done.
3. Then call the list_containers tool of the sgtm server and show me the names of my containers, to confirm the connection works. If its tools are not available in this session, tell me to open a new chat with the sgtm tools turned on in the tools picker and ask there: List my SGTM.space containers.

codex mcp add sgtm --url https://sgtm.space/mcp
codex mcp login sgtm

Set up the SGTM.space MCP server in Codex for me. It uses OAuth, so never ask me for a password or an API key.

1. Run `codex mcp add sgtm --url https://sgtm.space/mcp`. If that command is not available, add a `[mcp_servers.sgtm]` table with `url = "https://sgtm.space/mcp"` to `~/.codex/config.toml` instead and keep everything else in that file.
2. Ask me to run `codex mcp login sgtm` in a terminal and sign in to SGTM.space in the browser that opens, pressing Allow. Wait until I say I am done.
3. Then call the list_containers tool of the sgtm server and show me the names of my containers, to confirm the connection works. If its tools are not available in this session, tell me to start a new Codex session and ask there: List my SGTM.space containers.

hermes mcp add sgtm --url https://sgtm.space/mcp --auth oauth

Set up the SGTM.space MCP server in Hermes Agent for me. It uses OAuth, so never ask me for a password or an API key.

1. Add a server named sgtm under `mcp_servers` in `~/.hermes/config.yaml` with `url: "https://sgtm.space/mcp"` and `auth: oauth`, and keep every other server in that file. Do not run `hermes mcp add`: it asks questions in the terminal.
2. Ask me to run `hermes mcp login sgtm` in a separate terminal and sign in to SGTM.space in the browser that opens, pressing Allow. A running session waits only 30 seconds for a sign-in, so do not start it yourself. Wait until I say I am done.
3. Ask me to type `/reload-mcp` in this session.
4. Then call the list_containers tool of the sgtm server and show me the names of my containers, to confirm the connection works. If its tools are not available in this session, tell me to start a new Hermes session and ask there: List my SGTM.space containers.

Whichever app you use, the sign-in ends on the SGTM.space consent screen. It names the app and where it returns to, and lists what the app will be able to do. Check that it is the app you are adding, then press Allow.

1. 1 Ask your assistant: List my SGTM.space containers. It should name your containers, from every organization you belong to.
2. 2 Open Settings, AI apps in SGTM.space. Your app is listed there, with when you connected it and when it was last used.

• The assistant lists your containers.
• Your app shows under Settings, AI apps.
• Your app asks you before a tool that changes something.

Ask in your own words, in your own language. Name the container by its website or name, and replace example.com with your own site. A few prompts to start with:

• Find unfinished setup: List my SGTM.space containers and tell me, for each one, which setup steps are not done yet and what I should do next.
• Explain a container: Check the setup of my SGTM.space container for example.com and explain in simple words what Better Loader and the tagging server do there.
• Audit a website: Run an SGTM.space audit of https://example.com and tell me what is wrong with my tracking, most important problem first.
• Brief a developer: Read the latest SGTM.space audit of example.com and write a short note for my developer: what to fix, how to fix it and how to check it.

An audit loads your page in a real browser, so it takes a little while: the assistant starts it, then reads the result about 10 seconds later, as often as it needs. Audits it starts count towards the container's daily audit allowance, together with the ones you start on the Audit tab, and the page it loads counts like any visitor. Where available, a finding comes with links to its fix in SGTM.space and to a lesson to read.

Live Logs records what one tester's browser sends, step by step, so you can see where an event gets lost or sent twice (lesson 5). The assistant can run the whole session with you, but one step is always yours: a person has to open the start link in a browser.

1. 1 Ask, for example: Start a Live Logs session on my SGTM.space container for example.com. I will place a test order, then tell me where the purchase event got lost.
2. 2 The assistant says what the session records and asks you to confirm that the testers know their requests are shown. Confirm only once they do: the confirmation counts as yours, as in the app.
3. 3 It starts the session and gives you a start link. Open it yourself, in a private window on your own device, with Tag Assistant closed. The link works once the session is ready, usually within a minute.
4. 4 Do what you want to test, such as the test order, then ask the assistant to read the session. It reads the summary, looks at the events behind a problem and explains each one with its fix, most serious first.
5. 5 Ask it to stop the session when you are done. Stopping deletes what the session recorded.

• 404 Not Found when you add the server or sign in. We are opening MCP step by step, and an account it is not open to yet gets 404 from the server and the sign-in. Check the address too: it must be exactly the one above.
• consent_required. The app tried to sign in again without showing you the consent screen, which SGTM.space never allows. Connect again from the app: sign in, check the consent screen and press Allow.
• 401 Unauthorized after you disconnected. Disconnecting ends the app's access at once, and every token it had stays refused. To use it again, connect it again from the app and press Allow.
• The tools do not show up. Most apps load an MCP server's tools when a session starts: start a new chat or session, or reload the server (/mcp in Claude Code, /reload-mcp in Hermes).
• Too many requests (429). The server takes up to 120 calls a minute for each access token an app holds, and audits have their own limits per minute and per day. Wait a minute, or until the time the answer names, and ask again.

• analysis_busy. The Live Logs analysis is handling other sessions. The tool already waits and tries again by itself, so when it still says busy, ask again in about 10 seconds. When it says the analysis is unavailable, wait a minute and use the Live Logs tab meanwhile.
• The session reads as starting. A new session takes up to a minute to be ready. Open the start link once it is, then ask again.
• Live Logs is not available on this container. The answer says what is missing: a paid plan, a tagging server or Better Loader, each with a link to where you add it.