feat: Add Sourcery MCP server configuration

[flatfinderfintech-lab]

• Create .claude/mcp.json with Sourcery MCP server setup
• Configure Sourcery to run via npx @sourcery/mcp-server
• Add SOURCERY_API_KEY environment variable to .env.example
• Enable code quality analysis through Model Context Protocol

Summary by Sourcery

Configure Claude MCP integration with the Sourcery MCP server for code quality analysis.

New Features:

• Introduce .claude/mcp.json to register and configure the Sourcery MCP server via npx @sourcery/mcp-server.
• Document the SOURCERY_API_KEY environment variable in .env.example for authenticating Sourcery requests.

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

.claude/mcp.json is introduced to configure the Sourcery MCP server, and .env.example is updated to document the SOURCERY_API_KEY environment variable needed for Sourcery-based code quality analysis.

File-Level Changes

Change	Details	Files
Configure Claude MCP to use the Sourcery MCP server for code quality analysis.	Add a new MCP configuration file defining the Sourcery MCP server endpoint and invocation via npx @sourcery/mcp-server Wire Sourcery into the Model Context Protocol configuration so it can be used during development for code quality insights	.claude/mcp.json
Document Sourcery API requirements in environment configuration.	Introduce SOURCERY_API_KEY as a required/optional variable for Sourcery integration Update example environment file so developers know to provide their Sourcery API key	.env.example

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey there - I've reviewed your changes - here's some feedback:

• Ensure the SOURCERY_API_KEY in .env.example has a clear placeholder value (e.g., your-sourcery-api-key) rather than anything that could be mistaken for a real or default key.
• In .claude/mcp.json, consider pinning the @sourcery/mcp-server version in the npx command to avoid unexpected behavior when new major versions are released.
• If .claude/mcp.json includes project-specific paths or settings, double-check they work across typical local dev environments (e.g., relative paths, no machine-specific absolute paths).

Prompt for AI Agents

Please address the comments from this code review:

## Overall Comments
- Ensure the `SOURCERY_API_KEY` in `.env.example` has a clear placeholder value (e.g., `your-sourcery-api-key`) rather than anything that could be mistaken for a real or default key.
- In `.claude/mcp.json`, consider pinning the `@sourcery/mcp-server` version in the `npx` command to avoid unexpected behavior when new major versions are released.
- If `.claude/mcp.json` includes project-specific paths or settings, double-check they work across typical local dev environments (e.g., relative paths, no machine-specific absolute paths).

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[fucacctz-create]

ok