Remote or local: two ways to run an MCP server
By Sophie Filer · Updated 26 Oct 2026
Every server on MCP Shelf runs one of two ways, and some run both. The choice decides who holds your data and what you have to install.
Side by side
| Local | Remote | |
|---|---|---|
| Config | command and args (npx, uvx, docker) | url |
| Runs on | Your computer | The provider's servers |
| You install | Node.js, Python/uv or Docker | Nothing |
| Your data | Stays on your machine unless the tool sends it | Passes through the provider |
| Works in ChatGPT | No | Yes |
| Works offline | Often | No |
Choose local when
- The server works on your files, your terminal or a database on your network.
- You cannot send the data to a third party.
- You want to read and pin the exact code that runs.
Choose remote when
- The vendor runs it (Notion, Supabase, GitHub), so sign-in and updates are their job.
- You use ChatGPT or switch between several apps.
- You do not want Node or Python on the machine.
Questions
Are "remote" and "hosted" the same thing?
Yes. Both mean the server runs somewhere else and your app connects to it over HTTP.