GTM API: LinkedIn MCP Server

GTM API is a managed LinkedIn MCP server.

CommunityOnlineNo sign-inGlobalFreeCan modify data

What it can do

  • List Toolsets: List the available toolsets (domains) on this server. Each toolset groups related tools (e.g. linkedin.messaging, id.billing). Start here, then get_toolset_tools to inspect one, then ca
  • Get Toolset Tools: List the tools in a toolset. Default (lite) returns name + title + one-line summary; pass verbose:true for full descriptions, safety flags, and parameter names. Run one via call_too
  • Call Tool: Execute any tool by name (discovered via get_toolset_tools) with its arguments object. Behaves exactly like calling the tool on its domain mount. Dangerous tools still require the two-step

What data it sees

Do you need an account

No: the server works without sign-in

GTM API is a managed LinkedIn MCP server. It exposes 160+ typed LinkedIn tools across 10 toolsets over the Model Context Protocol, so an AI agent can run real LinkedIn outreach (send connection requests, message, InMail, enrich, search) on a LinkedIn account you own, wrapped in an anti-detect + rate-limit safety layer. Unlike cookie-scraping open-source servers, it runs on owned accounts with dedicated proxies and server-side limits: self-reported 20,000+ accounts at under 1% monthly ban, MCP + REST + webhooks, from $19/account/mo with unlimited calls.

Docs: gtm-api.com/linkedin-mcp-server Source: github.com/gtm-api/linkedin-mcp

How to connect

How to connect GTM API: LinkedIn MCP Server to Claude

The server address to paste into Claude settings:

https://linkedin-mcp-gtm-api.run.tools

  1. Open Claude (claude.ai or the desktop app).
  2. Go to Settings → Connectors.
  3. Click Add custom connector.
  4. Paste the server address copied below into Remote MCP server URL and click Add.
  5. In a chat, click + → Connectors and switch the new connector on.

Custom connectors are available on Free, Pro, Max, Team and Enterprise plans (Free is limited to one). On Team and Enterprise an organization Owner adds the connector first under Organization settings → Connectors.

Authorization

After you click Add, a sign-in window for the service opens. Sign in with your own account and approve access. Claude never sees your password.

How to connect GTM API: LinkedIn MCP Server to ChatGPT

The server address to paste into ChatGPT settings:

https://linkedin-mcp-gtm-api.run.tools

  1. Open ChatGPT in a browser (chatgpt.com). A Plus, Pro, Business, Enterprise or Edu plan is required.
  2. Turn on developer mode once: Settings → Apps → Advanced settings → Developer mode.
  3. Open Settings → Connectors and click Create.
  4. Fill in the form: Name (anything), Description (one line about what the service does), MCP server URL (copy it below).
  5. Under Authentication choose OAuth if the service requires sign-in, otherwise None. Click Create.
  6. In a new chat open + → Apps/Connectors and enable the connector.

OpenAI has renamed this section before (Connectors → Apps/Plugins). If the label differs, search settings for "developer mode". On Business/Enterprise workspaces an admin must allow custom connectors first.

Authorization

On first use ChatGPT opens the service's sign-in window. Sign in and approve access.

How to connect GTM API: LinkedIn MCP Server to Cursor

The server address to paste into Cursor settings:

https://linkedin-mcp-gtm-api.run.tools

Fastest: click Open in Cursor below and confirm the prompt.

Manually:

  1. In Cursor open Settings → Cursor Settings → MCP and click Add new global MCP server.
  2. Paste the JSON copied below into ~/.cursor/mcp.json (per project: .cursor/mcp.json in the repo root).
  3. Save the file. The server appears in the MCP list; authorize it there if asked.

Authorization

If the service needs sign-in, an authorize button appears next to the server in the MCP list.

Server tool list (3)

Raw names from tools/list. Only developers need these.

list_toolsetsList the available toolsets (domains) on this server. Each toolset groups related tools (e.g. linkedin.messaging, id.billing). Start here, then get_toolset_tools to inspect one, then call_tool to run a tool.
get_toolset_toolsList the tools in a toolset. Default (lite) returns name + title + one-line summary; pass verbose:true for full descriptions, safety flags, and parameter names. Run one via call_tool.
call_toolExecute any tool by name (discovered via get_toolset_tools) with its arguments object. Behaves exactly like calling the tool on its domain mount. Dangerous tools still require the two-step preview→confirm (pass commit_token inside arguments on the confirm call).