Locus product guide · Updated November 10, 2026

What is a remote MCP server? Setup, auth and limits

A remote MCP server runs on the internet and serves agents over Streamable HTTP at one HTTPS URL, such as https://api.paywithlocus.com/api/credits/mcp. A local server runs on your machine as a child process over stdio. Remote servers need no install, serve many clients at once, and sign users in with OAuth 2.1. In exchange you trust the host with your data, and every call makes a network round trip.

Setup, step by step

Step 1
Get the server URL
The provider gives you an HTTPS URL that ends in the MCP endpoint path. Use the full URL, including the path.
Step 2
Add the server to your client
In Claude Code, run claude mcp add with the HTTP transport, a name and the URL. In Claude or Claude Desktop, open Connectors in settings, choose Add, then Add custom connector, and paste the URL.
```
claude mcp add --transport http locus https://api.paywithlocus.com/api/credits/mcp
```
Step 3
Sign in
Most remote servers use OAuth. In Claude Code, run /mcp, pick the server and choose Authenticate. Approve the access in your browser. Do not paste an API key into the config unless the server asks for one.
```
/mcp
```
Step 4
Review the tools
Check which tools the server lists and turn off any you do not want the agent to use. Claude connector settings let you enable or disable each tool.

How is a remote MCP server different from a local one?

Both speak the same protocol. They differ in where the code runs and what it can reach.

How is a remote MCP server different from a local one?
Question	Local server (stdio)	Remote server (Streamable HTTP)
Where it runs	On your machine, launched by the client	On the provider’s infrastructure
Clients served	Usually one	Usually many
Install	A package or binary per machine	None, just a URL
Credentials	Read from environment variables	OAuth 2.1 sign-in, or a header the server accepts
Access to your files	Everything your user account can read	Only what you or the agent send it
Updates	You update each machine	The provider updates the server
Example	The filesystem reference server	The Sentry MCP server

How does Streamable HTTP work in the current spec?

Streamable HTTP replaced the older HTTP+SSE transport in the 2025-03-26 spec. The 2026-07-28 revision simplified it again.

One endpoint. The server accepts POST at a single path, such as /mcp.
One POST per message. The server replies with a JSON object or an SSE stream scoped to that one request.
No sessions. The Mcp-Session-Id header, the GET stream and stream resumption are gone. A broken stream means the client sends the request again.
Headers for routing. Each POST carries MCP-Protocol-Version, Mcp-Method and, for tool calls, Mcp-Name.
Change notices. A client that wants tool list updates opens one subscriptions/listen stream.
Safety rules. Servers must validate the Origin header. A server running locally should bind to 127.0.0.1, not all interfaces.

What limits do remote MCP servers hit?

Most limits come from the client, not the protocol. Claude Code documents these defaults.

Output size: a warning above 10,000 tokens per tool result and a 25,000-token cap. MAX_MCP_OUTPUT_TOKENS raises the cap.
Response size: an HTTP response over 16 MiB fails.
Text results over 50,000 characters are saved to a file instead of entering context.
Server instructions and tool descriptions loaded up front are limited to 4,096 characters each.
A configured Authorization header turns off the OAuth fallback for that server.

Should I build my own remote MCP server?

Build one when you own the data or the API and want any MCP client to use it. The official SDKs handle the transport. You still need OAuth, rate limits, input validation and logs.

You can also skip the code. AWS AgentCore Gateway turns APIs and Lambda functions into MCP tools. Kong AI Gateway maps REST endpoints to MCP tools. Both add sign-in and logging.

If the tools you want are other companies’ paid APIs, a hosted server that already wraps them saves the build and the provider accounts.

MCP gateways compared

What does the Locus Pro remote MCP server offer?

Locus Pro runs one remote server at https://api.paywithlocus.com/api/credits/mcp in front of many paid APIs. It uses Streamable HTTP and browser OAuth. The compact surface lists four tools: search, describe, execute and get_result.

Locus also runs single-purpose servers, such as https://search.mcp.paywithlocus.com for web search and https://scrape.mcp.paywithlocus.com for scraping. Each one is its own OAuth resource, so each needs its own sign-in. All of them bill the same credit balance.

Search and describe are free. Paid calls cost the catalog price, and 1,000 credits equal $1. Brave web search costs 30.3 credits. Firecrawl scrape costs 1 to 38.6 credits and was 1 credit on most recent calls. Hunter email finder costs 1 to 10.1 credits. Prices checked November 10, 2026.

Should I use a local or a remote MCP server?

Pick by what the server has to touch.

It must read or change files on your machine: local, ideally inside a container.
It wraps a web service or SaaS account: remote, run by that service.
Several people or agents share it: remote, so you update and secure it in one place.
It handles secrets you cannot share with a third party: local or self-hosted.
Your client only speaks stdio: use a bridge that speaks Streamable HTTP and OAuth, or switch clients.

Frequently asked questions

Can a remote MCP server read files on my computer?

No. It only sees what the client sends it, such as tool arguments. A local server runs with your user account and can read anything that account can read.

Do remote MCP servers still use SSE?

The old HTTP+SSE transport is deprecated. Streamable HTTP can still stream a single reply as server-sent events. Claude Code 2.1.265 and later tries HTTP first and switches to SSE for servers that only offer the old transport.

Is a remote MCP server slower than a local one?

Each call adds a network round trip, and the tool behind it may call another API. Locus Pro search results show success rate and latency for a tool once it has 20 calls in 7 days.

Who can see my data on a remote MCP server?

The server operator, and any provider the server calls for you. Read the operator’s data policy. Locus Pro sends each request to the provider named on the tool, such as Brave Search or Firecrawl.

Implementation references

Use these first-party references for current request contracts and account requirements. Tool availability, prices, and negotiated terms can change.

Sources

Third-party details were checked on November 10, 2026. Vendors change pricing and features often, so confirm on their site before you decide.