Skip to main content
The server speaks streamable HTTP at https://mcp.gtm-api.com/mcp and authenticates with OAuth. Your client discovers the flow on its own: the first call comes back with a WWW-Authenticate challenge pointing at the server’s metadata, the client registers itself, and you approve the consent screen in your browser. Nothing to paste, no key to store.

Add to your agent

One action per client, then approve the consent screen that opens. That is the whole setup.

Claude

Open Customize, Connectors, then Add, “Add custom connector”. Name it, paste https://mcp.gtm-api.com/mcp, click Continue, keep the detected sign-in settings and click Add, then Connect and approve access. Works for claude.ai and Claude Desktop. On Team and Enterprise plans an Owner adds it under Organization settings, Connectors, and each member clicks Connect.

Cursor

One-click install (the button opens Cursor). Sign in on the consent page that follows.

VS Code

One-click install (the button opens VS Code). Sign in on the consent page that follows.

ChatGPT

Plugins, the plus button, Add custom MCP server. Enter the URL above, choose OAuth, acknowledge the risk warning and select Create as a plugin, then complete the sign-in. Developer mode is not required. On Business and Enterprise workspaces an admin may need to allow custom MCP servers first.

Claude Code

Then run /mcp in any session and authenticate when prompted. claude mcp list shows gtm-api as connected once consent is done.

Codex

The first line registers the server in ~/.codex/config.toml, the second runs the OAuth flow and opens the consent page. No client id to pass: the server registers the client on its own.

Any other MCP client

Point it at https://mcp.gtm-api.com/mcp over the streamable HTTP transport and let it run the OAuth flow. Clients that support MCP OAuth need nothing else: the server advertises its authorization server, and dynamic client registration means your client does not need to be pre-registered with us.

Clients that only spawn a command

Some clients cannot take a URL at all, only a command to run over stdio. For those, the @gtm-api/linkedin-mcp launcher bridges stdio to the same hosted endpoint and runs the same OAuth flow, opening the consent page on first use and caching the tokens under ~/.mcp-auth.

Headless: authenticate with an API key

The same key that authenticates the REST API works on this server as a plain bearer token. No browser, no consent screen, so it fits CI, servers and any client where the OAuth round-trip is not an option. Mint a key in the app (Settings, API keys) and attach it as a header:
For command-spawning clients, the launcher takes it from the environment instead:
Use launcher 1.3.2 or later with a key. 1.1.0, 1.3.0 and 1.3.1 hand GTM_API_KEY to the bridge on its command line, so the key shows in the process list and in the MCP client’s log: npm marks the three deprecated, and a key used with one of them should be rotated. 1.2.x ignores the variable and does OAuth only.
Pick one mode per connection: with a key attached, the OAuth flow never starts. The key is scoped to its workspace and its permission set, revocable in the app, and treated like a password (see Authentication). Connectors on claude.ai and in Claude Desktop sign in through the browser. Anthropic’s request headers section, in beta for a limited set of organizations, is the one way to give a connector the key instead: choose No sign-in and add an authorization header with the value Bearer gtm_live_..., scheme included. Everyone who uses that connector then acts with that one key.

Check it from a terminal

To confirm the endpoint and walk the OAuth flow by hand:
Choose the streamable HTTP transport, enter https://mcp.gtm-api.com/mcp, connect, and complete the consent screen. The tool list appears once you are authorized.

What you get

Three meta-tools rather than hundreds of individual ones: list_toolsets to see the domains, get_toolset_tools to inspect one, and call_tool to run any tool by name. Dangerous tools still run their preview and confirm step, so an agent cannot commit a bulk send without showing you what it is about to do.

First prompt to try

“Check the smart limits on my LinkedIn account, then draft, preview and send a connection request to the profile at this URL.”
The agent chains the tools on its own. The preview step and the server-side limit check run before anything is sent.