MCP server for Gong.io - access calls, transcripts, and users
Nothing to run from here
gtm.help is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
93/100
tool-list score
16
tools declared
remote
at its publisher
—
calls last 7d
What it does
Your go-to-market plan, plays and opportunities from gtm.help, inside any AI agent.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http gtm-help-mcp https://gtm.help/mcp
# 2 — ask your agent for something these tools do
# analyze_site, list_workspaces, get_business and 13 more
gtm.help costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
GTAll 1 server
gtm1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http gtm-help-mcp https://gtm.help/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
16 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Analyse any website and return three high-leverage growth plays it could start this week. Free — no subscription required.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| url | string | yes | The website to analyse, e.g. acme.com or https://acme.com |
List the growth workspaces (businesses) belonging to the signed-in user, with their website, goal, stage and budget.
No parameter schema on file.
Read one workspace's full profile — website, description, audience, industry, stage, goal, budget, hours per week, competitors, channels, what has been tried — plus the notes stored with add_business_note and a quick progress summary. Use it before giving advice so it fits this business.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| business_id | string | yes | Workspace id from list_workspaces. |
Read the ranked growth plays for one workspace. Returns title, category, fit score, effort, budget, tools and status, ordered by rank.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| business_id | string | yes | Workspace id from list_workspaces. |
| status | string | no | Filter by completion state. Defaults to open plays. |
| limit | integer | no | How many plays to return. Defaults to 20. |
Read the full detail of one growth play: rationale, steps, tools, budget and success metric.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| play_id | string | yes | Play id from get_plan. |
Change a growth play's state: start it (in_progress), park it for later (snoozed, with days), skip it for good (skipped, with a reason), reopen it (open) or finish it (done). Mirrors the To do / In progress / Done / Parked board in the app.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| play_id | string | yes | Play id from get_plan. |
| status | string | yes | New state. |
| reason | string | no | Why it was parked or skipped — the best signal for the next plan. |
| snooze_days | integer | no | Days to park it when snoozed. Defaults to 7. |
Save the finished work for one play (copy, code or research, in markdown) onto the founder's gtm.help board as Ready to review. Use this whenever you have written the work for a play, instead of leaving it only in chat. It never marks the play done and never publishes anything.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| play_id | string | yes | Play id from get_plan. |
| deliverable | string | yes | The finished work in markdown, ready to copy and use. |
| kind | string | no | copy_kit (copy/emails/posts), code (markup/files) or audit (research). Defaults to copy_kit. |
| agent_name | string | no | Your name, e.g. Claude or Cursor, shown on the board. |
Mark a growth play as shipped (or reopen it). Completing a play unlocks the next one in the ranked plan.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| play_id | string | yes | Play id from get_plan. |
| done | boolean | no | Set false to reopen the play. Defaults to true. |
| note | string | no | Optional note about what was shipped. |
Save a note about the business so the growth plan and the consultant remember it (results, context, constraints).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| business_id | string | yes | Workspace id from list_workspaces. |
| note | string | yes | The note to remember. |
Create a public, shareable summary of recent progress for a workspace. Returns a URL that can be pasted into a chat, tweet, report or Slack thread.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| business_id | string | yes | Workspace id from list_workspaces. |
| focus | string | no | Time window for completed plays: week, month, or all time. Defaults to week. |
| title | string | no | Optional title for the recap card. |
Read the Reddit, LinkedIn and X conversations the agents found for a workspace: threads, posts and comments where the user's business can genuinely help. Ranked by fit and heat. Use draft_reply to write an answer and update_opportunity to record what happened. Nothing is ever posted automatically.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| business_id | string | yes | Workspace id from list_workspaces. |
| agent | string | no | Which network: reddit, linkedin, x or all. Defaults to all. |
| status | string | no | open = not yet answered, drafted = has a saved draft, replied = marked as answered. Defaults to open (which includes drafted). |
| sort | string | no | Order. Defaults to best (fit + heat). |
| limit | integer | no | How many to return. Defaults to 10, max 50. |
Write a reply for one Reddit, LinkedIn or X opportunity from list_opportunities, using the business's own context and the workspace's writing settings (karma-safe, mention business). Returns the text and the exact link to paste it at. gtm.help never posts on the user's behalf — the user copies, edits and posts it themselves.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| opportunity_id | string | yes | Opportunity id from list_opportunities. |
| tone | string | no | default, short, detailed, or no-pitch (never names the business). Defaults to default. |
Record what happened to a Reddit, LinkedIn or X opportunity: replied (the user posted their answer — include the link), ignored (not a fit, with an optional reason that sharpens future ranking), snoozed (come back later) or open (put it back on the board).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| opportunity_id | string | yes | Opportunity id from list_opportunities. |
| status | string | yes | New state. |
| posted_url | string | no | Link to the user's posted reply, when status is replied. |
| reason | string | no | Why it was ignored, e.g. 'wrong audience' or 'already answered'. Shapes future ranking. |
| snooze_days | integer | no | Days to hide it when snoozed. Defaults to 3. |
Read or change the watch lists behind the Reddit, LinkedIn or X agent for a workspace: keywords, topics the business can answer, competitors, people/accounts, and (Reddit only) subreddits. Each list holds up to 10 entries. Call with no add/remove to just read them.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| business_id | string | yes | Workspace id from list_workspaces. |
| agent | string | yes | reddit, linkedin or x. |
| list | string | no | Which list to change. Required when adding or removing. |
| add | array | no | Entries to add. |
| remove | array | no | Entries to remove. |
Show which tools a workspace has connected (Google Analytics, Search Console, Composio apps such as HubSpot, Stripe, Shopify, Mailchimp and more) with their health, and the most recent metric summary synced from each. Read-only.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| business_id | string | yes | Workspace id from list_workspaces. |
Read the user's gtm.help billing history: invoice number, date, status, amount, tax and links to the PDF and hosted receipt. Only the signed-in customer's own invoices are visible.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| limit | integer | no | How many recent invoices. Defaults to 12, max 50. |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install gtm.help or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATool-list grade · score 93 / 100
Release 1.0.0 · scanned 20 Oct 2026
Graded from the tools this server lists, not from its source code.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score93
Findings0 threat · 2 capability
Capabilitymoderate
Coveragemanifest
Verificationnot in this report
Surface digest7b797107d5e282f88b53280d77be42407ccbc71caac9a17457ffb1fd37631347
Score vectorthreat 100 → client 93
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
Tool surfaceread
Implementation sourcenot available
Package metadatanot available
Live transportnot available
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| analyze_site | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| list_workspaces | no tags | |
| get_business | no tags | |
| get_plan | no tags | |
| get_play | no tags | |
| update_play_status | state-write | state-write: declares readOnlyHint: false |
| submit_play_draft | state-write | state-write: declares readOnlyHint: false |
| complete_play | state-write | state-write: declares readOnlyHint: false |
| add_business_note | state-write | state-write: declares readOnlyHint: false |
| share_recap | state-write | state-write: declares readOnlyHint: false |
| list_opportunities | no tags | |
| draft_reply | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
| update_opportunity | state-write | state-write: declares readOnlyHint: false |
| update_watchlist | state-write | state-write: declares readOnlyHint: false |
| list_integrations | no tags | |
| list_invoices | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
flow-1
Untrusted input can drive an external action even though no sensitive source is exposed.
Supply chain and provenance
Integrityfirst-seen
Surface digest7b797107d5e282f8
Scanned2026-10-20
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.0.
1.0.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish gtm.help can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.