How to Host a Remote MCP Server Securely
Set up ownership, identity, permission checks, and release validation for a remote MCP server before connecting it to live customer data.
Remote hosting makes an MCP server available to compatible assistants over the network. Decide who owns the environment, which clients can connect, and which records each user may retrieve before connecting it to a live product.
Keep authorization with the application
Use HTTPS and an authorization setup compatible with the intended clients. Validate that the access token is issued for your MCP server. Carry the user's identity and access context into the product API, which should enforce account and record permissions on every request.
Choose a host your team can operate
Compare a managed platform with infrastructure your team already runs. In either case, assign an owner for the deployment, configuration, credentials, incident response, and updates. Log tool calls and outcomes with enough detail to investigate failures. Keep tokens and sensitive payloads out of logs.
Prove the access boundary before launch
Start with a read-only capability and use test accounts with different permissions. Verify that allowed records match the source and that restricted records remain inaccessible. Recheck client compatibility and permission behavior after changes to the connector, identity provider, or product API.
See the MCP authorization guide and the custom MCP planning guide.