vscode-mcp-manager
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| vscode_generate_mcp_configA | Generates ready-to-use, verified MCP client configuration files for Claude Desktop, Cursor IDE, Roo Code / Cline, and OpenAI Responses API. Automatically maps local stdio commands (npx/uvx) and remote Cloudflare SSE edge streams. Use when configuring an AI agent or IDE to communicate with SEOSiri servers. Do not use for non-MCP IDE settings. |
| vscode_audit_extension_manifestA | Audits VS Code extension package.json manifests against Microsoft Marketplace and security standards. Checks for required engines, activationEvents, publisher IDs, category validity, and unsafe dependencies. Use before packaging .vsix extension binaries. |
| vscode_sync_workspace_settingsA | Generates standardized enterprise workspace settings (.vscode/settings.json) and recommended extensions (.vscode/extensions.json) for TypeScript, ESLint, Tailwind CSS, and MCP development. Use to establish consistent team settings across VS Code and Cursor. |
| vscode_inspect_live_gatewaysA | Queries real-time operational status, sub-millisecond response latency, and supported protocol transports across all 13 official SEOSiri Cloudflare edge gateways (*.seosiri.com). Use to verify network connectivity before invoking remote MCP tools. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool targets a distinct artifact or action: generating MCP client configs, auditing extension manifests, syncing workspace settings, and inspecting live gateways. Even the two config-producing tools are clearly separated by output type and intended usage.
All tool names follow the same vscode_<verb>_<object> pattern, using specific verbs and clear nouns. There are no mixed conventions or vague actions.
Four tools form a compact, purposeful set well within the ideal range. Each tool covers a separate facet of the VS Code/MCP configuration workflow without redundancy.
The set covers configuration generation, workspace standardization, extension validation, and gateway health verification, which supports a solid setup workflow. Minor gaps exist—such as no explicit existing-config validation or server removal—but these do not create dead ends for the apparent purpose.