Skippy MCP

Use Skippy from Claude, Cursor, Kiro, VS Code, or any other MCP client. Your notes, workspace, skills, agents and research live in Skippy, so what you save in one tool is there in the next.

This is a private beta. Your Skippy account has to be added to it first. If you haven't been invited, ask the Skippy team.

Setup

You need two things: a Skippy account in the beta, and uv installed. Setup takes about five minutes.

1. Create an API key

In Skippy, open Settings > API Keys and click Create new key. Copy it straight away: Skippy shows it once.

2. Save the key

uvx skippy-mcp auth

Paste the key when it asks. It saves the key to ~/.skippy/token, readable only by you, then checks it with Skippy. You should see ✓ Key works.

3. Add Skippy to your client

Every client runs the same command, uvx skippy-mcp. Only where you put it changes.

Claude Code

claude mcp add skippy -- uvx skippy-mcp

Claude Desktop, Cursor, Kiro and Windsurf take this block:

{
  "mcpServers": {
    "skippy": {
      "command": "uvx",
      "args": ["skippy-mcp"]
    }
  }
}

VS Code uses a slightly different shape, in .vscode/mcp.json:

{
  "servers": {
    "skippy": {
      "type": "stdio",
      "command": "uvx",
      "args": ["skippy-mcp"]
    }
  }
}

Restart the client. Ask it to run skippy_status, and you should see your name and plan.

What you can do

Deep research draws on the same monthly research credits as the Skippy app.

Four tools run on your own machine instead: read_local_file, list_local_files, git_status and git_diff. They can only see the folder your client started the server in. What they read goes to your AI client, the same as any file you open in it, and none of it goes to Skippy.

skippy_publish_site also reads from your machine, and it uploads what it reads, so it is held to the same folder. If you meant to publish something elsewhere, start the server in that folder. When a site.config.js sits beside the folder you publish, it is run with node to read its settings, the same as your build tool would.

Troubleshooting

"The Skippy MCP server is in private beta." Your key works, but your account isn't in the beta yet. Ask the Skippy team to add you.

"This key is invalid or disabled." The key was revoked, disabled, or mistyped. Create a new one under Settings > API Keys and run uvx skippy-mcp auth again.

Your client says it can't find uvx. Desktop apps often start with a shorter PATH than your terminal. Run which uvx in a terminal and put that full path in "command" instead of uvx.

To check your setup at any time, run uvx skippy-mcp verify.

Folder-based scoping (optional)

If you keep work for different clients or projects in different folders, Skippy can file workspace writes and journal entries under that name automatically. Create ~/.skippy/client_map.json:

{ "/work/northwind": "northwind", "/work/contoso": "contoso" }

When the server starts in a folder whose path contains one of those fragments, notes.md is saved as clients/northwind/notes.md. The SKIPPY_CLIENT_MAP environment variable takes the same JSON and overrides the file. With neither, nothing is scoped.

Feedback

Something broken or missing? Ask your client to run skippy_submit_feedback. It goes straight to the team building Skippy.