Ruledebt.
Workspace/Settings

Settings

Connect your own source accounts. Tokens stay server-side in this RuleDebt instance.

Bring your own keys

Your keys are stored server-side in Supabase Postgres (ruledebt_secrets). Local next dev without Supabase credentials falls back to the RuleDebt data directory. They are never returned in full.

GitHub not configured
Slack not configured

GitHub: create a classic personal access token with the repo scope.

Slack: your bot needs channels:history, channels:read, and groups:history for private channels when needed.

Scan connected sources

Scans use the saved keys above. Matching source quotes are added to Inbox.

Scan GitHub repo
Scan Slack channel

MCP connection

Use the Settings shared store keys, or provide tokens directly as environment variables in your MCP client configuration.

Cursor configuration
{
  "mcpServers": {
    "ruledebt": {
      "command": "node",
      "args": ["/workspace/ruledebt/mcp/dist/index.js"],
      "env": { "RULEDEBT_DATA_DIR": "/workspace/ruledebt/.ruledebt-data" }
    }
  }
}

With this data directory, the MCP server reads the same saved secrets. Alternatively set GITHUB_TOKEN and SLACK_BOT_TOKEN in mcp.json.