Before you install — the 60-second version of how your data is handled
Content you save is stored in plaintext on a single hosted server operated by Fo0l1sh. The operator has technical access for system maintenance and your own support requests — not for browsing, training AI, embeddings, or sharing with third parties. Never.
When you use the Claude.ai chat connector, the bodies of MCP tool calls also pass through Anthropic's backend on the way to MinSets — true of every claude.ai MCP server, not specific to MinSets. Claude Code & Desktop connect directly from your machine; nothing routes through Anthropic.
Full picture: Privacy Policy · Terms. If those terms don't work for what you want to save, V1 isn't the right tool yet — see the privacy policy for the end-to-end-encryption roadmap.
After sign-in you land on your settings page with a one-time token. Copy it immediately — it's shown once. If you lose it, regenerate (the old one stops working).
~/.claude/mcp_servers.json
(Windows: %USERPROFILE%\.claude\mcp_servers.json):{
"mcpServers": {
"minsets": {
"url": "https://api.minsets.com/mcp",
"headers": {
"Authorization": "Bearer YOUR_TOKEN_HERE"
}
}
}
}
YOUR_TOKEN_HERE with the token from Step 1.
If the file already has other MCP servers, add the "minsets"
block alongside them — don't replace the whole file. Restart Claude Code
after saving.https://api.minsets.com/mcphttps://api.minsets.com/authorize. If you're not already signed in to MinSets, you'll bounce through GitHub login first.In Claude Code:
Save "my first minset works" as test/first using minsets
Then in a new Claude Code chat (or in Claude.ai if you wired Step 3):
Recall what I saved as test/first using minsets
You should get back the exact string you saved.
Your token is wrong, expired, or was regenerated. Get a fresh one at
/settings and update mcp_servers.json.
Restart the client after.
The Authorization header isn't reaching the server. Check
the headers block in your config matches the snippet exactly,
including Bearer + a space before the token. This error does
NOT apply to claude.ai — claude.ai uses OAuth, not header pasting.
claude.ai cached "no-auth-required" from before OAuth was enabled on your server. Fix: Disconnect the minsets connector in claude.ai, then re-add it with the same URL. claude.ai will re-probe and discover OAuth, and an Authenticate button will appear.
Some versions of claude.ai trigger the OAuth flow only when Claude actually tries to call a tool. Just ask Claude to use a minsets tool in a chat — the popup will appear at that point.
Claude Code: restart it fully (quit, not just close). Confirm the JSON
is valid (no trailing commas). The server name (minsets) is
what you reference in prompts. Claude.ai: refresh the page after the
connector is added + authenticated.
Both surfaces must be authenticated to the same MinSets account (same GitHub login). Different accounts = different isolated workspaces.