# Gtmotto LinkedIn MCP server

Source: https://glimind.com/server/mcp-registry%2Fcom.gtmotto%2Flinkedin
Registry id: `mcp-registry/com.gtmotto/linkedin`
Status: live (checked 2026-10-27T00:23:02.245Z)

## Measurements (30 days)

- Uptime: 99.93%
- Checks: 4933
- Outages (90 days): 3

## Install

```json
{
  "mcpServers": {
    "gtmotto-linkedin-mcp-server": {
      "type": "http",
      "url": "https://agent.gtmotto.com/mcp"
    }
  }
}
```

Claude Code:

```sh
claude mcp add --transport http gtmotto-linkedin-mcp-server https://agent.gtmotto.com/mcp
```

## Tools (21)

- `gtm_approve`: Approve ONE drafted action by its approvalId (from gtm_list_approvals). It then leaves on the seat's next slot, inside LinkedIn's limits — this is the human's t
- `gtm_configure_source`: Write a lane's settings — upload an account list, set the Post-discovery intent and anchors, change the job keywords, move a gate. MERGE semantics: only the fie
- `gtm_connect_linkedin`: The link a human opens to connect (or reconnect) their LinkedIn account to a play — the one cockpit step the play cannot run without. Hand the URL to the human,
- `gtm_create_play`: Create a fully-configured play in one call: the product (an existing productId, or a websiteUrl which seeds one and kicks its research), the play itself, the IC
- `gtm_estimate_icp`: How big an audience a CANDIDATE ICP would reach — '≈ N companies match' — before committing to it. Writes nothing: no play, no ICP row, no cache. Use it to iter
- `gtm_forget_harvested_posts`: The tuning escape hatch for the post lanes. A post lane remembers every post it already paid to harvest so it never buys the same engagers twice — which makes i
- `gtm_linkedin_status`: The play's LinkedIn seat and today's headroom against the LinkedIn limits. States: `no_seat` (nothing connected — the play cannot act), `seat_broken` (the accou
- `gtm_list_approvals`: Every drafted action that waits for the human — an invite note, a first message, a follow-up, a reply or a comment the planner wrote — with the draft, the 'why 
- `gtm_list_plays`: Every play in the workspace with enough context to route on: which product it sells, whether it is active or paused, whether a LinkedIn seat is actually connect
- `gtm_play_stats`: The play's Stats screen: the pipeline (leads sourced → warmed → invited → new connections → conversations started) over four windows — all time, last 30 days, l
- `gtm_preview_source`: Dry-run ONE lane: '≈ N people match' and a 10-person sample, WITHOUT inserting a lead, spending the day's budget or moving the run clock. Same query, same gates
- `gtm_reject`: Reject (skip) ONE drafted action by its approvalId. Nothing is sent; the planner records the decline and re-plans around it instead of proposing the same step a
- `gtm_run_source`: 'Run once now' — run ONE lane immediately through the same code the sourcing tick runs, with force: an OFF lane still runs (that is what run-once means while co
- `gtm_set_source`: Switch a lane on or off — the toggle on the Sources list. Switching ON a lane that has nothing to run on (no companies, no intent/anchors/posts, no role) is ref
- `gtm_show_play`: ONE play in full — everything needed to judge it or copy it into a better one: goal and voice, the account's daily cap and working hours (shared by every play o
- `gtm_show_sources`: All five sourcing lanes of a play, configured or not — the read to make before touching any of them. Per lane: `configured`, `on`, the parsed `config` (defaults
- `gtm_source_runs`: The run history of ONE lane, newest first — the funnel over time (scanned → dropped by fit → dropped by intent → added / duplicates / capped), the ICP facets Li
- `gtm_sources_reference`: THE REFERENCE for configuring sourcing lanes — read it before your first gtm_configure_source / gtm_set_source / gtm_run_source call. Every lane (people_search,
- `gtm_update_icp`: Change the ICP a play runs — the query behind people_search and the fit gate on every other lane. Seven string arrays, plain words (gtmotto normalises 'Swiss' →
- `gtm_update_play`: Change a play's own knobs — name, goal, voice — its two switches, and the ACCOUNT's pacing (daily action cap, working hours: shared by every play on the LinkedI
- `gtm_whoami`: Who this key belongs to, and what the workspace may do: org name, plan, subscription status, how many products and plays exist, and the LEAD METER (leads added 

Measured by Glimind (https://glimind.com): MCP handshake + tool list only, no tool is ever called. CC BY 4.0.