MCP server for your release briefs

The GTM Lead exposes a Model Context Protocol endpoint so Claude and other MCP clients can answer questions about your release briefs, recipients and acknowledgements. Access is read-only. An agent cannot create, change or delete anything.

Set up

  1. Sign up and choose a plan. MCP access is included in every plan.
  2. Open MCP access in the app and create a token. The token is shown once and only its hash is stored.
  3. Add the endpoint and token to your client as shown below.

Claude Code

claude mcp add --transport http gtm-lead https://thegtmlead.com/api/mcp \
  --header "Authorization: Bearer YOUR_TOKEN"

Other clients

{
  "mcpServers": {
    "gtm-lead": {
      "type": "http",
      "url": "https://thegtmlead.com/api/mcp",
      "headers": { "Authorization": "Bearer YOUR_TOKEN" }
    }
  }
}

Tools

list_briefs
Lists briefs with title, category, status, effective date and version. Accepts an optional status filter.
get_brief
Returns one brief with body, approved claims, do-not-say claims and its readiness questions.
list_recipients
Returns recipient groups and the email addresses in each group.
list_acknowledgements
Returns every assignment for a brief with viewed, acknowledged and readiness state.
get_readiness_summary
Returns counts per status for one brief.

Protocol and security

The endpoint speaks JSON-RPC 2.0 over Streamable HTTP with POST requests and supports initialize, tools/list, tools/call and ping. Every request needs an Authorization header with a bearer token. A token is tied to one workspace, so an agent only sees that workspace. Revoke a token on the MCP access page and it stops working immediately. Requests also stop working when the workspace has no active plan.

Test it from a terminal

curl https://thegtmlead.com/api/mcp \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'