Skip to content

varity-labs/varity

v1.0.1MIT

Deploy apps and AI agents to production from your AI editor, with the cost shown before you deploy.

Varity plugin

Deploy apps and AI agents to production from your AI editor, with the cost shown before you deploy.

Varity is the Orchestration Cloud: one place to run applications, AI agents, and virtual machines. Traffic alone does not change an app's monthly price. This plugin connects your AI coding agent to Varity through the Varity MCP server and adds a deploy-with-varity skill that walks the agent through checking the setup, showing the cost, deploying, and sharing the live URL.

What's included

PartWhat it does
mcp.json, .mcp.json, gemini-extension.jsonStart the Varity MCP server (npx -y @varity-labs/mcp@2.3.27) with 26 tools: deploys, status, logs, open-source app and AI agent templates, CPU virtual machines, and cost estimates
skills/deploy-with-varityTells the agent when and how to deploy with Varity
plugin.json, .claude-plugin, .cursor-pluginPlugin manifests: plugin.json for Agent Plugins clients such as Codex, GitHub Copilot CLI, VS Code and Kiro, .claude-plugin for Claude Code, .cursor-plugin for Cursor

Install

Claude Code

claude plugin marketplace add varity-labs/varity-plugin
claude plugin install varity@varity-plugin

Gemini CLI

gemini extensions install https://github.com/varity-labs/varity-plugin

Cursor, Codex, GitHub Copilot CLI, VS Code and Kiro: these clients load Agent Plugins, which use the root plugin.json and mcp.json; Cursor also has its own manifest in .cursor-plugin/plugin.json. Add the plugin from the client's plugin settings with the repository URL https://github.com/varity-labs/varity-plugin. In Kiro, open the Powers panel, choose Add Custom Power, then Import power from GitHub.

Skill only: add the deploy-with-varity skill to any agent that reads Agent Skills.

npx skills add varity-labs/varity-plugin --skill deploy-with-varity

The skill needs the Varity MCP server: install the plugin, or add the server to your MCP config as shown below, and set VARITY_DEPLOY_KEY.

Any MCP client: add the server directly.

{
  "mcpServers": {
    "varity": {
      "command": "npx",
      "args": ["-y", "@varity-labs/mcp@2.3.27"],
      "env": { "VARITY_DEPLOY_KEY": "<your deploy key>" }
    }
  }
}

Requirements

  • Node.js 22.11 or later
  • A Varity account and a deploy key from the developer portal. Set it as VARITY_DEPLOY_KEY in the MCP config (env) or in the shell that launches your editor or agent, then restart the editor or agent; or sign in with the Varity CLI. When more than one is set, the server uses VARITY_DEPLOY_KEY first, then the CLI sign-in, then the legacy VARITY_API_KEY. Never paste the key into the chat.
  • The Varity CLI (pipx install varitykit) only for varity_migrate, and optionally to sign in

Data handling

  • Personal data: the plugin stores no personal data. The MCP server reads your Varity deploy key from VARITY_DEPLOY_KEY (or VARITY_API_KEY) or the Varity CLI sign-in file and sends it only to the Varity API.
  • What is sent where:
    • The Varity API at https://varity.app receives deploy, status, logs, pricing and balance requests.
    • Docs search reads https://docs.varity.so.
    • Build, dev server, dependency install and browser tools run on your machine.
    • varity_create_repo uses your own GitHub credentials against GitHub.
    • varity_migrate clones the GitHub repository you name into a temporary directory.
    • varity_deploy_status sends one HTTP request to each listed app's own URL to check that it responds.
    • The MCP server sends no telemetry unless you set the OpenTelemetry OTEL_EXPORTER_OTLP_* variables or BETTERSTACK_MCP_DSN yourself.
  • Retention: see the Varity privacy policy.
  • Intended users: not intended for people under 18.

Links

License

MIT