Create app hosting
OfficialClick on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Create app hostingdeploy this repo to Create and add Postgres"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Create.com MCP servers
Deploy apps and run your online store on Create.com from any AI assistant or editor that speaks the Model Context Protocol.
Both servers are remote (streamable HTTP) and sign you in with OAuth on first use: nothing to install, no key to paste.
Server | URL | What it does |
Create app hosting ( |
| Create projects; deploy files, container images or Git repositories; attach domains; set write-only secrets; add Postgres; read logs, metrics and failure summaries; roll back. You choose which projects it may touch, a monthly spend limit and a size ceiling when you connect. |
Create Commerce ( |
| Work in one Create store: products, variants, collections, stock across locations, orders, returns, customers, draft orders with a link to your own checkout, pages, posts, navigation and theme. No tool refunds, cancels, pays out or issues gift cards. |
Registry names: com.create/apps, com.create/commerce (MCP Registry).
Install
One click
App hosting | Commerce | |
Cursor | ||
VS Code | ||
VS Code Insiders | ||
LM Studio |
|
|
Gemini CLI |
| (same extension) |
Claude
claude.ai / Claude Desktop: Settings → Connectors → Add custom connector → paste the URL → Connect.
Claude Code:
claude mcp add --transport http create https://mcp.create.com/apps(orcreate-commerce https://mcp.create.com/commerce), then/mcp→ Authenticate.
Local folders (the create CLI)
The remote servers take files, an uploaded tarball or a Git repository. To let a coding agent push the folder it is working in — building on your machine when needed — run the CLI's local MCP server instead:
claude mcp add create -- npx -y @create.com/cli mcp --local-builds # Claude Code
codex mcp add create -- npx -y @create.com/cli mcp --local-builds # CodexThen ask: "push this to Create". Sign in once with npx @create.com/cli login.
ChatGPT
Settings → Apps & Connectors → Advanced → Developer mode on → Create app → paste the URL, authentication OAuth.
Grok (grok.com)
grok.com/connectors → New Connector → Custom → paste the URL → sign in to Create when asked. (Grok Business/Enterprise: a team admin adds it first in console.x.ai → Grok Business → Connectors.)
Mistral Le Chat
Intelligence → Connectors → Add Connector → Custom MCP Connector → paste the URL → Connect (OAuth).
Perplexity (Pro, Max, Enterprise)
Settings → Connectors → Add custom connector → name Create, the URL, transport Streamable HTTP, authentication OAuth.
Microsoft Copilot Studio
Your agent → Tools → Add a tool → New tool → Model Context Protocol → server name Create, the URL, authentication OAuth 2.0 → Dynamic discovery.
Config files (everything else)
Most clients take the same shape; only the key names differ.
// Cursor ~/.cursor/mcp.json · Claude Desktop (via connectors) · LM Studio mcp.json · JetBrains AI Assistant
{ "mcpServers": { "create": { "url": "https://mcp.create.com/apps" } } }
// VS Code .vscode/mcp.json
{ "servers": { "create": { "type": "http", "url": "https://mcp.create.com/apps" } } }
// Windsurf ~/.codeium/windsurf/mcp_config.json
{ "mcpServers": { "create": { "serverUrl": "https://mcp.create.com/apps" } } }
// Kiro .kiro/settings/mcp.json · Amazon Q Developer CLI
{ "mcpServers": { "create": { "type": "http", "url": "https://mcp.create.com/apps" } } }
// Zed settings.json
{ "context_servers": { "create": { "url": "https://mcp.create.com/apps" } } }
// Cline cline_mcp_settings.json
{ "mcpServers": { "create": { "type": "streamableHttp", "url": "https://mcp.create.com/apps" } } }
// Gemini CLI ~/.gemini/settings.json
{ "mcpServers": { "create": { "httpUrl": "https://mcp.create.com/apps" } } }# Continue (.continue/mcpServers/create.yaml)
name: Create
version: 0.1.0
schema: v1
mcpServers:
- name: Create
type: streamable-http
url: https://mcp.create.com/appsOpen WebUI (0.6.31+): Admin Settings → Integrations → External Tool Servers → + Add Connection → type MCP (Streamable HTTP) → the URL → auth OAuth 2.1.
Warp: Settings → AI → MCP servers → + Add → paste
{ "create": { "url": "https://mcp.create.com/apps" } }.Ollama / Jan / other local model apps: use them through a client above that speaks MCP (Open WebUI or LM Studio work with local models).
Clients without OAuth (commerce only)
Make a personal access token in your Create store under Settings → API access, tick only what it needs, and send it as a header:
{ "mcpServers": { "create-commerce": { "url": "https://mcp.create.com/commerce", "headers": { "Authorization": "Bearer crk_…" } } } }Treat the token like a password; revoke it in the same place.
Related MCP server: Replit MCP Server
What it will and won't do
Your permissions are the limit. Each call uses your connection's permissions; a staff member's connection cannot do owner-only things.
It asks before big changes. Every tool is annotated read-only, write, or destructive (deletes, publishes, production deploys, shopper emails, paid resources) so your assistant can confirm with you.
No money moves through the commerce server's default tool set: refunds, cancellations, payouts, gift cards and shipping labels stay in your Create dashboard.
Secrets stay secret. Secret values, API token values, card data and passwords are never returned.
Shopper text is data. Order notes and messages are returned marked as untrusted data.
Disconnect any time: Settings → Connected apps (store) · Account → Apps → Access (hosting).
Links
Docs: https://docs.create.com/docs/apps/mcp.md · https://docs.create.com/docs/commerce/mcp.md
Privacy policy: https://www.create.com/policies/privacy-policy
Terms of service: https://www.create.com/policies/terms-of-service
Data processing addendum: https://www.create.com/policies/data-processing-addendum
Support: support@create.com
This server cannot be deployed
Maintenance
Related MCP Connectors
Deploy your project to a live HTTPS URL from your AI tool; read logs, set variables, resize apps.
Deploy and manage Jade Hosting projects from AI clients. Jade account and OAuth required.
Deploy and manage your apps, databases, storage, and scheduled jobs from your AI agent
Build, validate, deploy — HTTP APIs, cron jobs, webhooks and MCP tools — from your AI client.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to manage Dokploy deployments, including creating and deploying applications, managing databases, configuring domains with SSL, and monitoring application status through a standardized interface.20 npmMIT
- FlicenseBqualityDmaintenanceEnables AI assistants to interact with Replit workspaces directly, including managing repls, file operations, environment variables, and deployments without constant user intervention.244-
- AlicenseAqualityDmaintenanceEnables AI systems like Claude and Cursor to directly manage Railway projects, deployments, services, environment variables, and monitor logs through natural language commands.98 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to build, deploy, and inspect apps through a hosted backend service, including reading platform docs, deploying raw source, inspecting logs, verifying live pages in browsers, and managing project tasks.MIT