Skip to main content
Glama
xano-inc

Xano Developer MCP

Official
by xano-inc

xano_cli_docs

Read-onlyIdempotent

Get CLI documentation for installation, authentication, workspace management, function commands, and XanoScript execution to support local development and code sync.

Instructions

Get documentation for the Xano CLI. Use this to understand how to use the CLI for local development, code sync, and XanoScript execution.

Topics

  • auth: Xano CLI - Authentication

  • start: Xano CLI - Getting Started

  • profile: Xano CLI - Profile Management

  • workspace: Xano CLI - Workspace Operations

  • branch: Xano CLI - Branch Management

  • function: Xano CLI - Function Management

  • knowledge: Xano CLI - Knowledge & Skills

  • release: Xano CLI - Release Management

  • tenant: Xano CLI - Tenant Management

  • unit_test: Xano CLI - Unit Test Management

  • workflow_test: Xano CLI - Workflow Test Management

  • sandbox: Xano CLI - Sandbox Environment

  • platform: Xano CLI - Platform Management

  • static_host: Xano CLI - Static Hosting

  • update: Xano CLI - Update

  • integration: Xano CLI + Meta API Integration Guide

Usage

  • Start with "start" topic for installation and setup

  • Use "auth" or "profile" to understand authentication options

  • Use "integration" to understand when to use CLI vs Meta API

  • Use specific topics for command reference (workspace, sandbox, branch, release, tenant, function, etc.)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
topicYesDocumentation topic to retrieve. Start with 'start' for installation and setup. Example: topic='function' for function management commands, topic='sandbox' for the personal dev environment.
detail_levelNoLevel of detail to return. 'overview' = brief summary of commands and their purpose. 'detailed' = full command reference with flags and arguments. 'examples' = includes usage examples for each command. Default: 'detailed'.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
documentationYesThe CLI documentation content for the requested topic.
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already indicate read-only, idempotent, non-destructive behavior. Description adds value by listing topics and usage guidelines, which helps the agent understand the scope of documentation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Concise with clear sections (Topics, Usage). Every sentence is informative, no filler. Front-loaded with purpose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given simple input schema (2 params, both enums) and presence of output schema, description combined with schema fully covers what the agent needs to use the tool effectively. Usage guidelines are comprehensive.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with enums and descriptions. Description complements by explaining topic categories and recommended starting points, adding practical usage context beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description clearly states 'Get documentation for the Xano CLI.' It lists 16 topics and includes usage guidance. Differentiates from sibling tools like xano_meta_api_docs by mentioning when to use CLI vs Meta API.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit 'Usage' section advises to start with 'start' topic, use 'auth' or 'profile' for authentication, and use 'integration' to compare CLI vs Meta API. Provides clear when-to-use guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/xano-inc/xano-developer-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server