Clipps for AI assistants

Your library,
in your AI.

Connect Clipps to Claude, Codex, Cursor, Gemini, OpenCode, OpenClaw, and any other AI assistant that speaks MCP. One install lets you search, read, and save into your library without leaving the chat.

Get started View on npm
One command

Install and pair

Run it once on any computer. Your browser opens, you sign in, and the token gets stored in ~/.config/clipps/auth.json for every AI client on the machine to share.

$npx clippsapp clipps login

Need to install globally instead? npm i -g clippsapp

Setup

Wire it into your AI client

Find your client below, copy the snippet, then restart the client.

Claude Desktop

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "clipps": {
      "command": "npx",
      "args": ["clippsapp", "clipps-mcp"]
    }
  }
}

Claude Code

terminal, anywhere

# From any project directory:
claude mcp add clipps -- \
  npx clippsapp clipps-mcp

Codex CLI

terminal, anywhere

# Easiest:
codex mcp add clipps -- \
  npx clippsapp clipps-mcp

# Or edit ~/.codex/config.toml directly:
[mcp_servers.clipps]
command = "npx"
args = ["clippsapp", "clipps-mcp"]

Gemini CLI

terminal, anywhere

# Add globally (across all projects):
gemini mcp add -s user clipps \
  npx clippsapp clipps-mcp

# Or just for the current project:
gemini mcp add clipps \
  npx clippsapp clipps-mcp

OpenCode

opencode.json (project) or ~/.config/opencode/opencode.json (global)

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "clipps": {
      "type": "local",
      "command": ["npx", "clippsapp", "clipps-mcp"],
      "enabled": true
    }
  }
}

OpenClaw 🦞

terminal, anywhere

# Easiest:
openclaw mcp set clipps \
  '{"command":"npx","args":["clippsapp","clipps-mcp"]}'

# Or edit OpenClaw's config under mcp.servers:
{
  "mcp": {
    "servers": {
      "clipps": {
        "command": "npx",
        "args": ["clippsapp", "clipps-mcp"]
      }
    }
  }
}

Cursor

~/.cursor/mcp.json

{
  "mcpServers": {
    "clipps": {
      "command": "npx",
      "args": ["clippsapp", "clipps-mcp"]
    }
  }
}

Windsurf

~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "clipps": {
      "command": "npx",
      "args": ["clippsapp", "clipps-mcp"]
    }
  }
}

ChatGPT (Custom GPT Action)

app.clippsapp.com → Settings → Developer

# 1. Generate an API key in Clipps
# 2. Create a Custom GPT
# 3. Paste the OpenAPI schema (ships with the npm package
#    at packages/clipps-cli/openapi.yaml)
# 4. Auth: API Key, header X-API-Key

Anything else with stdio MCP

command + args

# Command:
npx
# Args:
clippsapp clipps-mcp
# Env: none required after `clipps login`
Capabilities

What your AI can do

Seven tools cover search, read, save, and conversation against any Brain in your library.

clipps_search

Find saved videos, articles, and notes by topic, keyword, or creator.

clipps_read

Pull a single item's full transcript, AI summary, and structured metadata.

clipps_recent

List the last N saves. Useful for "what did I save this week?"

clipps_save

Save a URL into your library from inside the chat.

clipps_brain_chat

Ask a question against a specific Brain. Returns an answer with citations.

clipps_brain_export

Export a whole Brain as markdown, JSON, or a system prompt.

clipps_list_export

Export a list with all its videos for grounded analysis.

Example prompts

Talk to your library

Once it's wired up, just ask. Your AI picks the right tools as needed.

What recipes did I save with chickpeas in them?
Pull every video about Claude Code from my AI Tools brain and summarize the techniques.
Save this YouTube link into Clipps: https://youtu.be/...
Compare what I've saved about Kubernetes vs. Docker. Where do they overlap, where do they diverge?
What sneaker drops did I save in the last 30 days, ranked by my interest signal?
Generate a system prompt from my Cooking brain that I can paste into a different model.
FAQ

Questions, answered

Where does the API key live?

Locally on your machine at ~/.config/clipps/auth.json (mode 0600). Override with CLIPPS_CONFIG_DIR if you want a different location. The MCP runs entirely on your machine and only talks to Clipps's API to fetch your data.

Does my AI assistant see my data directly?

Yes, that's the point. The MCP exposes tools like clipps_search to your AI. When the AI calls one, the request goes to Clipps's API, which returns your data, which the AI uses to answer. Nothing is forwarded to a third party.

Do I need a paid Clipps account?

No. The MCP works with any Clipps account. Free tier limits apply where they apply in the app.

How do I disconnect or rotate the key?

Run clipps logout to delete the local key. To revoke server-side, open app.clippsapp.com → Settings → Developer and revoke the key. Then run clipps login to issue a new one.

Multiple accounts?

Set CLIPPS_CONFIG_DIR to a different folder per account. Switch by changing the env var in your AI client's MCP config.

Mobile?

The MCP runs on desktop (where AI clients run). On iOS and Android, use the Clipps mobile apps directly. The Clipps Obsidian plugin mirrors your library as markdown if you want it inside a vault.

What if the install or pairing fails?

Run clipps login --manual and paste an API key from the Clipps Settings → Developer page. Same outcome, no browser dance.