What connecting ChatGPT to Klipy actually does
ChatGPT is one of the most capable general-purpose assistants around, and plenty of sellers already lean on it daily for drafting, research, and thinking out loud. On its own, though, it has no CRM, no deal memory between chats, and no pipeline. Every session starts from zero: you paste in whatever context you have by hand.
Connect ChatGPT to Klipy over MCP and that changes. ChatGPT reads the same CRM records Klipy already holds, along with your inbox captures and meeting history, and drafts through Klipy's own review queue instead of leaving the output stranded in a chat window. ChatGPT keeps doing what it already does well; the connection just gives it a memory it doesn't have natively.
How ChatGPT connects to Klipy
The mechanism is ChatGPT's own developer-mode custom-connector flow, pointed at Klipy's public MCP endpoint, https://api.klipy.ai/mcp. It isn't a bundled connector inside Klipy's own settings; ChatGPT adds Klipy the same way it would add any external MCP server.
Turn on developer mode, add the server URL, and authorize with OAuth. Klipy shows a consent screen with one checkbox per capability scope, and from that point on ChatGPT can call only the tools under the scopes you approved. These scopes apply to every AI agent connected to your Klipy account, not just ChatGPT: connecting a second agent, or re-approving ChatGPT later with broader scopes, changes what all of them can do, since the most recent grant is the one that governs.
Developer mode itself is a ChatGPT-side requirement: it needs a ChatGPT Pro, Plus, Business, Enterprise, or Education plan, and on a workspace plan an admin may need to turn it on first.
Every write action ChatGPT proposes still goes through the same review Klipy applies everywhere else in the app. See how do I connect Klipy to my assistant? for the full scope reference.