Claude Code

Claude Code is Anthropic’s terminal-native coding agent. It speaks Model Context Protocol natively, which means Scrubby plugs in cleanly: your agent gets architectural awareness, convention knowledge, and co-change detection without any custom glue.

Setup

1. Add the MCP server

Add this to your project’s .mcp.json file (create it in the repo root if it doesn’t exist):

{
  "mcpServers": {
    "scrubby": {
      "type": "http",
      "url": "https://mcp.scrubby.ai/mcp"
    }
  }
}

2. Authenticate

The first time Claude Code connects to Scrubby it opens a browser window for GitHub OAuth. Sign in with the same GitHub account you used to create your Scrubby account.

If your session expires, run /mcp in Claude Code to reconnect.

3. Start using Scrubby

That’s it. Scrubby’s MCP server publishes its usage instructions via the protocol, so Claude will consult Scrubby before editing files, before answering architecture questions, and before reviewing changes. No additional configuration needed.

Available tools

Once connected, Claude Code has access to the full MCP Tools Reference:

Tool	Used for
scrubby_index	Index a repository for the first time, or re-index after major changes
scrubby_review	Get domain, conventions, connected files, and git history for a specific file
scrubby_review_changeset	Check a set of changed files for missing co-changes, consistency issues, and domain crossings
scrubby_get_domains	List all architectural domains discovered in the repository
scrubby_get_segments	List code segments with their conventions and file summaries
scrubby_get_network	Get the domain connection graph showing how areas of the codebase relate
scrubby_get_findings	Retrieve commit and domain activity for a repository
scrubby_report_findings	Report issues found during review so Scrubby’s connection weights improve

How it works in practice

With Scrubby connected, Claude Code will automatically:

• Before editing a file. Check what domain it belongs to, what conventions apply, and what other files usually change with it.
• Before answering architecture questions. Query the domain graph to give accurate answers about how your codebase is structured.
• Before committing. Review the changeset for forgotten files, inconsistencies, and convention violations.

Troubleshooting

For the most common issues see Editor Not Connecting. Quick fixes:

• Session expired — run /mcp in Claude Code to reconnect.
• Repository not indexed — ask Claude to run scrubby_index with your repo name in owner/repo format.
• Tools not appearing — check that .mcp.json is in your project root and the URL matches the snippet above. Restart Claude Code after creating the file.