XanoScript VS Code Extension Deprecation

What’s happening?

The XanoScript VS Code Extension is being deprecated, in favor of the more recent XanoScript Language Server extension paired with the Xano Developer MCP and CLI.

Why?

The Developer MCP provides a much more robust XanoScript writing and validation experience, and the CLI enables more reliable push/pull capabilities with sandbox environments for review.

I’m still using the old extension

That’s okay! It’s easy to move over to the new workflow.

Try this prompt

Paste this into your AI coding agent and it will handle the setup for you:

Access Xano's Get Started prompt at https://go.xano.co/start-xano-skill. It will walk us through installing the Xano Developer Tools and the Xano development workflow.

Or follow the instructions below

Uninstall the old XanoScript extension

Install the new XanoScript Language Server extension

Get the VS Code extension from the Marketplace here. Using Cursor, Windsurf, or another OpenVSX-based IDE? Install it from OpenVSX here.

Install the Xano CLI

The CLI allows you or your AI agents to push/pull XanoScript code from your workspaces.

npm install -g @xano/cli

then

xano auth

There are additional steps if you’re running in a non-standard environment, such as our self-hosted users. More here

Enable the Developer MCP

The Developer MCP is necessary to ensure your agent can write and validate XanoScript properly. Pick your client below for the quick setup, or see the full client guides for step-by-step walkthroughs.

claude mcp add xano -- npx -y @xano/developer-mcp

Add --scope user to make it available across every project. Restart any active sessions. Full guide →

codex mcp add xano -- npx -y @xano/developer-mcp

Restart any active Codex sessions so the new server is picked up. Full guide →

Manage MCP servers from Cursor’s Customize page, or edit ~/.cursor/mcp.json (global) or .cursor/mcp.json (project root) directly:

{
  "mcpServers": {
    "xano": {
      "command": "npx",
      "args": ["-y", "@xano/developer-mcp"]
    }
  }
}

Save and restart Cursor. Full guide →

Open the Command Palette (⌘ / Ctrl + Shift + P), run MCP: Add Server, choose Command (stdio), and provide:

npx -y @xano/developer-mcp

Name it (e.g. Xano Developer MCP) and choose Workspace or Global scope. Full guide →

Edit ~/.codeium/windsurf/mcp_config.json:

{
  "mcpServers": {
    "xano": {
      "command": "npx",
      "args": ["-y", "@xano/developer-mcp"]
    }
  }
}

Save and restart Windsurf. Full guide →

Add to ~/.gemini/settings.json (or .gemini/settings.json in your project root to scope it to one project):

{
  "mcpServers": {
    "xano": {
      "command": "npx",
      "args": ["-y", "@xano/developer-mcp"]
    }
  }
}

Restart any active Gemini CLI sessions. Full guide →

Edit your config file — ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):

{
  "mcpServers": {
    "xano": {
      "command": "npx",
      "args": ["-y", "@xano/developer-mcp"]
    }
  }
}

Fully quit and restart Claude Desktop — reopening the window is not enough. Full guide →

To confirm it’s working, ask your agent: “What version of the Xano Developer MCP is installed?” It should call mcp_version and return the current version number.

How do I see my changes now?

The old extension’s diff view is gone, but the CLI diffs for you — you don’t have to set anything up to get it. Every push previews itself first. The CLI collects your local .xs files, compares them against your workspace, and shows you exactly what will change before applying anything: a per-type count of creates, updates, and deletes, then the individual operations, any destructive operations called out separately, and any objects that exist in Xano but not locally. Then it prompts for confirmation. To see that comparison without pushing, add --dry-run — it prints the full preview and exits:

xano workspace push -d ./my-workspace --dry-run

Add -v to see a reason line under each operation explaining why it was classified that way. The sandbox gives you a reviewable diff in the browser. Push to your sandbox — an isolated, ephemeral copy of your workspace — then open the review screen to inspect the diff against your workspace and promote it when you’re satisfied:

xano sandbox push -d ./my-workspace --review

Nothing reaches your live workspace until you promote it there.

On paid plans this is the default path — xano workspace push is blocked and prompts you to go through the sandbox first. You can bypass it by enabling Allow Direct Workspace Push in Xano → Workspace Settings.

Because your workspace is now plain files on disk, you can also put it under version control and get commit history and diffs on top of all this — see Working with Git.

Why the new workflow is better

The old extension tied XanoScript development to a single editor. The new workflow removes that limit and adds capabilities the extension never had:

Build from anywhere your agents run. You’re no longer confined to one VS Code-based IDE — work from your terminal, your IDE’s native AI assistant, or a coding agent right alongside your code.
Catch errors before they ship. The Developer MCP validates XanoScript as it’s written, so your agent fixes syntax and structural mistakes before they reach your workspace instead of after.
Safer, more complete sync. The CLI’s push/pull is more robust and fully-featured than the old extension’s, giving you clearer control over what moves between local and Xano.
A better editing experience. The XanoScript Language Server adds inline completion, syntax highlighting, and diagnostics — which every AI tool above reads from too.

What’s next

Developer MCP

Get oriented with the Developer MCP and how it fits into your workflow

Xano CLI

Install, authenticate, and pull a workspace to develop against locally

Client guides

Step-by-step setup walkthroughs for every supported editor and agent

Tools reference

Explore the tools the Developer MCP exposes to your AI agents

​What’s happening?

​Why?

​I’m still using the old extension

​Try this prompt

​Or follow the instructions below

​How do I see my changes now?

​Why the new workflow is better

​What’s next

Developer MCP

Xano CLI

Client guides

Tools reference

What’s happening?

Why?

I’m still using the old extension

Try this prompt

Or follow the instructions below

How do I see my changes now?

Why the new workflow is better

What’s next