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.
Official hosted MCP endpoints from SaaS providers — connect directly, no install required.
Figma
Files, designs, Dev Mode context
Magic Patterns
Discuss and iterate on Magic Patterns designs
tldraw
Diagrams and whiteboards
Send
Create shareable documents, one-pagers, and decks
Eraser
Generate, manage, and update Eraser diagrams and files
BioRender
Scientific figures, illustrations
Gamma
Presentations, documents, websites
Trimble SketchUp
Create and iterate 3D models for use in SketchUp
Spotify
Music and podcast recommendations, just for you.
Lucid
Ideate, diagram, and align teams
Splice
Search Splice's sounds catalog, build stacks & more!
Mermaid Chart
Validates Mermaid syntax, renders diagrams as high-quality SVG, and displays them instantly in an interactive UI where users can preview, zoom, and iterate in real time.
Excalidraw
MCP for creating interactive hand-drawn diagrams in Excalidraw
Audible
Ask for audiobook recommendations
Canva
Designs, assets, exports, comments
Melon
Browse music charts & your personalized music picks
Adobe for creativity
Ideate, create, and deliver with Adobe pro tools
Cloudinary
Manage, transform and deliver your images & videos
Miro
Access and create new content on Miro boards
Adobe Experience Manager
Manage your Adobe Experience Manager content
Common questions about hosted and remote MCP servers
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.
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.
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.
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.
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.
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.