Does Klipy have a native Claude Cowork integration?

Klipy has an MCP server at https://api.klipy.ai/mcp that any remote-MCP client, including Claude Cowork, connects to over OAuth. There's no bundled one-click Cowork-specific connector and no dedicated Klipy connect guide for Cowork yet, so setup follows the same generic remote-MCP-client flow Klipy documents for clients beyond Claude Desktop, Claude Code, and ChatGPT.

Can Claude Cowork send emails or messages on my behalf through Klipy?

Only after you approve the exact final message. Klipy's send handshake requires a fresh confirmation token from prepare_message_send and your explicit approval before send_message_draft dispatches anything. Reading data and drafting cost nothing; nothing sends on its own.

What can an agent connected through Claude Cowork actually see in my Klipy account?

Only what the OAuth scopes you grant allow. Klipy's MCP server exposes 38 tools behind 9 scopes (CRM read and write, communications read and draft, meetings read, agent read and write, account read, and the gated send scope); a connection can only call tools whose scopes you checked during consent.

Do I need a paid Klipy plan to connect Claude Cowork?

No. Klipy's MCP server is available on every Klipy account, including Free, with no separate plan or beta gate.

Does connecting Cowork cost tokens?

Reading your CRM, inbox, and meetings, and preparing drafts, are free. You only spend tokens when you accept an action, like sending a draft.

MCP agent

Run your CRM from Claude Cowork

Connect Claude Cowork to Klipy's MCP server over OAuth so your agent can read deals, draft follow-ups, and answer grounded questions, all supervised by you.

Start free See all integrations

Free on every plan

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

Quick answer

Klipy runs an MCP server at https://api.klipy.ai/mcp that any remote-MCP client can connect to over OAuth, and Claude Cowork connects the same way Claude Desktop, Claude Code, and ChatGPT already do. Once connected, the agent inside Cowork can read your CRM, inbox, and meetings across 38 tools and 9 consent scopes, and draft follow-ups. Nothing sends without your explicit approval.

Ask ChatGPT Ask Perplexity Ask Claude

At a glance

What you need to know

38

MCP tools

One connection covers CRM, comms, meetings, and agent actions inside your Cowork workspace.

9

OAuth scopes

You grant only the capability scopes your workflow needs, the same consent screen every remote-MCP client uses.

$0

On every plan

Klipy's MCP server is free on every Klipy account, including Free, with no separate plan or beta gate.

Claude Cowork is a real, fast-growing part of Anthropic's agentic workspace lineup: 110,000 monthly US searches at last count. On its own, though, it has no way to touch your CRM. It can't read your deals, your inbox, or a meeting your team just recorded.

The gap: Claude Cowork can't touch your CRM on its own

Klipy closes that gap with an MCP server at https://api.klipy.ai/mcp that any remote-MCP client can connect to over OAuth, Claude Cowork included. Once connected and the relevant scopes are granted, the agent inside your Cowork workspace can search and read CRM records (people, companies, deals, notes, tasks, pipelines), pull up email and meeting history with citations, read call transcripts and calendar events, and draft follow-ups for you to review. Nothing goes out until you approve the exact final message.

Cowork sits inside a wider, currently trending product family (searches for claude crm are up over 1,300% year over year, though still low in raw volume), and it's the daily agentic workspace in that family rather than a one-off chat window, which is part of why a real MCP connection to a CRM for Claude Cowork matters more here than it would for a single chat session.

How it connects: OAuth to a single MCP endpoint

Connecting Cowork to Klipy is not a one-click, Cowork-specific integration. It's the same remote-MCP-client flow Klipy documents for any client beyond its three named guides (Claude Desktop, Claude Code, ChatGPT), and it's the flow you'd use to connect Claude Cowork to a CRM in general:

Open Cowork's MCP or connector settings and add a remote server at https://api.klipy.ai/mcp.
Complete Klipy's OAuth consent screen, checking the scopes your workflow needs, out of 9 total.
Verify the connection with a plain-language prompt: "Who am I in Klipy?" This calls get_current_user and returns your Klipy identity, organization, role, connected accounts, and the scopes you consented to.

Klipy's docs don't yet have a Claude-Cowork-specific connect guide, unlike Claude Desktop, Claude Code, and ChatGPT, which each have one. Until that guide ships, this page routes through the generic flow above, and we keep Cowork's own side of the setup deliberately general here (look for Cowork's MCP or connector settings) rather than naming a specific menu path we haven't verified against Anthropic's own documentation.

Use cases

What you can do with it

I can now let my Klipy agent's suggestions from a meeting update the CRM, instead of typing it in by hand.

Read the suggestions Klipy already proposed from a recorded meeting and apply only the ones you accept.

CRM updates

I can now draft a follow-up grounded in the actual call and send it through Klipy's own review step.

Pull up a specific call, draft off the transcript and prior email history, then review and send.

Follow-up emails

I can now ask one question across every conversation with an account and get a cited answer, not a guess.

Get an answer grounded with citations back to the source interaction, not the open web.

Ask your data

Trade-offs

Pros and cons

Pros

Direction is explicit: Cowork connects to Klipy, and the agent only calls tools it has consented scopes for
Klipy's MCP server is available on every Klipy account, including Free, with no separate plan or beta gate
Reading and drafting cost nothing; sending requires a fresh confirmation token and your explicit approval every time
Same connection mechanism Klipy already supports for Claude Desktop, Claude Code, and ChatGPT, a proven flow, not a one-off

Cons

No Claude-Cowork-specific connect guide exists yet, so setup here follows Klipy's general remote-MCP steps rather than a dedicated walkthrough
Cowork's own MCP or connector settings menu isn't something we've verified firsthand against Anthropic's documentation, so this page keeps that half generic on purpose
Full access (read, draft, and send) needs all three scope groups checked at connect time, or a return trip to re-consent later
Claude Cowork is a newer product, so expect Klipy's Cowork-specific guidance to keep expanding as more of the connection gets verified end to end

Sources