To connect Cline to a remote MCP server over HTTP, open MCP Servers, choose Remote Servers, enter the server’s complete endpoint URL, select Streamable HTTP, add any required authentication headers, and save. If you edit configuration JSON, set "type": "streamableHttp" explicitly. Leaving out type makes Cline fall back to legacy SSE, which can produce an HTTP 405 when the endpoint expects Streamable HTTP.
What you need before configuring Cline
Have these details from the MCP server operator:
- The complete HTTPS endpoint, including any path such as
/mcp. - The transport the endpoint supports: Streamable HTTP or legacy SSE.
- Authentication requirements, including the exact header name and value format.
- Whether the endpoint is expected to expose tools that your Cline workspace can call.
Do not paste a real access token into a tutorial, screenshot, shared repository, or public issue. Use a placeholder while testing the shape of your configuration, then add the credential through your local Cline settings.
Add a remote HTTP server in Cline’s interface
- Open Cline in your editor and open the MCP Servers panel.
- Choose Remote Servers. This is the remote-server flow; local STDIO configuration is a different setup.
- Enter a unique, descriptive server name, for example
company-tools. - Paste the complete URL supplied by the operator. Do not replace it with the site’s home page or omit a path segment.
- Select Streamable HTTP. Use legacy SSE only when the server’s own instructions explicitly require SSE.
- Add authentication details only when the service requires them. For a bearer token, use the header format documented by that service.
- Add the server and wait for Cline to report its connection status.
- Confirm that the server’s tools appear, then try a low-risk tool call. A successful connection is not the same as a useful server: the endpoint must expose the tools your task needs.
Configure the server as JSON
Cline stores remote entries under mcpServers. The following is a configuration shape, not a working endpoint or credential:
{
"mcpServers": {
"my-remote-server": {
"type": "streamableHttp",
"url": "https://example.com/mcp",
"headers": {
"Authorization": "Bearer YOUR_TOKEN"
},
"disabled": false,
"autoApprove": []
}
}
}Replace the URL and header value with the values supplied by the server operator. Keep the transport value exactly as streamableHttp: the capitalization and camel-case spelling matter. The headers object is optional and should be omitted when the server does not require custom headers. disabled and autoApprove are part of the documented Cline entry shape; leave them at their existing values unless you intentionally want to change that server’s behavior.
#1 Best Overall
When using Cline’s configuration action or editor integration, place the entry in the MCP configuration managed by Cline rather than creating an unrelated JSON file that Cline never reads. The exact file location can vary with your editor, installation, and Cline version, so use the configuration action shown in your current MCP Servers interface.
Choose the correct HTTP transport
| Transport | Cline value | Use it when | Important consequence |
|---|---|---|---|
| Streamable HTTP | streamableHttp |
The endpoint documentation says it supports Streamable HTTP. | Set the value explicitly; this is the recommended remote-server choice in Cline’s current guide. |
| Legacy SSE | Use the SSE option presented by Cline | The server operator specifically documents the legacy SSE transport. | Omitting type makes Cline default to legacy SSE for backward compatibility. |
These are not interchangeable labels. A server listening for Streamable HTTP may reject an SSE request even though both are described informally as “HTTP MCP.” Select the transport implemented by the endpoint, not the one that sounds familiar.
Authentication and headers
Authentication is service-specific. Some servers accept an Authorization bearer token; others may require a different header or no header at all. Copy the operator’s required header name, prefix, and value format exactly. For example, the documented GitHub MCP Server Cline setup uses an Authorization bearer-token header, but that example is not a universal requirement for every MCP server.
Keep secrets out of autoApprove lists, prompts, source control, and diagnostic screenshots. If a token has been exposed, revoke or rotate it through the service that issued it before continuing.
Verify that the connection actually works
- Entry status: the server should show as connected rather than stopped or unavailable.
- Tool discovery: tools supplied by the endpoint should appear in Cline’s MCP view.
- Safe call: invoke a read-only or otherwise harmless tool and check its response.
- Scope: confirm that the returned tools belong to the server you intended to add, especially if several entries have similar names.
A server can be reachable while still exposing no usable tools. Treat missing tools as a server capability, URL, or authorization problem rather than immediately changing transports.
Troubleshoot common failures
HTTP 405, “SSE,” or method-not-allowed errors
First check the endpoint’s required transport. If it expects Streamable HTTP, make sure the entry contains the exact JSON value "type": "streamableHttp". A missing or misspelled value can make Cline fall back to SSE; the documented GitHub MCP Server example warns that this fallback can result in a 405. This explanation is specific to that documented server behavior, so also check the endpoint’s own instructions.
401 or 403 authentication errors
Confirm whether authentication is required, whether the token is still valid, and whether the header format is correct. Check for accidental whitespace, a missing Bearer prefix, an expired credential, or a token issued for a different environment. Remove any header that the operator did not request; an incorrect header can be rejected just as an absent one can.
Connection refused or endpoint unavailable
Recheck the full URL, including scheme, hostname, port, and path. Verify that the server is running and reachable from the machine where Cline runs. A browser opening the domain’s home page does not prove that the MCP path is available.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →Rank #3
- Upgraded Two Zipper Pockets: Forvencer server books feature two secure zipper pockets for better organization of coins, cash, and receipts, ensuring that everything you collect has a safe and secure place
- Smart Storage & Quick Access: Designed with 8 multi-functional compartments, the right side includes a guest receipt pad, while the left has a money pocket, ticket pocket, and credit card slot. Two small clear pockets store bills, receipts, and other visible items. A stitched pen loop ensures you always have your favorite pen ready
- High-quality & Easy to Clean: Crafted from high-quality PU leather with heavy-duty stitching, this server book is built to last. It resists tears, scratches, and its waterproof surface makes cleaning easy with just a damp cloth or a non-chlorine sanitizer
- Perfect Fit for Your Apron: Measuring 5” x 8”, this compact organizer is slightly smaller than other models, making it ideal for bending or sitting while carrying in your server apron. It holds everything a waitress needs—a place for everything
- What's Included: This server organizer comes with multiple open and zippered pockets to store money, receipts, tips, etc. Clear sleeves are perfect for keeping menus or special lists while serving. Available in a variety of colors, allowing you to express yourself even when in uniform
The server connects but no tools appear
Ask the operator whether the endpoint exposes MCP tools and whether your account is authorized to see them. Check that you added the intended server entry rather than a documentation URL, health-check URL, or proxy route that does not implement MCP.
Intermittent timeouts
Check the endpoint’s availability and any network proxy, VPN, firewall, or corporate gateway between Cline and the server. Cline’s troubleshooting guidance also points to URL or process status, exposed tools, credentials, and timeout settings. Do not “fix” a timeout by switching to SSE unless the server actually supports SSE.
Changes do not take effect
Save the entry through Cline’s MCP interface, verify that the JSON is valid, and reopen or reload the MCP panel if your installation requires it. Check for duplicate names or entries: you may be editing one definition while Cline is loading another.
Operational advice for teams
Name entries for their purpose
Use names that identify the service and environment, such as github-readonly or internal-staging-tools. Avoid several entries named only server; ambiguous names make tool selection and incident diagnosis harder.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Fix the driver behind crashes, sound loss and screen glitches3Repair Windows errors before they cause bigger problemsKeep transport and credentials documented together
Record the endpoint, required transport, authentication method, and expected tools in your team’s private runbook. A URL without its transport requirement is incomplete because Cline can otherwise select legacy SSE by default.
Start with least privilege
Use a token limited to the tools and resources needed for the task. Test a read-only operation before enabling workflows that modify external systems. Review any approval behavior represented by your Cline configuration before allowing an agent to call sensitive tools.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Or skip the browser setup
If your Cline workflow needs website screenshots rather than a general-purpose remote MCP endpoint, ScreenshotNeo provides a website screenshot API and an MCP server for AI agents, including Claude, Cursor, and other MCP clients. Its capture pipeline accepts cookie or consent banners and removes more than 60 known consent platforms, newsletter popups, and chat widgets before the shot; each cleanup step can be turned off. Bot checks, CAPTCHAs, blank pages, timeouts, failed loads, and cache hits are not billed, and responses identify the page verdict and billing result with X-Page-Verdict and X-Billed headers.
The one-call API returns PNG, JPEG, WebP, or PDF. See the ScreenshotNeo documentation for all options.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →cURL
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}`);ScreenshotNeo also supports full-page captures with lazy images loaded, CSS-selector element capture, dark mode, device presets and custom viewports, retina scale, PDF paper and page controls, custom CSS and JavaScript, pre-capture clicks, hidden selectors, selector or network-idle waits, request and resource blocking, custom headers, cookies, user agents, time zones, geolocation, transparent backgrounds, resizing, chosen cache TTLs, signed image links, asynchronous jobs with signed webhooks, bulk capture for up to 100 URLs per call, a usage API, an OpenAPI specification, and parameter names used by other screenshot APIs.
The Free plan includes 1,000 shots each month with no card. Paid plans start at $5 for 3,000 shots; every feature is available on every plan, and yearly billing provides two months free. Create a free ScreenshotNeo account to get the 1,000-shot allowance without adding a card.
FAQ
Can I leave the URL field at the domain root?
Only if the MCP service is actually mounted at the root. Use the complete endpoint supplied by the operator, including its MCP path.
Is a bearer token always required?
No. Authentication depends on the service. Add the header only when the operator specifies one, and follow that service’s exact format.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
What should I test first after adding the server?
Check that tools are listed, then call a harmless read-only tool so you verify both discovery and execution.
Frequently Asked Questions
Can I leave the URL field at the domain root?
Only if the MCP service is actually mounted at the root. Use the complete endpoint supplied by the operator, including its MCP path.
Is a bearer token always required?
No. Authentication depends on the service. Add the header only when the operator specifies one, and follow that service’s exact format.
What should I test first after adding the server?
Check that tools are listed, then call a harmless read-only tool so you verify both discovery and execution.
Recommended Free Tools
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.
