gtm-api: LinkedIn MCP Server avatar

gtm-api: LinkedIn MCP Server

Pricing

Pay per usage

Go to Apify Store
gtm-api: LinkedIn MCP Server

gtm-api: LinkedIn MCP Server

Managed LinkedIn MCP server for AI agents: search, connect, message and enrich on accounts you own. Safety enforced server-side: warm-up, daily limits, preview-then-confirm. Bridges to the hosted gtm-api endpoint.

Pricing

Pay per usage

Rating

0.0

(0)

Developer

Evgenii Salamatov

Evgenii Salamatov

Maintained by Community

Actor stats

0

Bookmarked

1

Total users

0

Monthly active users

6 days ago

Last modified

Share

gtm-api LinkedIn MCP Server

Managed LinkedIn MCP server for AI agents, running as an Apify Actor. It bridges MCP clients to the hosted streamable-http endpoint at https://mcp.gtm-api.com/mcp; no server logic runs inside the Actor. Every tool executes on the hosted server, where account safety is enforced: warm-up ramps for fresh accounts, server-side daily limits, preview-then-confirm on outward actions. gtm-api reports 20,000+ LinkedIn accounts running at under 1% monthly ban; the method is written up at gtm-api.com/safe-linkedin-automation.

The server exposes three MCP tools (list_toolsets, get_toolset_tools, call_tool) that give an agent progressive access to 160+ typed LinkedIn actions: messaging, connection requests, content, enrichment, search, account health and infrastructure.

Setup

  1. Get an API key at app.gtm-api.com (7-day trial, no card) and connect a LinkedIn account you own.
  2. Start this Actor in Standby mode with gtmApiKey set in the input, or pass the key per request instead (an x-gtm-api-key header, or ?gtm_api_key=... in the URL).
  3. Point your MCP client at the Actor's Standby URL, path /mcp, with your Apify token:
{
"mcpServers": {
"gtm-api": {
"url": "https://USERNAME--linkedin-mcp.apify.actor/mcp?token=YOUR_APIFY_TOKEN"
}
}
}

A normal (non-Standby) run performs a connectivity self-check against the hosted endpoint, writes the result to the dataset, and exits.

Input

FieldRequiredMeaning
gtmApiKeyno, if passed per requestAPI key from app.gtm-api.com, sent upstream as an Authorization bearer
upstreamUrlnoEndpoint override, defaults to https://mcp.gtm-api.com/mcp

Prefer a direct connection?

Clients that speak streamable-http do not need this Actor: point them straight at https://mcp.gtm-api.com/mcp with an Authorization: Bearer YOUR_API_KEY header. Stdio clients can use the npm launcher @gtm-api/linkedin-mcp or the Docker image gtmapi/linkedin-mcp. This Actor exists for teams that keep their agent stack on Apify.