What is a remote MCP server?
A remote MCP server runs over HTTP/SSE instead of a local process — you point your client at a URL instead of installing and running anything on your own machine.
Remote MCP Servers
Official hosted MCP endpoints from SaaS providers — connect directly, no install required.
Verified
Transform MCP
Unstructured
The Unstructured Transform MCP Server connects your ADK agent to Unstructured, a document processing platform that turns raw files into structured, AI-ready data. This integration gives your agent the ability to parse PD
Added in 4 hours
Rankbits
rankbits
AI visibility analytics across 15+ providers (ChatGPT, Perplexity, Gemini, AI Overviews, and more). The MCP connector lets assistants run scans, compare competitor mentions, and track your brand's visibility in AI answer
Added 6 hours ago
Frequently asked questions
Common questions about hosted and remote MCP servers
How is a remote server different from a local one?
A local server runs on your machine and needs a runtime like Node.js or Python. A remote server is hosted by a third party — you just need a URL (and sometimes an API key) to connect, which is simpler to set up but depends on the provider staying online.
Are remote MCP servers safe to use?
Your data passes through the provider's infrastructure, so stick to servers run by official or well-known teams that document how they handle data, and grant sensitive permissions carefully.
How do I connect to a remote MCP server?
Add the server URL in a client that supports remote MCP, then configure OAuth, an API key, or request headers as required by the provider. Streamable HTTP, SSE, and authentication support vary by client, so follow both the server page and client documentation.
Does a remote MCP server need to stay online?
Yes. Calls depend on network access, provider uptime, and rate limits. For important workflows, check the provider's status page, timeout and retry behavior, quotas, and fallback options.
Can Claude, Cursor, VS Code, and Codex use remote MCP servers?
Yes, when the client supports the server's remote transport and authentication method. Newer clients commonly support Streamable HTTP, while older versions may only support SSE or local stdio, so verify version compatibility first.