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 & 11Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchTo connect an MCP server to Cline in VS Code, open Cline’s MCP Servers panel, choose Configure → Configure MCP Servers, then add the server under the top-level mcpServers object in Cline’s settings JSON. Use a command-based entry for a local STDIO server; for a hosted Streamable HTTP server, provide its URL and set "type": "streamableHttp" exactly. Save the configuration, enable the server, and check that its tools appear in Cline.
What MCP integration does in Cline
The Model Context Protocol (MCP) lets Cline use tools and data sources exposed by MCP servers. Depending on the server and transport, those capabilities can come from a local process, such as a script running on your computer, or a hosted service that Cline contacts over the network.
The two main setup choices are local STDIO and remote Streamable HTTP. With STDIO, Cline starts a process on the same machine and communicates with it through standard input and output. With remote HTTP, the server is hosted separately and Cline connects to its endpoint. The right choice depends on where the server runs, how you manage credentials, and whether you need to share the service across machines.
Open Cline’s MCP settings
- Install and open the Cline extension in VS Code.
- Open the Cline panel and click the MCP Servers icon, shown as stacked servers in the panel’s top toolbar.
- Open the Configure tab and click Configure MCP Servers. Cline opens its MCP settings JSON file.
- Add or edit server entries inside the top-level
mcpServersobject, then save the file.
If the object already contains other servers, add a new named entry inside it and preserve the existing entries. The server name is a label for your configuration; the required fields depend on the transport and the server’s own instructions.
Free tools Windows power users keep installed
One-click scans. No signup required.
#1 Best Overall
Configure a local STDIO server
Use a local entry when the MCP server runs as a process on the computer where VS Code and Cline are running. Cline’s configuration identifies the executable with command and can pass arguments, environment variables, and approval settings.
{
"mcpServers": {
"local-server": {
"command": "node",
"args": ["/path/to/server.js"],
"env": {
"API_KEY": "your_api_key"
},
"disabled": false,
"autoApprove": []
}
}
}commandis the executable Cline should start. It must be installed and available to the environment in which VS Code runs.argsis an optional array of command-line arguments. Replace the example script path with the actual path to your server.envsupplies environment variables to the process. Use the variable names expected by the server.disabledlets you leave the entry configured without enabling it; set it tofalsefor an enabled entry.autoApprovecontrols which tools Cline may approve automatically. An empty array avoids granting automatic approval to named tools.
Use the server maintainer’s documented launch command and required environment variables. The example above shows the configuration shape, not a universal command for every MCP server.
Configure a remote Streamable HTTP server
For a hosted server, use Cline’s Remote Servers tab or edit the JSON directly. Include the complete endpoint URL, set the transport to the exact camel-case value streamableHttp, and add any required authentication headers.
{
"mcpServers": {
"github": {
"url": "https://api.githubcopilot.com/mcp/",
"type": "streamableHttp",
"disabled": false,
"headers": {
"Authorization": "Bearer <YOUR_GITHUB_PAT>"
},
"autoApprove": []
}
}
}This GitHub example illustrates the remote configuration format. Use the endpoint and credentials issued for the MCP server you are connecting to; do not copy the example URL or token format for an unrelated service without checking its instructions. The transport value is case-sensitive in practice: Cline’s GitHub integration guidance specifies streamableHttp. Values such as streamable-http, or leaving out the type, can cause a fallback to SSE and a 405 response.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Choose between local STDIO and remote HTTP
| Consideration | Local STDIO | Remote Streamable HTTP |
|---|---|---|
| Where the server runs | As a process on the machine running Cline. | On a hosted service reached through its endpoint URL. |
| Configuration shape | command, usually with optional args and env. |
url, explicit type, and any required headers. |
| Credential handling | Can pass server-required variables through env; follow the server’s guidance for storing secrets. |
Can send required credentials in headers; follow the provider’s authentication and secret-handling guidance. |
| Process ownership | Cline starts and communicates with the local process. | The service is hosted separately; Cline connects to it over the network. |
| Sharing across machines | Each machine needs a usable local process and configuration. | A reachable hosted endpoint can be configured by clients on multiple machines, subject to the service’s access controls. |
| First checks when it fails | Confirm the executable, path, arguments, environment, and server process requirements. | Confirm the complete URL, exact transport spelling, network reachability, and authentication headers. |
Latency and operational reliability depend on the server, network, and environment; the transport choice alone does not establish a speed or uptime guarantee. For a process that should remain on your computer and use local resources, STDIO is the natural fit. For a service intended to be hosted and reached remotely, use the remote transport the server supports.
Verify that Cline has loaded the server
- Return to the Cline MCP Servers panel after saving the settings.
- Check that the server is listed and enabled.
- Confirm that its tools appear in Cline. If tools are missing, inspect the server’s startup or connection details and verify its configuration before relying on it in a task.
- Try a low-risk tool call and review what the tool does before approving it.
A saved JSON entry is not by itself proof that the connection succeeded. The useful verification is that Cline recognizes the enabled server and exposes its tools.
Keep Cline settings separate from VS Code MCP settings
Cline manages its MCP configuration through its own panel and JSON file, with a top-level mcpServers object. VS Code’s native MCP configuration uses a different surface: a workspace .vscode/mcp.json or a user profile file with a top-level servers object. VS Code also supports a portable .mcp.json using mcpServers for Agent Host interoperability.
These configurations are not interchangeable merely because both use MCP. If the intended client is Cline, add the entry through Cline’s MCP Servers panel and check for it there. Seeing an entry in VS Code’s native configuration does not establish that Cline has loaded it.
Troubleshoot common connection problems
Cline reports HTTP 405 for a remote server
Check the remote entry’s type first. For a Streamable HTTP server, use "type": "streamableHttp" with that exact spelling. A misspelled value or missing type can lead to an SSE fallback, which may produce a 405 response. Also confirm that the URL is the server’s MCP endpoint, not merely its website or API homepage.
The server does not appear in Cline
Make sure the entry is in Cline’s own settings JSON under mcpServers, not only in VS Code’s native MCP configuration. Check that the JSON is valid, the entry is enabled, and you saved the file. Then review the command or URL for typos.
A local server fails to start
Verify that the executable named by command is installed and available to VS Code, and that every path in args is correct. Check the server’s own startup requirements and confirm that the environment variable names and values match its documentation. A command that works in a separate terminal may still fail if VS Code is using a different environment or working context.
A remote server cannot authenticate
Confirm that the provider requires the header you configured, that its name and value are correct, and that the credential is valid and permitted to access that server. Avoid placing real secrets in shared or committed settings files. If a token has been exposed, replace it according to the provider’s procedures.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Clear out junk files and repair common Windows errors3Fix the driver behind crashes, sound loss and screen glitchesThe connection is slow or times out
Check the server’s availability and the client machine’s network connection. Cline’s troubleshooting guidance recommends increasing the MCP timeout when a server is slow. A longer timeout can accommodate a slow response, but it does not fix an incorrect URL, an unavailable process, or a server that cannot complete the request.
The server connects but a tool does not work
Check the server’s requirements for that specific tool, including permissions, arguments, and credentials. Review the tool call before approving it, especially if it can change data or perform actions outside the project. Troubleshooting the connection and troubleshooting a particular tool call are separate tasks.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Manage servers with the Cline CLI
Cline’s CLI includes an mcp wizard for listing, adding, editing, enabling or disabling, and deleting servers. The documented non-interactive listing commands are:
cline config mcp
cline config mcp --jsonUse the wizard for guided changes, or the JSON form when you need a machine-readable listing. CLI availability and command behavior can vary with the installed Cline version, so consult the Cline documentation for the version you use if a command is not recognized.
Security: treat MCP servers as tools with real access
- Install servers only from sources you trust. A local MCP server is executable code, and starting it can run code on your machine.
- Review the server publisher, launch command, and configuration before enabling it.
- Store secrets in environment variables where appropriate, rather than hard-coding them in a file that may be shared or committed.
- Keep
autoApprovelimited to tools you consider safe to run without a prompt. Review other tool calls before approval. - For remote services, use only the authentication method and endpoint supplied by the service provider, and protect access tokens as credentials.
Or skip the browser setup
If what you need from an MCP server is website screenshots, ScreenshotNeo offers a screenshot API and an MCP server for AI agents, including Cline and other MCP clients. Its MCP tool names are take_screenshot, get_page_info, and capture_pdf. The exact Cline connection fields for a ScreenshotNeo MCP server are not specified here, so use ScreenshotNeo’s documentation for its current server connection instructions rather than guessing an endpoint.
You can also capture a page with one API request. This runnable cURL example saves the returned image as WebP; replace the sample URL and provide your API key.
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpSee the ScreenshotNeo documentation for request options. Before capture, ScreenshotNeo accepts cookie or consent banners like a visitor and removes more than 60 known consent platforms, newsletter popups, and chat widgets; each cleanup step can be turned off. Bot checks and CAPTCHAs, blank pages, timeouts, failed loads, and cache hits are not billed. Responses identify the page verdict and billing status in the X-Page-Verdict and X-Billed headers. Its MCP server lets AI agents take screenshots, while the API provides PNG, JPEG, WebP, or PDF output.
The free plan includes 1,000 shots per month with no card required. Paid plans start at $5 for 3,000 shots; every feature is available on every plan. Try it by signing up for 1,000 free screenshots a month with no card.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →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.
