drift_create_ conversationStart a new conversation with a contact by email, for example to continue something that began on another channel.
Ask who chatted with your team today, read a whole conversation with the contact beside it, leave a private note or answer a visitor, and see which meetings got booked, all from the Drift account your team already runs.
PopMCPDrift
Every operation in Drift's API, with the everyday conversation and contact tools loaded by default and the rest, from privacy requests to user provisioning, one search away.
46 tools in the full catalog: 28 read and 18 write. 35 load by default, and the rest are found with tool search.
drift_create_ conversationStart a new conversation with a contact by email, for example to continue something that began on another channel.
drift_download_ attachmentDownload a file attached to a message.
drift_get_ conversationRead one conversation: status, participant user ids, contact id, inbox id, tags, the playbook it came from and times.
drift_get_ conversation_ statsCount the conversations in this Drift account by status: open, closed and pending, with a total.
drift_get_ conversation_ transcriptRead a conversation as one formatted text transcript.
drift_list_ conversation_ messagesRead a conversation's messages, 50 to a page, including private notes.
drift_list_ conversationsList conversations, most recently updated first, optionally by status.
drift_run_ conversation_ reportReport on conversations with filters and metrics, for example every closed conversation in a date range with its time to close and message counts.
drift_send_ messagePost a message in a conversation.
drift_create_ contactCreate a contact.
drift_create_ timeline_ eventAdd an event to a contact's timeline in Drift, such as "Requested a demo from <your app>".
drift_delete_ contactRemove a contact from the Contacts view in Drift.
drift_find_ contactsLook contacts up by email or by your own external id.
drift_get_ contactRead one contact, with all their attributes, by Drift contact id.
drift_list_ contact_ attributesList every contact attribute in this Drift account with its internal name, display name and type (STRING, NUMERIC, BOOLEAN, DATETIME or DATE).
drift_unsubscribe_ contacts_ from_ emailsUnsubscribe contacts from Drift emails, by email address.
drift_update_ contactChange a contact's attributes by Drift contact id.
drift_create_ accountCreate a company account in Drift.
drift_delete_ accountHide a company account from the list in Drift.
drift_get_ accountRead one company account by id.
drift_list_ accountsList the company accounts in Drift (used for account-based marketing), with owner, domain and custom properties, and the total.
drift_update_ accountUpdate a company account.
drift_get_ conversation_ contextRead one whole conversation in one call: status, tags and playbook, the contact's details, the participants' names, and the messages oldest first as plain text with each author's name, including private notes.
drift_get_ conversation_ transcriptsRead the text transcripts of up to 10 conversations at once, to summarize or review a batch.
drift_get_ userRead one user (agent or bot) by id.
drift_get_ workspace_ overviewStart here.
drift_list_ recent_ conversationsList conversations, most recently updated first, with each contact's name and email instead of only an id.
drift_list_ usersList every user (agent or bot) in this Drift account with id, name, email, role and availability.
drift_update_ userChange an user's details, or set them available or offline for chat.
drift_list_ conversational_ landing_ pagesList the conversational landing pages that are enabled, with playbook id, name and page link.
drift_list_ playbooksList the bot playbooks that are enabled and active, with name, goals, type, authors and interaction id.
drift_list_ teamsList every team in this Drift account with its members, owner, status and availability mode.
drift_list_ user_ teamsList the teams one user belongs to.
drift_get_ token_ infoShow what this connection can reach: the Drift organization id, the scopes on its token, and when the token expires.
drift_list_ booked_ meetingsList meetings booked in this Drift account between two times, with the agent, the scheduling contact, the conversation, start and end.
drift_get_ conversation_ json_ transcriptRead a conversation's transcript as structured JSON rather than formatted text.
drift_update_ contact_ by_ external_ idChange a contact's attributes using your own external id, or Drift's anonymous id, instead of the Drift contact id.
drift_scim_ create_ userAdd a teammate to Drift through SCIM, on Drift's paid plans.
drift_scim_ delete_ userDelete an user account through SCIM, on Drift's paid plans.
drift_scim_ get_ userRead one user account through SCIM, on Drift's paid plans.
drift_scim_ list_ usersSearch user accounts through SCIM, the provisioning interface, on Drift's paid plans.
drift_scim_ replace_ userReplace an user account through SCIM, on Drift's paid plans.
drift_scim_ update_ userChange fields on an user account through SCIM, on Drift's paid plans.
drift_get_ usersRead up to 20 users at once by id, such as a conversation's participants.
drift_request_ gdpr_ deletionPermanently erase all data (attributes, conversations, messages and more) for every contact and user with an email address.
drift_request_ gdpr_ retrievalAsk Drift to gather all data for every contact and user with an email address, for a privacy request.
Credentials off one Drift screen, then an endpoint your client signs into. Nothing to deploy, and nothing to install.
A Drift admin makes a small private app at dev.drift.com: Build Your App, turn scopes on under OAuth & Permissions, then Install App to Drift. They paste the access token it shows into PopMCP, which checks which organization it belongs to and locks the connection to it.
••••••••••••3f7aSending messages, changing contacts and privacy requests are writes and wait until an owner or admin allows write actions; new connections start read-only. A chat message reaches a real visitor straight away, so teammates who only need answers stay on read-only, and a token made with only the read scopes cannot change anything at all.
Drop the PopMCP URL into Claude, ChatGPT, Claude Code, Codex or any other supported client. It signs in through PopMCP with OAuth, so your Drift credential never leaves the server.
app.popmcp.com/mcpAsk for something harmless before the agent changes anything. Writes run as soon as it calls them, so confirm it reads the right account first.
Who has chatted with us since yesterday, and what did each person want?
drift_list_recent_conversationsok
Then just ask for the work
“Who has chatted with us since yesterday, and what did each person want?”
“Read my latest open Drift conversation and leave a private note for the team with a suggested reply”
“Look up ana@example.com in Drift and add the event Requested a demo to her timeline”
“Which meetings were booked through Drift this month, and with whom?”
“How many conversations are open right now, and which teammates are available to answer them?”
“Find every closed conversation from last week and how long each one took to close”
One hosted endpoint, registered once per client. The same tools and the same permissions, whichever window the request comes from.
Add the PopMCP URL under Customize → Connectors and the tools appear in every chat.
The same endpoint, registered in the browser. Nothing to install on the machine you are working from.
Register PopMCP as a custom connector, then let ChatGPT read and update the account.
Wire the endpoint into Codex or the Codex CLI when a task needs live business context, not a fixture.
Register the remote MCP server in OpenCode's config for terminal-first and scripted agent runs.
Add PopMCP as an MCP server in Z.ai's desktop app and work the account from the same window.
FAQ
What teams ask before putting Drift behind an AI client.
Clari + Salesloft, which owns Drift, announced a gradual sunset in March 2026 and named 1mind as the successor. It has not published an end date, and Drift's app and API were still answering when this page was written. This connector is for teams still on Drift, and it works for as long as your Drift account does. It is also a practical way to read your conversations before you move.
One access token. A Drift admin goes to dev.drift.com, clicks Build Your App, turns on the scopes it should reach under OAuth & Permissions, and clicks Install App to Drift. That shows a token that does not expire. Paste it into PopMCP, which checks which organization it belongs to, stores it encrypted and locks the connection to that organization. The token never reaches your AI client.
Only if you allow it. The token needs the conversation_write scope, and the connection in PopMCP has to allow write actions, because new connections start read-only. Even then, a private note stays inside your team: only a chat message reaches the visitor, and it goes straight away and cannot be taken back.
A Drift token keeps the scopes it had when it was made. Turn the scope on for your app under OAuth & Permissions at dev.drift.com, install the app again and paste the new token into PopMCP. The error names the scope, and get_token_info shows what the connection has.
Not through Drift's API, which finds contacts by email or by your own id and has no call that lists them all. For a whole list, use the CSV export in Drift. Conversations are different: the AI can page through them, and run_conversation_report finds them by date.
No. delete_contact only removes them from the Contacts view. request_gdpr_deletion erases their conversations, messages and attributes for good, and it cannot be undone. Both are write actions, and the privacy calls only work with a token from your own organization's app.
No. PopMCP removes IP addresses, browser strings and exact positions from what it returns for messages and contacts. The AI still sees the page a visitor was on and their city, region and country when Drift has them.
No. PopMCP hosts it and gives you a Streamable HTTP MCP URL. There is nothing to deploy, no callback URL to register, and no infrastructure to keep running or patch.
Any client that supports a remote Streamable HTTP MCP server: Claude Desktop, Claude Web, Claude Code, ChatGPT custom connectors, Codex and the Codex CLI, OpenCode and Z.ai's ZCode, as well as editors such as Cursor, Windsurf and Zed. Your client signs in to PopMCP with OAuth; the provider credential never leaves the server.
Connect Drift in PopMCP first, then run claude mcp add --transport http popmcp https://app.popmcp.com/mcp in a terminal. Inside Claude Code, run /mcp and sign in to PopMCP in the browser window it opens, ticking Drift on the consent screen. The Drift tools are then available in that session, and no Drift credential is stored on your machine.
Loading 46 tool definitions into every conversation burns context before the work starts. PopMCP loads a curated 35-tool set covering the everyday workflows and keeps the rest searchable, so your AI pulls a specialist tool only when a task needs it. Every tool stays searchable, and on Scale the owner can load the full catalog for a teammate's connection.
A tool is something your AI calls, and there are 46 here. A trigger is something PopMCP watches for you: 7 Drift events that can start work on the PopMCP side. Triggers never enter your AI client's context, and none of them ask you to paste a callback URL into Drift.
Launch a hosted MCP endpoint for Drift, keep tool access under control, and start testing real workflow prompts right away.