Deploy from Claude Code or Cursor.The developer never leaves their AI IDE.

What this is

Varity ships an MCP server. MCP (Model Context Protocol) lets your AI coding tool call external tools on your behalf. Once the Varity MCP server is installed in Claude Code or Cursor, your AI assistant can deploy, check deployment status, view logs, and manage your app without you leaving the editor.

The conversation goes like this:

You: Deploy this app with Varity

Claude Code (calling varity_deploy):
  Detecting framework: Next.js
  Configuring auth...done
  Configuring database...done
  Deploying...

  Live at https://varity.app/my-app/

The developer never switches windows. The app goes from working locally to live in production in the same session where it was built.

Setup takes about two minutes

There are two steps: get your Varity API key and add the MCP server to your editor config.

Step 1: Get your API key

Create a free account at developer.store.varity.so. Your API key is in the settings page under API Keys.

Step 2: Add the Varity MCP server

For Claude Code, add this to your .claude/settings.json:

{
  "mcpServers": {
    "varity": {
      "command": "npx",
      "args": ["-y", "@varity-labs/mcp"],
      "env": {
        "VARITY_API_KEY": "your-api-key-here"
      }
    }
  }
}

For Cursor, add the same config to your Cursor MCP settings (Settings > MCP > Add Server).

Restart your editor. The Varity tools are now available inside your AI assistant.

What you can do from inside your editor

Once the MCP server is installed, your AI assistant can run any Varity operation. Here are the most common ones:

What gets auto-configured

When you say "deploy this with Varity," the MCP server does not just copy your files to a server. It runs Varity's orchestration algorithm, which detects what your app needs and configures the whole stack automatically.

You do not write any of this config. The algorithm reads your code, picks the right services, and wires everything together.

Why this matters for AI-assisted development

The non-technical developer using Claude Code or Cursor has a different workflow than a career engineer. They write code by describing what they want. They debug by asking questions. They ship by asking their AI tool to ship it.

Every context switch kills momentum. If deploying requires a browser, a dashboard, and a set of commands the AI tool did not help write, the developer either skips deploying or spends an hour figuring it out.

The Varity MCP server closes that gap. Build, test, and deploy all happen inside the same window, in the same conversation. The developer never has to leave.

"AI gives you the power to build. Varity gives you the power to ship."

Supported AI editors

• +Claude Code (Anthropic)
• +Cursor
• +Windsurf
• +Any editor that supports the Model Context Protocol