Connect ChatGPT to your CRM

SalesCrew's MCP server hands ChatGPT 140+ tools. It works inside your login's scopes, and outside sends queue for a person to approve.

An admin approves every new account by hand. Nothing is created until then. We reply by email; no newsletter, no sequence.

  • Works through MCP
  • Writes only when you allow
  • One approval queue
app.salescrew.io/settings
Settings: MCP tokens, integrations and the audit log

The short answer

  • SalesCrew connects to ChatGPT through its MCP server. ChatGPT reaches MCP servers through its own connector settings, and once SalesCrew is added it can read and update your pipeline in plain language.
  • Writes are opt-in per token. A token minted without Allow writes can answer questions all day and never change a record.
  • Every tool ChatGPT calls is the twin of a button in the app, so an update from chat is identical to one made by hand. Nothing lives only in the chat window.
  • Emails, LinkedIn messages and proposals that ChatGPT prepares wait in the SalesCrew approval queue by default, next to the evidence and the cost.

Mechanism

What a ChatGPT request turns into inside SalesCrew.

WhatMechanismDirectionObjectsStatus
Ask about the pipelinepipeline_query, stalled_deals, next_actions_listOutboundDeals, tasksAvailable
Update a dealdeal_update_stage, deal_contact_add, note_addInboundDeals, notesAvailable
Update a contactcontact_update, lead_update, task_createInboundContacts, leads, tasksAvailable
Prepare a replyinbox_draft_reply, then the approval queueInboundDrafts, approval itemsAvailable
Daily summarydaily_briefing and record_summaryOutboundPipeline, inbox, channelsAvailable
Access controlPer-user token with channel, profile and area scopesInternalMCP tokensAvailable

Tool names read from the SalesCrew MCP server, September 2026. OpenAI's own help pages are the authority on where ChatGPT keeps its connector settings.

Setup

A token in SalesCrew, a connector in ChatGPT, then a test question.

  1. 1

    Mint a personal token

    Settings → API access (MCP) in SalesCrew. Label it "ChatGPT" and tick Allow writes only if ChatGPT should change records. Copy the token, because it's shown once.

  2. 2

    Copy your server URL

    The same settings page shows your instance's MCP server address. Every SalesCrew instance has its own.

  3. 3

    Add SalesCrew in ChatGPT

    In ChatGPT's connector settings, add a custom MCP server. You'll give it the SalesCrew URL and your personal token, following OpenAI's steps for your plan.

  4. 4

    Ask a read question first

    Try "which deals haven't moved in 14 days?" before you ask ChatGPT to change anything. If the answer matches the kanban, the scopes are right.

  5. 5

    Watch the approval queue

    Ask for a follow-up email and it appears in the SalesCrew queue, not in the prospect's inbox. Approve or reject it there.

One token per person, never a shared one

A shared token makes the audit log say "ChatGPT" for everyone, and one leaver means rotating it for the whole team. Personal tokens cost nothing extra because seats are unlimited on every plan.

Questions

Can ChatGPT update deals and contacts in SalesCrew?
Yes, when your token allows writes. ChatGPT calls the same tools the app uses, such as deal_update_stage, contact_update and note_add, and each change has the same effect as clicking it in the UI.
What stops ChatGPT from emailing a prospect by mistake?
The approval queue. Any external send defaults to review, so a prepared email waits until a person approves it, and the decision is logged with that person's name.
Does each salesperson need their own connection?
Yes, and that's the point. Each person mints a personal token, so ChatGPT sees only what that person's login sees and the audit log shows who did what. Seats are unlimited on every plan.
Can I switch ChatGPT off for the whole team at once?
Revoke the tokens in Settings → API access or with mcp_token_revoke. For SalesCrew's own agents, the kill switch on the Agents page stops every agent in one move.

Put ChatGPT on your pipeline, with a person on the send button

140+ tools, per-user scopes, and every outside message held in one queue.

An admin approves every new account by hand. Nothing is created until then. We reply by email; no newsletter, no sequence.