Free tools Windows power users keep installed
One-click scans. No signup required.
Some links on this page are affiliate links: if you buy through them we may earn a commission, at no extra cost to you.
Define each MCP server as its own named entry in your client’s MCP configuration, then use the client’s server controls to start and inspect them. In VS Code, one configuration can contain remote and local servers together. The exact file and schema depend on whether you use a workspace, portable workspace, user profile, or Agent Host session, so do not assume another MCP client uses the same path or keys.
What “start multiple MCP servers” actually means
MCP (Model Context Protocol) clients usually manage server processes from configuration. You do not need one terminal command that launches every server. Instead, create one uniquely named definition per server. The client reads those definitions, starts eligible processes, and exposes lifecycle actions such as start, stop, restart, and view logs.
VS Code’s documented example combines a remote GitHub server and a local Playwright server in one configuration. A remote entry points to a URL; a local entry specifies an executable command and its arguments. They remain separate services even though they are managed from the same server list.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Choose the VS Code configuration scope first
| Scope | File or location | Schema | Best for |
|---|---|---|---|
| Workspace | .vscode/mcp.json |
Top-level servers object |
Servers needed by one project |
| Portable workspace | Workspace-root .mcp.json |
Top-level mcpServers object |
Sharing a portable MCP configuration with compatible hosts |
| User profile | VS Code user MCP configuration | Use the format shown by your VS Code build | Servers available across workspaces |
| Agent Host | .mcp.json or ~/.copilot/mcp-config.json |
Agent Host format | Sessions where the Agent Host discovers and manages servers |
VS Code also provides MCP: Add Server in the Command Palette. Use it when you want the editor to generate the appropriate structure rather than editing JSON manually. Do not paste a servers configuration into a file expecting mcpServers, or vice versa.
#1 Best Overall
Method 1: configure several servers in .vscode/mcp.json
1. Create the workspace file
In the project root, create .vscode/mcp.json. Add one child property for every server and give each property a distinct name. This illustrative configuration follows VS Code’s documented split between a remote URL and a local command:
{
"servers": {
"github-remote": {
"type": "http",
"url": "https://example.invalid/mcp"
},
"playwright-local": {
"type": "stdio",
"command": "npx",
"args": ["@playwright/mcp@latest"]
}
}
}Replace the example URL, command, and arguments with values documented by each server publisher. The names are labels used by VS Code; they do not install or authenticate the servers.
2. Review execution and credentials
- Confirm the publisher, package, executable, and arguments before allowing a local server to run.
- Local MCP servers can run arbitrary code on your machine. Treat a new entry like any other executable you are about to trust.
- Do not hardcode API keys in a committed JSON file. Use the credential mechanism supported by the server and your client, or environment-variable substitution where VS Code and that server document it.
- Check whether a server should run on your local computer or on a remote development host. Processes run wherever they are configured to run.
3. Save, then use the MCP controls
- Save
.vscode/mcp.jsonand respond to any trust or permission prompt after checking the entries. - Open the Command Palette and run MCP: List Servers.
- Select a server to start, stop, restart, or inspect it. Use the output/log action (shown as Show Output in VS Code) when a process fails.
- Repeat the action for each configured server, or use the available start-all action in the server management UI if your installed VS Code version exposes it.
There is no universal guarantee that every VS Code release starts all entries at exactly the same moment. The reliable model is “several independently named servers managed from one client.”
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 minuteMethod 2: use the portable .mcp.json format
If you specifically want the portable workspace format, create .mcp.json at the workspace root and use mcpServers instead of servers:
{
"mcpServers": {
"github-remote": {
"type": "http",
"url": "https://example.invalid/mcp"
},
"playwright-local": {
"type": "stdio",
"command": "npx",
"args": ["@playwright/mcp@latest"]
}
}
}VS Code documents that the Agent Host reads .mcp.json (or the user file ~/.copilot/mcp-config.json) directly, while VS Code forwards eligible servers from .vscode/mcp.json. Consequently, a server visible in one surface may not be started by another. Check which host is running your agent session before diagnosing a missing server.
Automatic startup and lifecycle behavior
VS Code’s automatic-start setting has three documented values:
never: do not automatically start configured servers.onlyNew: automatically start newly added servers.newAndOutdated: start newly added and outdated servers; this is documented as the default.
Disabled or errored servers are excluded from that automatic pass. Change the setting through VS Code’s MCP configuration UI or settings, then verify the result with MCP: List Servers. Automatic start is a client behavior, not an MCP protocol feature.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →For Agent Host sessions, the Agent Host may start servers discovered from its own configuration independently of VS Code’s automatic-start pass. If a process appears to start even after you change VS Code’s setting, inspect the Agent Host configuration and session logs.
Local versus remote execution
Local servers
A local definition launches the command on the machine where that configuration is being processed. It may inherit that machine’s filesystem, network access, installed runtimes, and environment variables. A command that works in your terminal can still fail in VS Code if the editor uses a different PATH, shell, virtual environment, or operating-system account.
Remote servers
A remote definition connects to a URL rather than spawning a local process. For remote development, VS Code documents configuring servers intended to run on the remote machine. Decide deliberately whether a server should access local files, remote files, or neither, and keep credentials in the environment that actually makes the connection.
Troubleshooting multiple-server startup
The configuration is ignored
- Cause: wrong filename, location, or schema.
- Fix: verify that
.vscode/mcp.jsonusesserversand that root.mcp.jsonusesmcpServers. Confirm the file is in the opened workspace.
Only one server appears
- Cause: duplicate names, malformed JSON, or the second entry is outside the server object.
- Fix: validate commas and braces, give every entry a unique name, then reopen MCP: List Servers.
A local process exits immediately
- Cause: missing runtime, incorrect package name, wrong arguments, or a command unavailable in VS Code’s PATH.
- Fix: run the exact command in a terminal, install the required runtime, use an absolute executable path when appropriate, and read Show Output for the process error.
A remote server cannot connect
- Cause: invalid URL, unavailable network route, TLS/proxy policy, or missing authentication.
- Fix: test the endpoint from the execution environment, check the server’s authentication instructions, and avoid embedding secrets in the JSON.
It starts twice
- Cause: the same server is present in both VS Code configuration and Agent Host configuration.
- Fix: choose one owner for that process and remove or disable the duplicate entry.
It works locally but not in a remote workspace
- Cause: the command or files exist only on the local machine.
- Fix: install the dependency and configure the server on the remote host if that is where the workspace runs, or deliberately point the client at a remote endpoint.
Performance, reliability, and cost considerations
- Starting many local servers increases process count, memory use, and startup time. Enable only servers needed for the current workspace.
- Prefer stable, pinned package versions for repeatable startup; update deliberately rather than changing every launch.
- Keep logs available while onboarding. A server that appears “slow” may be waiting for a browser, network connection, authentication, or package download.
- Remote servers shift compute and maintenance away from your machine but add network and service-availability dependencies.
- There is no MCP-wide pricing rule. Any usage charges, limits, or authentication requirements come from the individual server provider.
Or skip the browser setup
If one of the MCP tools you need is website capture, ScreenshotNeo provides an MCP server with take_screenshot, get_page_info, and capture_pdf tools for Claude, Cursor, and other MCP clients. You can also call its API directly:
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpPython:
import requests
r = requests.get("https://api.screenshotneo.com/v1/shot", params={"access_key": "YOUR_API_KEY", "url": "https://stripe.com"}, timeout=90)
open("shot.webp", "wb").write(r.content)Node.js:
const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://stripe.com' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);See the complete option list and MCP setup at ScreenshotNeo’s documentation. It accepts consent banners before capture and removes more than 60 known consent platforms, newsletter popups, and chat widgets; each cleanup step can be disabled. Bot checks, CAPTCHAs, blank pages, timeouts, failed loads, and cache hits are not billed, and response headers identify the page verdict and billing result. It supports full-page and element captures, device and retina settings, PDFs, custom CSS or JavaScript, waits, request blocking, headers, cookies, geolocation, caching, signed links, asynchronous jobs, bulk capture, and a usage API. The free plan includes 1,000 screenshots per month without a card; paid plans start at $5 for 3,000. Create a free ScreenshotNeo account.
Final verification checklist
- Every server has a unique name.
- The filename and top-level schema match the host.
- Commands, arguments, URLs, and runtimes work in the intended execution environment.
- Secrets are supplied through approved credential handling, not committed JSON.
- You checked MCP: List Servers and Show Output.
- You confirmed that VS Code and Agent Host are not both launching the same process.
Frequently Asked Questions
Does adding an MCP entry install the server package?
No. A configuration entry describes how the client should connect to a remote service or launch a command; local runtimes and packages must already be available unless the command itself performs installation.
Can two entries use the same executable?
Yes, provided each has a distinct name and its arguments or environment identify the intended server instance.
Where should I look when startup behavior differs between editor windows?
Compare workspace configuration, user-profile configuration, workspace trust, and whether the session is being managed by VS Code or the Agent Host.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →The Bottom Line
Use one named definition per MCP server, choose the schema that matches the VS Code file you are editing, and verify ownership when Agent Host sessions are involved. The server list and output logs are the fastest way to confirm what actually started.
Quick 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.
