ClipzingClipzing
Log In
Sign Up
Setup guide

Connect Clipzing to your agent

Your agent gets the controls. The skills teach it how to use them well.

  • About 2 minutes
  • No API key to copy
  • 9 apps, or your own agent

Claude Desktop

The Claude app on your Mac or PC

Needs uv

Add the MCP server

  1. Install uv (one time)

    Clipzing's MCP server runs through uv, which does not ship with macOS. Skip this if you already have it.

    curl -LsSf https://astral.sh/uv/install.sh | sh
    Then open a new terminal window, so it is on your PATH.

  2. Open the config file

    ~/Library/Application Support/Claude/claude_desktop_config.json
    Or in the app: Settings → Developer → Edit Config. It opens this same file.

    If the file does not exist, create it. That is normal on a fresh install. Make the folder too if it is missing, then paste the block below as the whole file.

  3. Paste this in

    Whole file, if it was emptyjson
    {
  "mcpServers": {
    "clipzing": {
      "command": "uvx",
      "args": ["clipzing-mcp"]
    }
  }
}

    Already have other MCP servers in there?

    Do not replace the file. Add only the "clipzing" line inside your existing "mcpServers" block, and keep the comma rules of JSON: every entry except the last needs a trailing comma. A stray or missing comma makes the app silently load no servers at all.

  4. Restart the app

    Quit Claude completely and reopen it. A window reload is not enough.

  5. Approve the connection in your browser

    The first time your agent uses Clipzing, your terminal or the app log shows a short code and a browser tab opens at clipzing.com/link. Sign in if you are not already, check the code matches, and choose what the agent may do.

    Reading is the default

    Editing, rendering and publishing are separate opt-ins, and deleting or publishing always asks you again at the moment it happens. The credential is stored in your computer's keychain, not in the file you just edited, and you can revoke it any time under Billing, API keys.

  6. Check that it worked

    Ask your agent:

    If it answers with your clips, you are done. If it says it has no such tool, see troubleshooting.

Add the skills

Optional, recommended

The MCP server gives your agent the controls. The skills tell it how an experienced editor uses them: where to cut, what makes a hook work, how to judge a clip before publishing. Without them the agent can still do everything, it just decides less well.

Skills are an open standard (agentskills.io), so the same files work in Claude Code, Cursor, Windsurf and Zed. Only the folder differs.

Download the skills (.zip)Browse on GitHub

Using skills with Claude Desktop

Claude Desktop loads skills through your Claude account rather than a folder on disk, and we have not verified that upload flow well enough to walk you through it. The reliable route today is Claude Code, which reads ~/.claude/skills/. Pick "Claude Code" above for the exact folder and a one-line install.

Try these first

Tap one to copy it.

If something did not work

"uvx: command not found"

uv is not installed, or your terminal has not picked it up yet. Run the install command from step 1 and then open a NEW terminal window, because the old one still has the old PATH.

The agent says it has no Clipzing tools

Almost always the restart. Quit the app completely rather than reloading the window, and start a fresh session. If it still shows nothing, your JSON has a syntax error: a missing or extra comma makes the app load no servers at all rather than complain.

No browser tab opened, or I missed it

The code lasts 10 minutes. Go to clipzing.com/link and type the code shown in your terminal, or just restart your agent to get a fresh one.

It says it is connected but has no Clipzing tools

The app caches the tool list from the moment you added the connector. If it was added while something was failing, it stored "zero tools" and will not re-check on its own. Remove the connector and add it again, which is the only thing that makes it re-read the list. Everything else, including your sign-in, is unaffected.

"Agent access is not included on your current plan"

Agent access is a paid feature. Starter covers reading and editing; Pro adds rendering and publishing.

"405 Method Not Allowed", or an SSE error, from my own agent

Your agent is using the older SSE transport. Clipzing speaks Streamable HTTP: in your framework choose "Streamable HTTP" (often called "http" or "streamable-http") instead of "SSE", and keep the same URL.

403 "forbidden_origin" when my agent calls from a web page

Keys work from servers by default. If your agent calls Clipzing from inside a browser, add that page's origin, such as https://agent.example.com, to the key: Billing, API keys, Restrict.

401 "restricted to specific IP addresses"

The key is locked to certain IP addresses and the request came from another one. The message names the address it saw. Add it to the key under Billing, API keys, Restrict, or remove the lock.

It can read but refuses to change anything

The connection was approved read-only. Restart your agent to pair again and tick the extra permissions, or check what your plan allows under Billing, API keys.

Still stuck? Email info@clipzing.com.

Manage your connectionsBack to Clipzing