Why is my MCP server missing from the VS Code tool list?

The most common causes are a config entry in the wrong scope (user vs workspace settings), a workspace not trusted in Restricted Mode, or a server that failed to start. Check the Output panel for the specific error.

Where does VS Code store MCP server configuration?

MCP servers can be configured in user settings (global, applies to every workspace) or workspace settings (the .vscode/settings.json file in the project folder). The correct location depends on whether the server should be available everywhere or only in one project.

What does "Restricted Mode" mean for MCP servers?

Restricted Mode limits features that can execute code. An MCP server configured in workspace settings may not start in Restricted Mode. Trust the workspace from the status bar if you own the code, or move the server config to user settings.

How do I see why an MCP server failed to start in VS Code?

Open View > Output and select the MCP or Copilot Chat channel. VS Code logs server startup attempts and errors there. The log usually shows the exact command it ran and the exit error.

After I fix the config, do I need to restart VS Code?

In most cases you can reload the window (Command Palette > "Developer: Reload Window") rather than closing and reopening VS Code. After a reload, check the Output panel to confirm the server started.

MCP Server Not Showing in VS Code: Checks That Find the Cause

When an MCP server does not appear in VS Code, the problem is usually in configuration scope, workspace trust, or a startup failure the UI hides. These checks find the cause and show you where to save the fix.

September 8, 2026Updated October 21, 20264 min read

When an MCP server does not show up in VS Code, the cause is almost always one of four things: the config entry is in the wrong scope, the workspace is not trusted, the server process failed to start, or a version of the extension does not support the server type you configured.

Working through these checks in order saves time. Once you find and fix the root cause, save the verified setup in fenbs so the next time you or a teammate configures this server, the working steps are already recorded.

Check 1: confirm the config is in the right scope

VS Code separates MCP server configuration into user settings (global, available in every workspace) and workspace settings (local to the current folder). A server added to workspace settings does not appear in other workspaces. A server added to user settings does not appear if the feature requires a workspace.

Open the Command Palette and run "Preferences: Open User Settings (JSON)" to see global config, or "Preferences: Open Workspace Settings (JSON)" for the current folder. Confirm the mcp or github.copilot.chat.mcp.servers block is in the file you expect.

If the server should be available everywhere, add it to user settings. If it is project-specific, add it to the .vscode/settings.json in the project folder.

Check 2: workspace trust

VS Code restricts certain features in workspaces that are not trusted. If a folder is open in Restricted Mode, MCP servers configured in workspace settings may not load. Look for a "Restricted Mode" badge in the bottom-left status bar.

Click the badge and trust the workspace if you own the code. For a workspace you do not control, consider adding the server to user settings instead, where workspace trust does not apply.

Check 3: read the startup error

VS Code launches MCP servers as child processes. If the process exits immediately, the server never appears in the UI. The error is usually in the Output panel.

Open View > Output and select the MCP or Copilot Chat channel from the dropdown. Look for the server's startup attempt and the error that follows. Common causes: the command is not found (wrong path or missing npx), a required argument is missing, or the server expects an environment variable that is not set.

Command not found: add the full path or confirm the runtime (node, python, npx) is on the PATH.
Argument missing: compare your config against the server's documentation. A required --port or --token flag that is missing causes an immediate exit.
Environment variable missing: some servers read API keys from environment variables. Set them in the env block of the server config entry.

How fenbs helps

Save the working config so the team does not repeat the search

When you find the setting that fixed the problem, record it as a lesson or a context note in fenbs. Add the working config snippet as a code block in the note. The next teammate who sets up this server will find the answer before they start debugging, not after an hour of checking. Create a free account and start with a single lesson.

Create a free account

Free for one person · No credit card · Works with Claude, ChatGPT, Cursor and more

Check 4: confirm extension version support

MCP support in VS Code has evolved through extension updates. An older version of GitHub Copilot or another extension may not recognize all server types or transport options.

Open the Extensions panel and check the installed version of any extension that provides MCP support. Compare it against the extension's changelog or release notes to confirm whether MCP server discovery was available at that version.

Check 5: validate the JSON

A single syntax error in a JSON config file silently prevents the entire block from loading. VS Code may not surface this clearly in the UI.

Open the settings file, look for the red squiggle that VS Code shows on JSON errors, and fix any syntax problems. Common issues: trailing commas after the last item in an array or object, unescaped backslashes in Windows paths, and mismatched brackets.

For general connection issues beyond VS Code, the companion article on MCP server not connecting covers transport and authentication failures that apply to any client.

After fixing the issue, reload the window with Developer: Reload Window from the Command Palette rather than closing VS Code entirely. Watch the Output panel after the reload. The server should log its startup and list its available tools. If it does, run a test call in Copilot Chat or whichever extension uses MCP to confirm the end-to-end connection is working before you rely on it for real work.

How to do this with fenbs

If you are adding the fenbs MCP server to VS Code specifically, these steps apply.

Create a free account and go to Integrations to find the VS Code setup guide.
Follow the guide to add the fenbs MCP server entry to your VS Code settings at the right scope (user or workspace).
Complete the OAuth sign-in from the browser. VS Code's extension will prompt you when it discovers the server and needs a token.
After sign-in, open the Output panel and check the MCP channel to confirm the server started and listed its tools.
Record the working setup as a context note or lesson in fenbs, including the config location and any environment-specific steps, so the next setup is faster.

fenbs connects over OAuth: there is no token to paste into config files. If the sign-in step is missing or was interrupted, disconnect and reconnect from Integrations to restart the flow.