moai-cc-mcp-plugins-settings-2

Configure MCP servers by setting OAuth credentials and scoped permissions in settings.json. Define least-privilege access for each server (GitHub, Filesystem, SQLite, Brave Search), store secrets in environment variables, and validate structure via CLI commands to enforce security boundaries.

Set up MCP plugins by configuring server definitions in settings.json with explicit path whitelisting, OAuth tokens, and scoped permissions. Use CLI commands to validate health checks and marketplace integration, enabling secure tool and API access without exposing unnecessary credentials.

Yes, MCP servers support GitHub, Filesystem, SQLite, and Brave Search integration simultaneously. Configure each with separate OAuth scopes and permission restrictions in settings.json, then use CLI validation to ensure all servers pass health checks before deployment.

Restrict filesystem access by defining explicit path whitelists in the Filesystem MCP server configuration within settings.json. Enforce least-privilege scopes and validate restrictions through CLI commands to prevent unauthorized directory traversal.

Store OAuth secrets in environment variables, never in settings.json. Apply least-privilege scopes for each MCP server, whitelist specific paths for filesystem access, and run CLI health checks to validate configuration before enabling external tool integration.

Yes, use CLI commands to validate settings.json structure and run health checks on configured MCP servers. Validation ensures OAuth credentials are properly scoped, paths are whitelisted correctly, and all servers are ready for secure integration with Claude Code.