How do I audit VS Code’s Montage servers schema without replacing other MCP entries?
A valid JSON object can still use the wrong client’s configuration shape. Review VS Code’s servers structure in place, preserving existing definitions and separating schema correctness from the editor’s trust, authentication and conversation tool-selection decisions. Use the VS Code servers shape as a schema check, not a reason to replace the whole file. Parsing success, editor trust, conversation selection and account-scoped execution remain different acceptance milestones.
Help me audit VS Code’s Montage servers schema without replacing other MCP entries. Inspect .vscode/mcp.json or the server location managed by the current editor controls. After supported trust and auth decisions, request a single signals_status call where the tools are enabled. No writes.Locate the active MCP document
Inspect .vscode/mcp.json or the server location managed by the current editor controls. Do not assume a file copied from Cursor is meaningful merely because it contains an MCP URL. The reviewed document should distinguish a workspace definition from a copied example that the running editor never loaded at all.
Check the enclosing object
Confirm that the Montage entry belongs under servers and uses type http with the hosted URL. A top-level mcpServers object from another client is not this documented VS Code shape. Compare the full servers entry against the official VS Code form; a parser accepting unknown JSON keys does not establish product support.
Preserve neighboring registrations
Compare the complete file before any scoped correction and retain unrelated server entries. Do not replace team configuration with the minimal Montage example just because that example is shorter. A single-entry documentation sample is an illustration of shape, not an instruction to discard a team’s other useful MCP registrations.
Inspect editor loading separately
Use VS Code’s server controls to determine whether the active editor recognizes the entry. JSON parsing, server trust and tool availability each provide different evidence and should not be collapsed into one success claim. The editor’s trust prompt remains an intentional decision boundary; do not accept unknown server definitions merely to obtain a green indicator.
Validate in the intended chat
After supported trust and auth decisions, request a single signals_status call where the tools are enabled. Record whether the corrected schema reached real workspace execution or exposed a separate authorization blocker. The proof note should distinguish corrected schema from completed account authorization and from a status read in the chosen conversation.
Keep the boundaries clear.
- A single-entry documentation sample is an illustration of shape, not an instruction to discard a team’s other useful MCP registrations.
- The proof note should distinguish corrected schema from completed account authorization and from a status read in the chosen conversation.
Start with a read-only check: ask your agent to report actual source coverage before collecting records or exporting an audience.
Primary references
Documentation reviewed 2026-11-15. Product capabilities, client availability and plans can change. Third-party marks identify their products, not an affiliation.