What it is

The GTM Brigade connector is a remote Model Context Protocol (MCP) server. One server, the same tools, whichever assistant you connect it to. Once connected, your assistant can answer questions like “how did my posts do this week?” and carry out work like “draft a post about our pricing change and schedule it for Tuesday” or “add these five profiles to the watchlist.”

It exposes 69 tools across your whole GTM Brigade account: 31 read your data and 38 change something. Six of them reach outside GTM Brigade — they publish on LinkedIn under your own name, send an email, or write into your CRM. Every tool that is not read-only is flagged as such, so your assistant asks you before it runs.

For worked examples of what people actually ask it, see what you can do with the connector: real sentences, the tools each one fires, and which of them change your account.

Add it to Claude

  1. In Claude, open Settings → Connectors → Add custom connector.
  2. Enter the server URL: https://api.gtmbrigade.com/mcp
  3. Claude opens a browser window to sign in. Log in with your GTM Brigade account, review the permissions listed on the consent screen, and click Allow.
  4. That's it — the tools appear in Claude.

Add it to ChatGPT

  1. In ChatGPT, open Settings → Connectors and add a custom connector (this needs developer mode on a plan that allows custom connectors).
  2. Enter the same server URL: https://api.gtmbrigade.com/mcp
  3. Sign in on the GTM Brigade consent screen and click Allow, exactly as above.

The same URL and the same account work in both. ChatGPT's research surface looks for two specifically-named tools, search and fetch, and the connector serves them, so your leads, posts, drafts and knowledge base are citable there. Note that ChatGPT's deep-research mode is read-only by design: it will use the reading tools and will not run the ones that write.

Add it to Gemini or Perplexity

Both connect to the same URL, with one difference: they may ask you for a client ID and client secret instead of registering themselves. Gemini Enterprise always does (its admin console has no automatic registration), and Perplexity falls back to it. Ask us and we will issue a pair for your organization.

  • Gemini Enterprise: add a custom MCP server in the admin console, enter https://api.gtmbrigade.com/mcp and the credentials we issue. If the console shows a PKCE checkbox, tick it: this server requires PKCE and the connection will not complete without it.
  • Perplexity: add a custom connector under your account or organization settings (Pro, Max, Business or Enterprise). Enter https://api.gtmbrigade.com/mcp, and the credentials if it asks for them.

Neither Google nor Perplexity runs a connector directory, so there is nothing to browse for. You add the URL yourself.

Authorization uses OAuth 2.1 with PKCE in every client. GTM Brigade never sees your Claude, ChatGPT, Gemini or Perplexity account, and none of them ever sees your GTM Brigade password. You sign in on our own consent page.

What it can read

31 read-only tools, in eleven groups:

  • Your analytics and your team’s · 6
    Your posts, comments, reactions, impressions, reach, followers, activity score and leaderboard rank — plus the team leaderboard, org-wide overview and Company Page metrics for owners.
  • Leads and lead lists · 4
    Search your lead database, open a single lead with its enrichment and engagement history, list your lead lists, and follow the progress of enrichment running in the background.
  • Watchlist, feed and comment suggestions · 4
    The profiles your team monitors with their activity stats, the posts they published, and the AI comment suggestions waiting on them.
  • Content and drafts · 3
    Your posts and drafts with their status and performance, and the personal writing style GTM Brigade learned from you.
  • Knowledge base · 2
    List your organization’s knowledge-base assets, and search them semantically — your private personal assets stay private to you.
  • ICPs · 2
    Your ideal-customer profiles, their signals, and how many leads match each one.
  • Comment automation · 2
    Your automation settings and the queue of drafts waiting for approval or scheduled to go out.
  • Feed keywords · 1
    The keywords you subscribe to for keyword-matched posts in your feed.
  • Billing, plans and consumption · 3
    Your plan, credit balances, consumption breakdown by user and feature, invoices, and the available plans.
  • Search and fetch · 2
    One search across your leads, posts, drafts and knowledge base, and a fetch that opens any result in full. These carry the names ChatGPT expects for its research surface, and work the same way in every client.
  • Team and targets · 2
    Your organization’s member roster (owners only) and the activity targets set for the team.

What it can change

38 tools write. They do exactly what the equivalent button in the app does — same permission checks, same validation, same credit accounting — driven by Claude instead of a click. Anything that spends credits is quoted to you first: Claude tells you what it will cost and what your organization has left, and only goes ahead once you say so.

  • Content · 8
    Generate a post with AI, create and edit drafts (including attaching an image by URL), schedule a draft for automatic publishing to LinkedIn, publish a draft to LinkedIn immediately, unschedule a scheduled draft, delete a draft, and set up your personal writing style.
  • Leads · 5
    Add profiles by LinkedIn URL, enrich leads you already have, assign leads to teammates, delete leads (owners only), and push a lead out to your connected HubSpot or Salesforce (owners only). Anything that costs credits is quoted first: Claude shows the exact cost and what your balance will be afterwards, and can only spend against a quote you approved.
  • Lead lists · 6
    Create, rename and delete lists, add and remove leads from them, and flag leads as ready for outreach.
  • Watchlist and engagement · 4
    Remove profiles from the watchlist, generate a comment with AI, post a comment on LinkedIn, and react to a post on LinkedIn.
  • Feed state and keywords · 3
    Claim, unclaim or mark posts as seen for your team, and subscribe or unsubscribe from feed keywords.
  • Comment automation · 3
    Change your automation settings (daily cap, approval mode, quiet hours), and approve or reject a queued draft.
  • Knowledge base · 2
    Add a text note to the knowledge base, and delete an asset.
  • ICPs · 5
    Create, edit and delete ICPs, recompute their matches, and apply them to a lead list.
  • Team and targets · 2
    Invite a person to your organization by email (owners only), and set the team’s activity targets.

The six actions that leave GTM Brigade

Most writes only change data inside your account. These six do not — they are visible to other people, and they cannot be taken back from here:

  • Publish a post. Publishes one of your drafts immediately and publicly on LinkedIn, under your own LinkedIn identity, using the LinkedIn account you connected in the app. There is no scheduler in between and no undo from GTM Brigade — once it is live, taking it down is a manual job on LinkedIn itself.
  • Post a comment. Publishes immediately and publicly on LinkedIn, under your own LinkedIn identity, using the LinkedIn account you connected in the app.
  • React to a post. Sets your reaction immediately and publicly on LinkedIn, under your own identity.
  • Approve a comment-automation draft. Schedules that comment; our publisher posts it publicly on LinkedIn as you, with no further confirmation.
  • Invite a team member. Sends an invitation email to the address you name.
  • Push a lead to your CRM. Writes that lead's details — name, email, company, job title, LinkedIn URL — into your connected HubSpot or Salesforce. This one is different from the others: it goes out under your organization's shared CRM connection rather than your personal one, so it is restricted to owners. It matches on email address, so pushing the same lead twice updates the existing record instead of creating a duplicate — and a lead with no email address is refused outright, which in practice rules out most LinkedIn-sourced leads until you add one. In Salesforce it creates a Lead, not a Contact, so your own Lead-to-Contact conversion stays yours to run.

Scheduling a post is worth knowing about alongside these: it does not publish when you ask, but GTM Brigade will publish it to LinkedIn for you at the scheduled time. Undo it with the unschedule tool before it fires. It is the calmer sibling of publishing immediately — prefer it unless you really mean “now.”

What “destructive” means here

Six tools are flagged destructive, which is what makes Claude warn you before running them. None of them is a hard wipe:

  • Remove from watchlist. Deletes that profile’s collected posts, comment suggestions and assignees in your organization. The person stays in your lead database — they are demoted from watched profile to lead, never fully deleted.
  • Delete lead. The app’s soft delete: the lead disappears from your database and its list memberships are removed. Recoverable only by us, on request. Owners only, 50 per call.
  • Delete lead list. A soft delete of the list and its memberships. The leads themselves are not deleted and stay in your org. Default lists, such as the watchlist, cannot be deleted at all.
  • Delete draft. Permanently deletes one of your own drafts. Refuses anything scheduled or already published — you have to unschedule first.
  • Delete knowledge-base asset. Removes the stored file and its semantic index entries. Same rule as the app: your own assets, or any asset if you are an owner.
  • Delete ICP. Permanently deletes the ICP, its signals and its lead matches. Owners only.

Access & permissions

The connector respects the exact same permissions as the app. Who you are and what you may do are worked out on our side from the account you signed in with — never from anything Claude sends us. If Claude asks for another organization's data, the request simply does not resolve.

Every member can read and act on their own work. Owner-only tools — team leaderboard, team overview, Company Page analytics, member roster, invitations, lead deletion, ICP deletion — give a member a plain “requires owner access” message, never another person's data. Everything is scoped to the organizations you belong to.

Safety controls

  • Granular scopes. Access is split across 16 permissions — reading analytics, reading leads, writing leads, writing content, engagement, knowledge base, team, ICPs, settings. Each tool checks its own scope before doing anything, so a connection granted part of the list reaches exactly that part.
  • Per-user, per-organization isolation. Every query is scoped to your organization on our side. Your private personal knowledge-base assets stay isolated to you, including when Claude generates content from them.
  • Hourly budgets on outward actions. Public LinkedIn actions, invitations and AI generations each have their own per-hour cap per user. A runaway agent loop hits the cap and stops with a clear message instead of spamming anyone.
  • Claude asks first. No write tool is marked read-only, so your client prompts you before running one — and warns harder on the destructive and outward-facing ones.
  • Your normal audit trail. Writes run through the same code paths as the app, so they land in the same records — activity logs, credit ledger and audit log — attributed to you.
  • Yours to revoke. Remove the connector in Claude at any time. Access tokens are short-lived and bound to this connector and your account.

What it deliberately cannot do

Some things were left out on purpose, because doing them safely needs more than a wrapper:

  • Repost. GTM Brigade has no repost action anywhere, and the connector does not invent one.
  • Message anyone on LinkedIn. There is no tool to send a DM, an InMail, or a connection request. The connector can comment and react in public; it cannot slide into anyone's inbox.
  • Change roles or remove members. It can invite, and that is all — a decision we made deliberately, not a gap. Lockout and billing consequences stay with a human.
  • Buy anything. No checkout, no plan changes, no payment details. Billing is read-only: consumption, invoices, plans.
  • Merge or hard-delete leads. Lead deletion is the app's recoverable soft delete; merging duplicates is not exposed at all.
  • Upload files. Text notes to the knowledge base, yes. File uploads stay in the app.
  • Touch platform administration. Our internal staff tooling is not on the connector at all.

Privacy

See our privacy policy for what the connector accesses, what it changes, and who your data is shared with when you use it.

Support

Questions or issues? Email support@gtmbrigade.com.