Free tools Windows power users keep installed
One-click scans. No signup required.
To connect an MCP server in VS Code, install one from the MCP gallery or add its configuration, choose the transport and environment it actually supports, approve the server if VS Code asks you to trust it, then check its status and tools in Chat. Local servers commonly use stdio; remote servers can use HTTP or legacy SSE. The right setup depends on where the server must run and whether you want it available in one workspace or across several.
Choose where the server should run and who should be able to use it
Before configuring a server, decide its scope and execution location. A workspace configuration travels with a project; a user-profile configuration is intended for your VS Code profile across workspaces. Remote and Dev Container configurations run in their respective environments, not necessarily on your computer. Put the configuration where the server process or connection needs to exist.
- One project: use the workspace configuration, usually
.vscode/mcp.json. - Across workspaces: run MCP: Open User Configuration from the Command Palette.
- Remote environment: run MCP: Open Remote User Configuration while connected to that environment.
- Dev Container: define the server under
customizations.vscode.mcpindevcontainer.json. VS Code writes it into the remote MCP configuration when the container is created.
Profiles can have their own MCP configuration. In a remote workspace, check where the server is configured: a local user-profile server runs locally, while a remote configuration runs in the remote environment.
Pick a setup method
Install from the MCP gallery
- Open Extensions in VS Code and search for
@mcp. - Select a server and install it in the user profile or workspace, depending on the scope you chose.
- Review the publisher and configuration details. Approve the trust prompt only if you trust the server.
- Start the server and verify its status using MCP: List Servers.
The official quickstart demonstrates this route with Playwright MCP. Gallery availability may vary by server; if you cannot find the one you need, use its own installation instructions with guided or manual configuration.
Use the guided configuration command
Open the Command Palette and run MCP: Add Server. Follow the prompts to choose a server type and whether to save it for the current workspace or your global/user profile. This is useful when the server is not installed from the gallery or needs custom launch settings.
Configure it manually for a workspace
Create or open .vscode/mcp.json. VS Code’s format has a top-level servers object and provides IntelliSense. Use the server’s documented command, package, URL, and authentication requirements; the examples below show the structure, not a universal package or endpoint.
Choose the transport and configure the server
Local process over stdio
A local server commonly launches as a child process and communicates over standard input/output (stdio). In this example, replace the package name and arguments with the server’s official launch instructions. The command must be available in the environment where VS Code launches the server.
{
"servers": {
"my-server": {
"command": "npx",
"args": ["-y", "<server-package>"]
}
}
}For stdio servers, command is required. Depending on the server, you can also configure args, cwd, env, envFile, and development settings. Use the server’s instructions for required variables and working directory; do not assume a package can be launched with npx just because the example uses it.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
If launching through Docker, keep the container in the foreground. A detached container exits the communication path VS Code needs for stdio.
Remote server over HTTP
For a remote server that supports Streamable HTTP, configure its endpoint as an HTTP server:
{
"servers": {
"my-remote-server": {
"type": "http",
"url": "https://example.com/mcp"
}
}
}VS Code tries HTTP Stream first and falls back to SSE if HTTP is unsupported. Use the exact endpoint and transport documented by the server. Older or specialized servers may expose SSE rather than Streamable HTTP; do not change transports without checking server support.
Authentication and secrets
The VS Code reference supports HTTP headers and OAuth configuration. VS Code handles the OAuth flow and opens a browser for first authorization. Use an input variable or environment file for credentials instead of writing API keys or tokens directly into a configuration file that might be shared or committed. For stdio servers, supply secrets through the server’s expected environment variables or its documented secure input mechanism.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Rank #3
Use portable or automatically discovered configuration when appropriate
VS Code’s .vscode/mcp.json is VS Code-specific. For portable configuration read by the Agent Host and compatible Copilot tools, the documented format is .mcp.json with a top-level mcpServers object; user-level configuration can be stored at ~/.copilot/mcp-config.json. These formats are not interchangeable: use the key and location expected by the host that will read the file.
Agent Host sessions do not read .vscode/mcp.json directly. VS Code forwards eligible entries, but configurations requiring interactive input may not be forwarded. If the same server needs to work in an Agent Host session, configure it in a format and location the Agent Host supports rather than assuming the workspace file will be consumed as-is.
VS Code can also discover configurations from supported applications, including Claude Desktop, GitHub Copilot CLI, Cursor, and Windsurf. Discovery sources are off by default. If you want to use this route, enable the relevant sources through chat.mcp.discovery.enabled and verify the imported server configuration before starting it.
Start the server and use its tools in Chat
- Start or install the configured server. If prompted, review and approve its trust request only when you accept the publisher and the server’s behavior.
- Open Chat and select Configure Tools.
- Find the server’s tools and toggle on the ones you want available to the agent.
- Ask Chat to use a relevant tool. Tool availability does not guarantee every request will invoke it; make the requested task and tool purpose clear.
Servers may provide more than tools. Depending on the implementation, VS Code can also add MCP resources as chat context or invoke server prompts using slash-command syntax. Tools that are not marked read-only may trigger a confirmation dialog. Review proposed actions before approving them.
Connect ScreenshotNeo for screenshot work
If your goal is to have an AI agent capture website screenshots, ScreenshotNeo is a relevant MCP-server option as well as a screenshot API. Its MCP server provides take_screenshot, get_page_info, and capture_pdf for Claude, Cursor, and any MCP client. Use ScreenshotNeo’s current setup documentation for its MCP connection details; the information here does not assume a package name or configuration that is not specified.
Or skip the browser setup
For a direct API screenshot instead of configuring browser automation, one GET request can return an image or PDF. This cURL example saves a WebP screenshot of Stripe; replace the target URL with the page you need and use your API key. See the ScreenshotNeo API documentation for request options.
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpScreenshotNeo accepts cookie or consent banners like a visitor and removes more than 60 known consent platforms, newsletter popups, and chat widgets before capture; each step can be turned off. Bot checks/CAPTCHAs, blank pages, timeouts, failed loads, and cache hits are not billed, and response headers report the page verdict and billing status. Its MCP server lets AI agents take screenshots. The Free plan includes 1,000 screenshots per month with no card; paid plans start at $5 for 3,000. Learn about ScreenshotNeo, or sign up for the free plan.
Troubleshoot a server that will not connect
- Open the Command Palette and run MCP: List Servers.
- Select the server and inspect its status.
- Choose Show Output and read the reported error.
- Correct the configuration or connection issue, select Restart Server, and try again.
- If it connects but a tool is not invoked, check the separate VS Code guidance for tool invocation and confirm that the tool is enabled in Configure Tools.
Common causes and fixes
| Symptom | What to check | Fix |
|---|---|---|
| Stdio server fails to start | The command exists in the environment where VS Code is running; its arguments and working directory match the server’s instructions. | Install the required runtime or use the command’s full path; correct arguments or cwd, then restart. |
| Server works locally but not in a remote workspace | The configuration location determines where the process runs. | Put it in the remote user configuration or Dev Container configuration if the server must run remotely. |
| HTTP connection fails | The endpoint URL and transport match the server; any required authorization is configured. | Correct the endpoint or authentication settings. Check the server’s own instructions and the Show Output message. |
| OAuth or credentials fail | The authorization flow completed and secrets are provided through the expected mechanism. | Complete the browser authorization when prompted; replace hardcoded credentials with an input variable or environment file. |
| Docker stdio process disconnects | The container may have been launched in detached mode. | Run the container in the foreground so it remains attached to the stdio connection. |
| Server connects but the expected tool is missing | The server exposes that tool, and it is enabled in Chat’s Configure Tools list. | Enable it if present; if absent, verify the server configuration and its documented capabilities. |
Understand the trust and sandboxing trade-offs
Visual Studio Code warns: “Local MCP servers can run arbitrary code on your machine.” Install only servers from sources you trust, and review the publisher and configuration before starting one. Configuration can cause code to run locally or in a remote environment, so verify both the source and the location.
VS Code documents optional sandboxing for local stdio servers on macOS and Linux, with filesystem and network allow rules. The documentation says sandboxing is unavailable on Windows. When sandboxing is enabled, tool confirmations are auto-approved; understand the configured restrictions and the server’s behavior before relying on that setting.
Best Value
Frequently asked questions
Does an MCP server have to run on my computer?
No. A stdio server generally launches as a local process in the environment where it is configured. A remote server can instead be reached over HTTP or SSE. Workspace, user, remote, and container configuration affect the execution location.
Why does my configuration use servers in one file and mcpServers in another?
They are different host configuration formats. VS Code’s .vscode/mcp.json uses servers; portable MCP configuration described for the Agent Host uses mcpServers.
Can I use an MCP server’s prompts and resources, not just tools?
Yes, if that server provides them. VS Code can use MCP resources as chat context and invoke server prompts with slash-command syntax, in addition to exposing tools.
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteQuick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
