Skip to content

Connect c6s over MCP

c6s mcp is a local stdio server. The MCP client launches the process and owns its lifetime; c6s does not install a daemon or open a network listener.

Use the absolute path to the executable:

json
{
  "mcpServers": {
    "c6s": {
      "command": "/Users/you/.local/bin/c6s",
      "args": ["mcp"]
    }
  }
}

Replace /Users/you with your actual home directory. Do not place tokens, recovery material, or secret values in the MCP configuration.

Current tools

The initial surface can report non-sensitive capabilities, verify the public synthetic approval fixture, and inspect its canonical digest data. It cannot read a vault, reveal secrets, approve a request, consume a grant, or execute an action.

Process contract

  • JSON-RPC frames use standard output.
  • Diagnostics use standard error.
  • Closing standard input stops the server.
  • MCP calls pass through the same validation and redaction boundary as CLI commands.

Private beta documentation. Authentication never unlocks the vault.