> ## Documentation Index
> Fetch the complete documentation index at: https://docs.mcp-use.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Manufact Cloud

> Deploy your MCP server to Manufact Cloud with one command

Deploy your MCP server to **Manufact Cloud**, the recommended deployment platform for mcp-use servers. With a single command, you can deploy your server and get a production-ready URL.

## Prerequisites

**Manufact Cloud account**: Sign up at [mcp-use.com](https://mcp-use.com) or log in via CLI:

```bash theme={null}
mcp-use login
```

For non-interactive flows (web onboarding, agents), use a pre-approved device code:

```bash theme={null}
mcp-use login --device-code <CODE>
```

See the [CLI reference](/typescript/server/cli-reference#login---authenticate-with-manufact-cloud) for `--api-key` and `--org` options.

## Quick Deployment

Deploy your MCP server in one command:

```bash theme={null}
# Install the CLI (if you are using create-mcp-use-app this step is not needed)
npm install -g @mcp-use/cli

# Login to Manufact Cloud
mcp-use login

# Deploy your server
mcp-use deploy
```

That's it! Your server will be built and deployed automatically.

## Deploy Without GitHub

You do not need a GitHub repository to deploy. Use `--no-github` to upload your local project source directly — the platform creates a managed repo and runs the normal build pipeline:

```bash theme={null}
mcp-use deploy --no-github
```

This path:

* ✅ Works without a git remote or GitHub App installation
* ✅ Uploads your local files (not GitHub)
* ✅ Creates the server in the platform-managed org
* ✅ Supports redeploys — linked projects auto-detect the upload path, so `--no-github` is only needed on the first deploy

You can later connect your own GitHub repository from the server dashboard ("Connect your GitHub") if you want push-to-deploy.

<Tip>
  Web onboarding uses `mcp-use login --device-code` followed by `mcp-use deploy --no-github -y` for a fully non-interactive first deploy.
</Tip>

## GitHub Repository Deployment

If your project is a GitHub repository, `mcp-use deploy` (without `--no-github`) automatically detects it and offers to deploy from GitHub:

```bash theme={null}
mcp-use deploy
```

You'll see:

```
GitHub repository detected:
  Repository: your-org/your-repo
  Branch:     main
  Commit:     abc1234

Deploy from GitHub repository your-org/your-repo? (y/n):
```

This approach:

* ✅ Deploys directly from your GitHub repository
* ✅ Automatically detects build and start commands
* ✅ Uses the latest commit from your branch
* ✅ Requires the mcp-use GitHub App on the repo and changes pushed to GitHub

## After Deployment

Once deployment completes, you'll receive:

### Deployment URLs

```
✓ Deployment successful!

🌐 MCP Server URL:
   https://your-deployment/id.deploy.mcp-use.com/mcp

🔍 Inspector URL:
   https://inspector.mcp-use.com/inspect?autoConnect=https://your-deployment/id.deploy.mcp-use.com/mcp
```

The `autoConnect` parameter and other Inspector URL options are documented in [Inspector URL parameters](/inspector/url-parameters).

#### Claude Desktop Configuration

```json theme={null}
{
  "mcpServers": {
    "my-server": {
      "url": "https://your-deployment/id.deploy.mcp-use.com/mcp"
    }
  }
}
```

### Test Locally First

Before deploying, test your server locally:

```bash theme={null}
# Build and test locally
mcp-use build
mcp-use start
```

## Next Steps

* [Deploying to Supabase](./supabase) - Alternative deployment option
* [Configuration Guide](../configuration) - Advanced server configuration
* [UI Widgets](../mcp-apps) - Building interactive widgets
* [CLI Reference](/typescript/server/cli-reference#deploy---cloud-deployment) - All deploy and login flags
* [API Reference](/typescript/server/index#mcpserver-api-reference) - Complete API documentation