Skip to main content
Klipy’s MCP server works with any client that supports remote HTTP MCP servers and OAuth 2.0, not just Claude and ChatGPT. Clients like Cursor support adding a remote MCP server through their own settings, using the same server URL and OAuth flow described on this page. Every write action still goes through Klipy’s normal review.
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 another MCP client to Klipy?

1

Open your client's MCP or connector settings

Check your client’s documentation for where it manages MCP servers — this is usually under a settings section named “MCP,” “Connectors,” or “Integrations.”
2

Add Klipy as a remote HTTP server

Add a new server pointing at:
The exact labels and fields vary by client — look for a remote/HTTP MCP server or custom connector option. Most ask for a name and a server URL, and some let you paste a full JSON server entry.
3

Complete the OAuth flow

Your client should redirect you to sign in and authorize access. Approve the request, then return to your client — Klipy’s tools are now available.
4

Verify it works

Ask your client’s chat:
Your client 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 my client is connected?

Enable the Klipy connector in your client to put its tools to work in any chat.

Explore what you can do

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