Xano

You can run an MCP server to interact with Xano’s metadata API, giving you programmable control over tables, schemas, and API documentation from your preferred MCP client. This enables AI assistants and automation to manage your Xano workspace efficiently.

How to use

You connect to the Xano MCP Server from an MCP client (such as Cursor or Claude Desktop) and then issue high-level actions like listing tables, editing schemas, and generating API documentation. The server exposes tools to manage your workspace programmatically, so you can automate common backend tasks without switching to the Xano UI. Start by configuring a local MCP client to communicate with the server, then use the available tools to perform the actions you need.

How to install

Prerequisites: Node.js v16 or higher, npm or another Node.js package manager, a Xano account with API access, and an MCP client such as Cursor or Claude Desktop.

Step 1: Clone the project and enter the directory.

git clone https://github.com/lowcodelocky2/xano-mcp.git
cd xano-mcp

Step 2: Install dependencies.

npm install

Step 3: Configure your Xano credentials. Create or edit the configuration to include your API key, workspace, and base API URL.

XANO_API_KEY=your_xano_api_key
XANO_WORKSPACE=your_workspace_id
XANO_API_BASE=https://your-instance.xano.io/api:meta

Step 4: Build the project.

npm run build

Step 5: Start the MCP server using your MCP client of choice. The canonical way shown here is to run the local build via Node.

{
  "mcpServers": {
    "xano": {
      "command": "node",
      "args": [
        "/path/to/xano-mcp/build/index.js"
      ]
    }
  }
}

Additional setup notes

If you prefer to reference the build path from your current directory, ensure the path in the command points to the built entry file, typically under build/index.js.

Configuration and usage notes

The MCP server exposes tools for database management, schema operations, API management, and documentation generation. You can use these tools to create, list, modify, and delete tables; edit schemas; manage API groups and endpoints; and generate Swagger or Markdown specifications for API groups.

Security considerations

Securely store your Xano API key and workspace identifiers. Use environment variables or a secrets manager in production. Do not expose credentials in logs or client configurations.

Troubleshooting tips

If the MCP server does not start, verify that Node.js is available, dependencies are installed, and the index.js build file exists at the expected path. Check that the Xano credentials are correctly set and that your MCP client is configured to reach the local server.

Available tools

list-tables

List all tables in your Xano workspace to understand current structure.

view-table

View detailed schema information for a specific table.

create-table

Create a new table with a custom schema.

delete-table

Delete an existing table from the workspace.

edit-schema

Modify an existing table schema, including adding or renaming columns.

add-column

Add new columns with various data types to a table.

remove-column

Remove columns from a table.

rename-column

Rename an existing column in a table.

update-schema

Update an entire table schema with complex types and relationships.

create-api-group

Create a new API group for organizing endpoints.

list-api-groups

List all API groups in the workspace.

browse-apis

Browse APIs within a group to inspect endpoints and metadata.

toggle-swagger

Enable or disable Swagger documentation for API groups.

manage-api-metadata

Add or update metadata such as tags and descriptions for APIs and groups.

add-api

Add new APIs to a group with configurable HTTP methods and docs.

configure-http-methods

Set up HTTP methods (GET, POST, PUT, DELETE, PATCH, HEAD) for APIs.

generate-api-spec

Generate API specifications in Markdown or JSON formats for documentation.