Orchestrating Model Context Protocol in IDEs: The SEOSiri VS Code MCP Manager (v1.0.2)

Question

If you are running multi-server Model Context Protocol (MCP) setups across Cursor, Claude Desktop, and VS Code, you already know the friction: syntax errors in mcp.json, mismatched npx vs uvx arguments, un-sandboxed extension permissions, and zero visibility into remote edge health.

To solve this, we engineered and open-sourced seosiri-vscode-mcp-manager (now live on the Visual Studio Marketplace):

🛠️ What it does under the hood:

• vscode_generate_mcp_config: Auto-compiles validated .vscode/mcp.json and claude_desktop_config.json snippets for zero-setup execution.
• vscode_audit_extension_manifest: Audits package.json extension manifests for activation triggers and permission leaks.
• vscode_sync_workspace_settings: Synchronizes linters, TypeScript configs, and approved MCP tool lists across development teams.
• vscode_inspect_live_gateways: Real-time sub-10ms health and latency checks across Cloudflare Workers edge nodes (vscode.seosiri.com).

📦 Lightweight Architecture:

Bundled with esbuild down to 73 KB (single-file CJS runtime, zero bloated node_modules in the VSIX bundle).

• VS Code Marketplace: https://marketplace.visualstudio.com/items?itemName=SEOSiri.seosiri-vscode-mcp-manager
• Architecture Guide: https://www.seosiri.com/2026/08/vscode-mcp-manager.html
• Developer Portal & Topology: https://developers.seosiri.com/

Would love feedback from engineers building autonomous agents and custom MCP tools!