feat: disable sentry and socket MCPs by default

[marcusquinn]

Remote MCPs requiring auth - disable until configured. Only osgrep remains eager.

Summary by CodeRabbit

• Chores
  • Optimized application startup by refining module loading and initialization strategy.
  • Reconfigured priority modules for eager initialization while expanding the deferred loading list for improved resource management.
  • Added runtime policy enforcement mechanism to automatically control module activation based on system configuration priorities during startup.

[gemini-code-assist]

Summary of Changes

Hello @marcusquinn, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request refines the default loading strategy for Micro-Capability Providers (MCPs) by moving remote, authentication-dependent MCPs ('sentry' and 'socket') from an eager-loaded state to a lazy-loaded one. This adjustment aims to enhance application startup efficiency and reduce initial resource consumption by only initializing these components when they are actively needed.

Highlights

• MCP Loading Strategy: The 'sentry' and 'socket' Micro-Capability Providers (MCPs) have been reconfigured from eager-loaded to lazy-loaded. This means they will no longer be initialized at launch by default.
• Performance Optimization: This change is expected to save approximately 7K+ tokens during session startup by deferring the loading of these remote MCPs until they are explicitly required.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

Refactors MCP loading strategy by moving 'sentry' and 'socket' from eager to lazy loading, retaining 'osgrep' as exclusively eager. A new policy enforcement loop validates MCP classifications and configures runtime loading behavior.

Changes

Cohort / File(s)	Summary
MCP Loading Policy Configuration .agent/scripts/generate-opencode-agents.sh	Reorganized EAGER_MCPS (now only 'osgrep') and expanded LAZY_MCPS to include 'sentry' and 'socket'. Added policy application loop to enforce enabled/disabled states and warn on uncategorized MCPs.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Poem

🚀 MCPs take flight with wisdom's hand
Eager 'osgrep' leads the grand parade,
While 'sentry' & 'socket' join the lazy brigade,
Runtime policies keep all things planned,
Loading strategies now perfectly made! 🎯

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch feat/disable-sentry-socket

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[gemini-code-assist]

Code Review

This pull request correctly disables the sentry and socket MCPs by default by moving them from the eager-loaded list to the lazy-loaded list. This change aligns with the stated goal of disabling remote MCPs that require authentication until they are configured. I have one suggestion to improve the maintainability of the code.

[gemini-code-assist]

For better readability and easier maintenance, consider sorting the items in the LAZY_MCPS set alphabetically and placing each item on its own line. This makes it much easier to find specific MCPs and simplifies future modifications.

LAZY_MCPS = {
    'ahrefs',
    'amazon-order-history',
    'augment-context-engine',
    'chrome-devtools',
    'claude-code-mcp',
    'context7',
    'dataforseo',
    'gh_grep',
    'google-analytics-mcp',
    'gsc',
    'localwp',
    'macos-automator',
    'MCP_DOCKER',
    'outscraper',
    'playwriter',
    'quickfile',
    'sentry',
    'shadcn',
    'socket',
}

[augmentcode]

🤖 Augment PR Summary

Summary: Moves the auth-required remote MCPs (sentry, socket) out of eager startup so only osgrep loads at launch by default.
Why: Prevents remote MCPs that require authentication from starting automatically until a user explicitly opts into using/configuring them.

_{🤖 Was this summary useful? React with 👍 or 👎}

[augmentcode]

Review completed. 1 suggestions posted.

Comment augment review to trigger a new review at any time.

[augmentcode]

Adding sentry/socket to LAZY_MCPS means this script will keep forcing those MCPs to enabled: false on every regeneration if they exist in opencode.json. Is it intentional that they should always remain lazy-loaded (never eager), even after a user finishes auth configuration?

_{🤖 Was this useful? React with 👍 or 👎, or 🚀 if it prevented an incident/outage.}