MCP Tool Reference

Technische Referenz auf Englisch.

GTM Automation exposes its entire internal tool surface through one MCP (Model Context Protocol) server per workspace:

https://<your-domain>/api/mcp/<your-mcp-key>

Any MCP-capable client — Claude Code, Claude Desktop, Cursor, or a custom agent — can connect to this URL and call every tool documented below, scoped to that one workspace.

Getting a key

Generate or read the workspace MCP key from Extensions → GTM Goat MCP Server in the web app, or via the get_mcp_key / generate_mcp_key tools from an already-connected session (e.g. Command). Rotating the key (generate_mcp_key) invalidates the previous one immediately — the new key is shown once and is not retrievable in plain text later.

Reading this reference

This reference is generated directly from the live tool registry (src/lib/mcp/tool-registry.ts) by scripts/generate-mcp-docs.ts — every tool, parameter, and annotation below reflects the code, not a hand-maintained description. Re-run the generator after any registry change; never edit the files in this folder by hand.

Each tool carries exactly one badge:

• read-only — safe to call anytime, no side effects.
• destructive — overwrites, deletes, or resets something; call deliberately.
• action — performs a side effect (send, sync, create, trigger) that is neither read-only nor destructive.

A Required integration line, where present, names the adapter category id(s) (as configured in Extensions) that must be connected for the tool to be advertised to an agent in this workspace — the tool remains callable directly via the MCP endpoint regardless.

Categories

Category	Modules	Tools	Reference
Pipeline	7	58	pipeline.md
Research	7	41	research.md
Outreach	8	81	outreach.md
Analytics	6	42	analytics.md
Workspace	6	60	workspace.md
Automation	7	56	automation.md

Total tools documented: 338