SEED / Clearance
developer preview
Get started · 2 of 2

Connect your assistant

SEED Clearance works with the assistant you already use. It adds a local bridge so the assistant can ask for permission before using a controlled tool.

MCP is the connection method. The product is the permission layer: identity, permission slip, budget, signed log, proof, and revoke.

Pick your assistant

Claude Desktop
Adds SEED to Claude Desktop as a local tool server. Claude asks SEED before using controlled actions.
seed clearance connect --profile claude-desktop
config · Claude Desktop
// ~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "seed": {
      "command": "seed",
      "args": ["clearance", "bridge", "--mcp"]
    }
  }
}
Cursor
Connects your editor assistant to SEED so code-agent actions can be permissioned and logged.
Continue
Connects Continue to the local SEED bridge. Continue keeps its UX; SEED handles permission checks.
Generic MCP
Use this for any assistant that can launch an MCP server over stdio.

What connect does

  • Gives the assistant a name under your local SEED identity.
  • Creates a permission slip for the actions you allow.
  • Updates the assistant config so it can launch seed clearance bridge.
  • Writes a signed connect receipt to your local log.

Local bridge

sh
seed clearance bridge --mcp     # stdio, for MCP hosts
seed clearance bridge --http    # localhost-only HTTP, for custom integrations

The bridge runs on your machine. MCP uses stdio. HTTP binds to 127.0.0.1 only and requires a per-assistant token created during connect.