Does connecting Gemini change how Klipy captures data?

No. Klipy keeps capturing Gmail, Outlook, meetings, and the rest exactly as it does today. Connecting Gemini over MCP only gives Gemini read and write access to that same account data, through whichever of the nine scopes you grant.

Can Gemini send messages on my behalf?

Only through Klipy's two-step gated handshake: Gemini calls prepare_message_send to get a preview and a single-use confirmation token, shows you that exact message, and only after you approve does send_message_draft dispatch it. Nothing sends automatically.

Do I need a paid Klipy plan to connect Gemini?

No. Klipy's MCP server is generally available on every account, no separate plan or beta waitlist. Tokens are only spent when you accept a suggestion or a send, not for reading or drafting.

Is there a step-by-step Gemini connect guide?

Not yet a Gemini-named page. Today's steps follow Klipy's generic any-client MCP flow: add https://api.klipy.ai/mcp as a remote HTTP server in your client's connector settings, complete OAuth, and verify by asking "Who am I in Klipy?"

What if Gemini's tool list looks outdated after a Klipy update?

Remove and re-add the Klipy connector in Gemini to force a fresh fetch of the tool catalog. This is a client-side cache, not a Klipy outage.

MCP agent

Gemini works alongside Klipy through an MCP server

Gemini connects to Klipy's MCP server and reads your deals and conversations, drafts follow-ups, and sends only once you approve.

Start free See all integrations

Gemini connects to Klipy's MCP server at api.klipy.ai/mcp over OAuth, the same open endpoint every MCP client uses. Once authorized, it reads your contacts, deals, inbox, and meeting data across nine scopes and drafts messages for review. Nothing sends without your explicit approval through Klipy's two-step handshake.

Gemini has no native connection into your account data. Added as an MCP client at Klipy's open server (api.klipy.ai/mcp), it can search and read people, companies, and deals, read email and meeting interactions, and draft follow-ups and recaps for you to approve. Access runs through nine capability scopes and the same two-step send handshake every Klipy MCP client uses, so nothing goes out until you say so.

Free on every plan

Connecting Gemini is included on every Klipy plan, including Free. API access, webhooks, and the MCP server ship standard, with no add-on fee.

Quick answer

Gemini connects to Klipy's MCP server at api.klipy.ai/mcp over OAuth, the same open endpoint every MCP client uses. Once authorized, it reads your contacts, deals, inbox, and meeting data across nine scopes and drafts messages for review. Nothing sends without your explicit approval through Klipy's two-step handshake.

Ask ChatGPT Ask Perplexity Ask Claude

At a glance

What you need to know

OAuth

One-way connection

Gemini calls into Klipy over MCP at api.klipy.ai/mcp; Klipy never reads or writes inside Gemini or Google Workspace.

9

OAuth scopes

Grant exactly what a workflow needs, from read-only research to the full draft-and-send handshake.

$0

On every account

Klipy's MCP server is generally available today, no separate plan or waitlist; reading and drafting cost no tokens.

What Gemini can't do on its own, and what this connection adds

Gemini has no native link into your deal and contact data. Connected as an MCP client to Klipy's open server at https://api.klipy.ai/mcp, it gains read and write access to the same people, deal, inbox, and meeting data you already manage inside Klipy.

The connection runs over the identical endpoint that Claude Code, ChatGPT, and any OAuth-capable MCP client point at, gated by the same nine capability scopes and the same two-step send handshake: prepare_message_send returns a preview and a single-use confirmation token, and only send_message_draft with that fresh token actually dispatches anything. Once you grant the scopes a workflow needs, Gemini can search and read people, companies, and deals, read email and meeting interactions, draft follow-ups and recaps, and, with your explicit approval each time, send them.

The direction only runs one way. Klipy doesn't read or write anything inside Gemini or Google Workspace. Gemini's own Gmail and Calendar connections are a separate system and stay exactly as they are; that side of capture is documented on Klipy's Gmail integration page, not here.

How to connect Gemini to Klipy

Add Klipy as a remote MCP server in Gemini's connector or MCP settings, using the endpoint:

text

https://api.klipy.ai/mcp

Complete the OAuth consent screen, checking only the scopes your workflow needs, for example crm:read and meetings:read for research-only use, plus comms:draft if you also want Gemini to prepare follow-ups. Confirm the connection by asking "Who am I in Klipy?", which calls get_current_user and returns the account behind it.

Klipy doesn't yet publish a Gemini-named connect guide the way it does for Claude Desktop, Claude Code, and ChatGPT, so the steps above follow the documented any-client MCP flow instead. Gemini CLI users add remote servers through its MCP configuration and are the ones most likely to complete this setup today. We didn't independently confirm the exact menu steps against Gemini's own live documentation for this page, so check your specific client's settings, whether that's the Gemini app, Gemini CLI, or a Vertex AI-built agent, before connecting.

If Gemini's tool list looks stale after a Klipy update, remove and re-add the connector to force a fresh fetch of the catalog. That's a documented client-side cache behavior, not a Klipy outage. See MCP troubleshooting for more.

Use cases

What you can do with it

I can now ask a grounded question across every conversation with an account instead of re-reading a dozen threads.

Gemini calls ask_klipy and answers with citations back to the source, read-only, no tokens spent.

Ask your data

I can now walk into a call with a pre-built brief pulled from the calendar event, account record, and last call's transcript.

Gemini reads the calendar event, account record, and interaction timeline before the meeting starts.

Pre-call research

I can now turn a recorded meeting into a recap and a drafted follow-up I approve before it sends.

Gemini surfaces the next-step suggestions Klipy already proposed from the call for me to accept.

Meeting recaps

Trade-offs

Pros and cons

Pros

No migration. Gemini keeps doing what it already does; Klipy is just one more MCP server it can call.
Nine scopes let you grant exactly what a workflow needs, from read-only research to the full draft-and-send handshake.
Reading data and preparing drafts cost no tokens; a token is spent only when you accept a suggestion or a send.
Generally available on every Klipy account today, no separate plan or beta waitlist.

Cons

No Gemini-specific connect guide yet; setup follows the generic any-client steps, not a named Gemini walkthrough.
Whether your particular Gemini surface supports a remote MCP server over OAuth depends on that product; confirm before connecting.
This MCP link is separate from Gemini's own Google Workspace connections; connecting doesn't change how Klipy captures Gmail or Calendar.
A client's cached tool list can go stale after a Klipy update; removing and re-adding the connector is the documented fix.

Sources