Connect Codex to gtm.help

Codex talks to gtm.help over MCP, so the same tools you get in Claude or Cursor work from the terminal: analyse a site, pull the ranked plays for a workspace, mark work shipped and drop notes back into the plan.

Add the MCP server in Codex.

  1. Step 1

    Open your Codex config

    Codex reads MCP servers from ~/.codex/config.toml. Create the file if it isn't there yet.

  2. Step 2

    Add the gtm.help server

    Codex launches MCP servers as local processes, so wrap the hosted endpoint with mcp-remote. It handles the OAuth sign-in for you.

    [mcp_servers.gtm-help]
    command = "npx"
    args = ["-y", "mcp-remote", "https://gtm.help/mcp"]
  3. Step 3

    Sign in once

    Start Codex and run the tool below. A browser window opens for the gtm.help sign-in; the token is cached, so you only do this once per machine.

    codex
  4. Step 4

    Put it to work

    Ask Codex for the plan the same way you'd ask in chat.

    Use gtm.help to analyse example.com, then list this week's plays with hours and cost.

First things to ask.

Once Codex is connected, these prompts confirm everything works.

  • “Analyse stripe.com and give me three growth plays.” (free, no plan needed)
  • “List my gtm.help workspaces.”
  • “What should I ship this week?”
  • “Mark the cold outbound play complete and share a recap.”

What Codex gets access to.

Your agent works inside your own account, and it never posts anything for you.

  • Your agent signs in as you. It sees the same businesses, plans and notes you see when you log in — nothing from anyone else's account.
  • It can read your plan, move plays, store notes, draft replies and read the numbers your connected tools have synced.
  • It can never post, comment or message on Reddit, LinkedIn, X or anywhere else. Drafts are text you copy, edit and post yourself.
  • It cannot see your password, your card details or anyone's contact data. Invoices are limited to your own account.
  • Disconnect whenever you like: remove the connector in your agent, and the access ends immediately.

The four common snags.

The server connects but shows no tools

The sign-in did not finish. Remove the connector, add it again and complete the gtm.help sign-in window to the end.

The sign-in window keeps reopening

Usually a blocked pop-up or a stale cookie. Allow pop-ups for your agent, sign in at gtm.help in the same browser first, then retry.

It worked yesterday and now says disconnected

The access token expired. Reconnecting takes a few seconds and keeps all your data.

Analysing a site works, but everything else is refused

Site analysis is free; reading and changing your own plan needs an active plan. Start a 7-day trial and the rest unlocks.

Notes for Codex.

  • Any MCP client works the same way — the endpoint is https://gtm.help/mcp and there is no separate REST API or API key to manage.
  • analyze_site is free for any connected account; plan, workspace and completion tools need an active Growth or Agency plan.
  • If Codex lists the server with no tools, delete the cached mcp-remote credentials in ~/.mcp-auth and sign in again.

Run your growth plan from Codex.