MCP and AI basics
Remote MCP server
An MCP server hosted by the vendor and reached over the internet. Setup is usually adding a URL and signing in.
A remote MCP server is hosted by the vendor and reached over the internet. You add it to an assistant by URL, sign in, and the vendor's infrastructure handles the connection to its own API. Nothing is installed locally and no API key is pasted anywhere, which makes it the easiest option for a merchant.
The directory marks these as 'Remote (hosted by vendor)'. Examples include the Stripe, Klaviyo, HubSpot and Wix servers and Meta's ads AI connectors. Most sign in with OAuth, so the permissions you grant are shown on a consent screen and can be withdrawn later from the vendor's account settings.
Remote does not mean read-only. Several hosted servers include write tools, and the vendor's sign-in may request broad scopes by default. Read the consent screen, prefer a read-only role or restricted key where the vendor offers one, and keep the host's approval step on for anything that changes live data.