← Back to Dashboard
1. OAuth & Security2. Deployment Strategies3. MCP Across Tools4. Agentic Orchestration5. Remote MCP & Connectors
Deployment Strategies
Going to Production
How you deploy depends entirely on your use case:
- Private Desktop Tools (stdio): Best for manipulating local files. Distribute the code via
npm install -gorpipx install. The user editsclaude_desktop_config.jsonmanually. - Internal SaaS Integrations (SSE): Best for teams accessing a centralized company database securely. Deploy as an HTTP container on AWS/Vercel. Teams configure their Host with an API key.
- Public Platforms: Companies providing public APIs (like Notion or Slack) will host public, rate-limited MCP endpoints that any user can connect their Claude Desktop to using OAuth.
⌨ HANDS-ON LABDeploy a Remote MCP Server to the Edge
⭐ +150 XPLocal stdio servers only serve you. Scaffold Cloudflare's remote MCP template and push it to the edge - one URL any client can connect to.
1Scaffold a remote MCP server from Cloudflare's authless template.
2Deploy it to Cloudflare Workers with wrangler.
OBJECTIVE 1 / 2 — type "hint" if stuck
🧪 Knowledge Check
Press 1-4 to select1 of 3
Which deployment strategy is best for a tool that scans identical local `node_modules` folders?
A public Vercel endpoint
A serverless function via SSE
A local stdio distribution via npm or pip
A Python Flask server on AWS EC2