opencode

Prerequisites

Node.js 18 or later
opencode installed

If you don’t have opencode yet:

Installation

Install the MCP Server

You can add the Xano Developer MCP with opencode’s interactive CLI, or by editing your config file directly.

Option 1: Interactive CLI

Run the guided add command, which walks you through adding a local or remote MCP server: When prompted, enter:

Name: xano
Type: Local
Command: npx -y @xano/developer-mcp

opencode writes the server into your config for you.

Option 2: Edit the config file

opencode is configured through JSON. Add the Xano Developer MCP as a local MCP server in your opencode config file at ~/.config/opencode/opencode.json:

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "xano": {
      "type": "local",
      "command": ["npx", "-y", "@xano/developer-mcp"],
      "enabled": true
    }
  }
}

To scope the server to a single project instead of all projects, put the same mcp block in an opencode.json file at your project root. When opencode starts, it looks for a config file in the current directory and traverses up to the nearest Git directory, and project config overrides your global defaults. Restart any active opencode sessions so the new server is picked up.

Verify Setup

In opencode, ask:

“What version of the Xano Developer MCP is installed?”

opencode should call mcp_version and return the current version number.

Usage

The Developer MCP lets opencode write and validate XanoScript using your local Xano workspace as context. Before asking opencode to make changes, pull a workspace locally with the Xano CLI. If you haven’t installed and authenticated with the CLI yet, do that now before continuing. Then select or create a workspace and run:

xano workspace pull

Once your workspace is available locally, you can ask opencode to help with XanoScript tasks, from building a complete workspace:

Create a small backend for advisor client intake. It should include a `clients` table with fields for name, email, phone, risk tolerance, investment objective, and advisor notes. Add API endpoints to create a client, list clients, get a single client by ID, and update client details. Include validation for required fields and valid risk tolerance values.

Show See the result

opencode creates a small advisor client intake backend for storing and managing client profile details.The generated backend includes a clients table with fields for the client’s name, email, phone number, risk tolerance, investment objective, advisor notes, and timestamps. The email field is stored as a unique value, so duplicate client records cannot be created with the same email address.It also adds a clients API group with endpoints to:

Create a new client
List clients with pagination and sorting
Get a single client by ID
Update an existing client

The generated XanoScript includes validation for required fields, supported risk tolerance values, duplicate email addresses, and missing client records. Before pushing the changes, opencode validates the generated XanoScript with the Developer MCP and fixes any issues it finds.You can download the complete backend for further review.

You can also ask it to expand or iterate on existing backends.

Add a follow-up task feature to the advisor client intake backend. Create a `client_tasks` table linked to clients, with fields for task title, due date, status, and notes. Add API endpoints to create a task for a client, list all tasks for a client, and mark a task as complete.

Show See the result

opencode extends the advisor client intake backend with a follow-up task feature for managing next steps after a client profile is created.The updated backend keeps the existing clients table and API endpoints for creating, listing, retrieving, and updating client records. It also adds a new client_tasks table linked to the clients table, so each task belongs to a specific client.The client_tasks table includes fields for the related client, task title, due date, status, notes, and timestamps. Task status supports values like pending, in_progress, and completed, making it possible to track where each follow-up task stands.The backend also adds new API endpoints to:

Create a follow-up task for a client
List all follow-up tasks for a client
Mark a follow-up task as complete

The generated XanoScript includes checks for missing clients, missing task titles, valid task statuses, and missing task records. Before pushing the changes, opencode validates the updated XanoScript with the Developer MCP and fixes any issues it finds.

Once you’re ready, push the changes to your sandbox so you can review them in the browser before promoting to your live workspace: xano sandbox review opens your sandbox in the browser — verify everything looks right, then promote the changes to production from there.

Getting Started

Clients

Reference

Prerequisites

Installation

Install the MCP Server

Option 1: Interactive CLI

Option 2: Edit the config file

Verify Setup

Usage

What’s Next

Tools Reference

Resources & Library

​Prerequisites

​Installation

​Install the MCP Server

​Option 1: Interactive CLI

​Option 2: Edit the config file

​Verify Setup

​Usage

​What’s Next

Tools Reference

Resources & Library

Prerequisites

Installation

Install the MCP Server

Option 1: Interactive CLI

Option 2: Edit the config file

Verify Setup

Usage

What’s Next