Skip to main content
Klipy connects to Claude Code through the same remote MCP server every client uses. Add the server with one command in your terminal, then authenticate with OAuth. Once connected, ask Claude Code about your Klipy pipeline, contacts, and conversations directly from the terminal; every write action still goes through Klipy’s normal review process.
Klipy’s MCP server is supervised — every write action still goes through the same review Klipy applies everywhere else. See how the MCP server works before connecting.

​
How do I connect Claude Code to Klipy?

1

Add the Klipy MCP server

From your terminal, run:
This adds Klipy as a local-scoped HTTP server for the current project. If you want Klipy available across every project on your machine, add --scope user:
2

Authenticate with OAuth

Klipy’s MCP server requires OAuth 2.0. Inside a Claude Code session, run:
Select klipy and follow the browser login flow. You can also authenticate directly from your shell without opening a session:
Connecting over SSH or another environment without a local browser? Claude Code detects this and prints an authorization URL instead of opening a browser. Open that URL on your local machine, then paste the full redirect URL from your browser’s address bar back at the prompt. Use ssh -t so the paste step has an interactive terminal, or pass --no-browser to force the URL prompt.
3

Verify it works

Ask Claude Code:
Claude Code calls the get_current_user tool and returns your Klipy account details. If it responds with your name and workspace, the connection is authenticated and ready.

​
What can I do once Claude Code is connected?

Ask Claude Code about your Klipy pipeline, contacts, or conversations from any terminal session.

Explore what you can do

See example prompts and workflows once Claude Code is connected.
Last modified on July 30, 2026