Set up the MCP server

Snoze runs a hosted Model Context Protocol server, so AI clients can search and act on your workspace directly — no local bridge to install or keep updated. It speaks Streamable HTTP at https://api.snoze.dev/mcp.

Connecting takes one step: add the server to your client, and when the client first talks to Snoze your browser opens to sign in and approve access. The agent then works as you — it can see and change exactly what your workspace role allows, nothing more. No API key required.

Claude Code

Add the server with the official command, then sign in:

claude mcp add --transport http snoze https://api.snoze.dev/mcp

Run /mcp inside Claude Code and pick snoze to sign in through your browser. The default command enables the server for you in the current project only. Two other scopes are worth knowing:

# For you, in every project on this machine
claude mcp add --transport http --scope user snoze https://api.snoze.dev/mcp

# For everyone on this project — writes a shared .mcp.json you commit
claude mcp add --transport http --scope project snoze https://api.snoze.dev/mcp

Claude (web and desktop)

In Claude, open Settings → Connectors → Add custom connector and paste https://api.snoze.dev/mcp. Claude walks you through the sign-in.

Codex

codex mcp add snoze --url https://api.snoze.dev/mcp
codex mcp login snoze

The second command opens your browser to sign in.

Cursor

On the web version of this page, use the Add to Cursor button — Cursor opens, installs the server, and shows a Login prompt that completes the sign-in. Or add it by hand in Cursor Settings → MCP with the JSON below.

VS Code

code --add-mcp '{"name":"snoze","type":"http","url":"https://api.snoze.dev/mcp"}'

VS Code prompts you to sign in the first time Copilot uses the server. The web version of this page also has a one-click Add to VS Code button.

Any other MCP client

Point the client at the server URL — every MCP client that supports remote servers understands this shape:

{
  "mcpServers": {
    "snoze": { "type": "http", "url": "https://api.snoze.dev/mcp" }
  }
}

Running headless? Use an API key

Scripts, CI jobs, and servers can’t open a browser to sign in. For those, create a workspace API key at Settings → API keys and send it as a bearer token instead — no sign-in step:

{
  "mcpServers": {
    "snoze": {
      "type": "http",
      "url": "https://api.snoze.dev/mcp",
      "headers": { "Authorization": "Bearer snoze_sk_YOUR_KEY" }
    }
  }
}

An API key is also the right choice when you want the agent to have less access than you: a read-only key lets an assistant search and summarize with no risk of it changing your data — see API keys and scopes.

What the agent can do

Once connected, the client discovers Snoze’s tools automatically. They map to the same typed operations the app uses:

• Search — full-text and semantic search across every item you can read
• Read — fetch pages, database schemas and records, dashboards, files
• Mutate — create and update items, edit page content, write records
• Actions — list and run the workspace’s automations

Workspace items are also exposed as MCP resources under stable snoze:// URIs, so a client can browse and attach them.

Safety

Signed in with your account, the server can never do more than your workspace role allows; with an API key, never more than the key’s scopes. The workspace comes from your authenticated identity, never from anything the model says. High-stakes operations respect the same approval gates as the in-app assistant.

Building your own integration?

The full protocol surface, tool reference, and API details live in the developer docs.