Deploy Your MCP Server

This is the payoff. You click deploy, and your MCP server goes live on mctx's global infrastructure. No payout account required, no mandatory payment setup — just your code.

Before you deploy

Make sure you have completed these steps:

• Connected your GitHub repository
• Added your MCP server (repository selected, branch and path configured)

Your MCP server detail page tracks this for you. If the status shows setup_required, finish the GitHub connection first:

• Connect GitHub -- link your GitHub account and install the mctx GitHub App (~2 minutes)

Once the GitHub connection is complete, your MCP server status changes to ready.

Payout setup is not required to deploy. You can set up payouts later, from your MCP server's detail page.

Step 1: Click deploy

Once your server status is ready:

1. Click Deploy Server
2. Confirm the deployment

That is it. mctx takes it from here.

What happens during deployment

Behind the scenes, mctx:

1. Pulls your code from the branch you configured
2. Validates the entry point -- confirms your JavaScript file exists and is valid
3. Deploys to the edge -- creates a worker on Cloudflare's global network
4. Sets up your subdomain -- {slug}.mctx.ai starts routing to your server
5. Runs a health check -- verifies your server responds correctly

Typical time: 1-3 minutes. You get an in-app notification when it finishes.

Step 2: Verify it works

Once the status changes to live, check that everything is working.

Visit your MCP server's public page:

Go to mctx.ai/apps/{slug} in your browser. This is the page subscribers see. It shows your MCP server name, description, available tools, and a subscribe button.

Test the MCP endpoint:

Your MCP server is live. Share the versionless URL with subscribers — it always connects to your latest deployed version:

https://{slug}.mctx.ai

For example, if your slug is weather-api:

https://weather-api.mctx.ai

Subscribers who need to pin to a specific version can use:

https://weather-api.mctx.ai/v1.0.0

Check real-time logs:

Open the logs modal from your server detail page and make a test request. You will see console.log, console.warn, and console.error output in real time. Logs are ephemeral -- they only appear while the modal is open. See Server Logs for details.

If deployment fails

Deployment issues are almost always one of these things.

"File specified in main not found in repository"

The file in your package.json main field does not exist in the repo. Make sure it is built and committed. mctx does not run build commands — you commit the built file, similar to GitHub Actions JavaScript actions. If you are using a release branch pattern, confirm the mctx dashboard is set to deploy from your release branch, not main.

Still stuck? Check the Last Deployment Error section on your server detail page for the full error message. If that does not help, see the FAQ.

After deployment

Your MCP server is live. Your detail page shows a checklist to help you get the most from it:

Publish to MCP Community Registry -- One click. Your MCP server appears in the registry within minutes. See Publish to MCP Registry for details. If your repository belongs to a GitHub organization, your org membership must be set to public before publishing will succeed -- see Publishing org-owned servers.

Share your MCP server page -- Your public URL is https://mctx.ai/apps/{slug}. Share it on Twitter/X, Discord, Reddit, your GitHub README -- wherever developers hang out. See Your Vanity Link.

Enable monetization -- Optional. Charge subscribers for usage and keep 100% of what they pay. Requires payout setup first. See How Payouts Work.

Updating your MCP server

Bumping the version in package.json triggers a new deployment. mctx creates a new version endpoint (/v2.0.0 alongside /v1.0.0). Subscribers using the versionless URL automatically connect to the new version on their next session. Subscribers pinned to a specific version remain on that version until they update their configuration.

Pushing without a version change is a no-op — mctx detects that the version already exists and skips deployment. To trigger a new deployment, you must bump the version in package.json. See Versioning for details.

Next Steps

Your MCP server is live and accepting subscribers. Here is what to explore:

• Publish to MCP Registry -- Get discovered
• Environment Variables -- Add API keys and secrets
• Versioning -- Manage multiple versions
• Server Logs -- Debug with real-time logs
• How Payouts Work -- Optionally charge subscribers

See something wrong? Report it or suggest an improvement — your feedback helps make these docs better.