Skip to content

Deploy from Claude Code, Cursor, or Windsurf

Varity Team Core Contributors Updated June 2026

Varity works seamlessly with AI coding tools. Install the MCP server once, and your AI editor can build and deploy apps to production without you ever leaving the chat.

Works with Claude Code, Cursor, Windsurf, VS Code (Copilot), and any other editor that supports the Model Context Protocol.

Run this once from any directory:

Terminal window
claude mcp add varity -- npx -y @varity-labs/mcp

Claude Code picks up the server automatically on the next conversation. Confirm it is registered:

Terminal window
claude mcp list

You should see varity in the list.

Once the MCP server is installed, type this in your AI editor:

Deploy this project to Varity

Your AI editor calls varity_build and varity_deploy in sequence and returns the live URL.

For a brand new project, ask your AI editor to build the app first, then deploy it:

Build a Next.js app called my-app with a dashboard, install dependencies, then deploy it to production

Your AI editor writes the app code, then the Varity tools handle dependency installation, the production build, and the deploy. You get a live URL when it is done.

These prompts are tested and work out of the box in Claude Code, Cursor, and Windsurf.

Check environment

Check if my environment is ready for Varity

Build a new app

Build a Next.js app called my-project with a dashboard, install dependencies, start the dev server, and open it in my browser

Deploy to production

Build my project and deploy it to Varity. Show me the live URL when done.

Check status

Show me the status of my Varity deployments

Debug a failed deploy

Show me the build logs for my last Varity deployment

Estimate cost

How much would it cost to host this app with 1000 monthly users on Varity?

Full build-to-deploy flow

Check my Varity environment, then build this project, deploy it, and open the live URL in my browser

The Varity MCP server gives your AI editor a full set of tools. Here are the most useful ones for the build-to-deploy workflow:

ToolWhat to ask your AI
varity_doctor”Check if my environment is set up for Varity”
varity_login”Log in to Varity”
varity_search_docs”Search the Varity docs for Docker image deploys”
varity_install_deps”Install dependencies for this project”
varity_dev_server”Start the dev server and open it in my browser”
varity_open_browser”Open the deployed app in my browser”
varity_build”Build this project for production”
varity_create_repo”Create a GitHub repo and push this project”
varity_deploy”Deploy this to Varity”
varity_deploy_status”Show me my deployment status”
varity_deploy_logs”Show me the build logs”
varity_set_env”Set environment variables on this app”
varity_redeploy”Redeploy this app in place”
varity_delete_deployment”Tear down this deployment”
varity_migrate”Migrate my Vercel app to Varity”
varity_cost_calculator”How much will this cost at 500 users?”
varity_list_templates”What templates can Varity deploy?”
varity_template_info”What does the Agent Zero template need?”
varity_deploy_template”Deploy Agent Zero with these environment variables”
varity_list_agents”What agent templates can Varity deploy?”
varity_agent_info”What does the Agent Zero template need?”
varity_deploy_agent”Deploy Agent Zero”

Full reference at MCP Server Spec.

For Claude Code, add this to your project’s CLAUDE.md:

## Deployment
This project deploys to Varity. Use the Varity MCP server tools:
- Deploy: ask "Deploy this project to Varity"
- Check status: ask "Show me my Varity deployment status"
- Logs: ask "Show me the build logs for my last deployment"

For Cursor, save this as .cursor/rules/varity.mdc:

When the user asks to deploy, use the Varity MCP varity_deploy tool.
When the user asks to check deployment status, use varity_deploy_status.
When the user asks to see logs, use varity_deploy_logs.

This tells your AI editor to route deploy-related requests to the Varity tools automatically.

Here is a complete session from idea to live app, using only your AI editor:

  1. Check your setup

    Check if my environment is ready for Varity

    The AI runs varity_doctor and tells you if anything needs fixing.

  2. Build the app

    Build a Next.js app called task-tracker. I want a dashboard where users can create and manage tasks.

    Your AI editor writes the project code: a Next.js app with a dashboard for creating and managing tasks.

  3. Install dependencies

    Install dependencies and start the dev server

    The AI runs varity_install_deps and varity_dev_server, then opens localhost:3000.

  4. Build the feature

    Work with your AI editor to build the task feature:

    Add a tasks data model with title (string), status (string), and dueDate (string) fields. Include a dashboard page with a list and a create form.
  5. Deploy to production

    Build and deploy this to Varity

    The AI calls varity_build and varity_deploy. Your app is live in about 60 seconds.

  6. Share the link

    Show me the live URL for my deployment

    Done. Send it to anyone.

If you already have a Vercel app, one prompt migrates it to Varity:

Migrate my Vercel app at https://github.com/your-org/your-app to Varity

The AI calls varity_migrate, which clones the repository, removes Vercel-specific configuration, and deploys to Varity infrastructure. See Migrate from Vercel for details.

Browser-based AI tools (Claude.ai, ChatGPT)

Section titled “Browser-based AI tools (Claude.ai, ChatGPT)”

If you use a browser-based AI tool instead of a desktop editor, connect to the hosted MCP endpoint:

https://mcp.varity.so

Claude.ai: Settings > Connectors > Add MCP Server > URL: https://mcp.varity.so

ChatGPT: Settings > Connectors > Create > MCP server URL: https://mcp.varity.so

The first connection asks you to authenticate via the Varity login page.

“varity not found” in your AI editor

Re-add the server and restart:

Terminal window
# Claude Code
claude mcp add varity -- npx -y @varity-labs/mcp

Verify with claude mcp list.

Deploy fails with “varitykit not found”

Terminal window
pipx install varitykit

Then ask your AI to try again.

Cursor does not show the Varity tools

Check that .cursor/mcp.json is valid JSON, then restart Cursor. Cursor requires a full restart (not just reload) to pick up MCP config changes.

Server is registered but tools are not being called

Ask your AI directly:

Use the varity_doctor tool to check my environment

If the AI is not picking up the tools automatically, being explicit about the tool name always works.

See MCP Server Spec for the full troubleshooting section.