Xano Developer MCP
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| xano_validate_xanoscriptA | Validate XanoScript code for syntax errors. Supports multiple input methods:
Returns errors with line/column positions and helpful suggestions for common mistakes. The language server auto-detects the object type from the code syntax. |
| xano_xanoscript_docsA | Get XanoScript programming language documentation for AI code generation. Call without parameters for a compact index of all topics (~4KB, ~1K tokens); then drill in with topic= or file_path=. Use topic='readme' for the full prose overview (previously the no-arg default). For context-limited models: use tier='survival' (~1.2K tokens) or tier='working' (~4.5K tokens). Use 'topic' for specific documentation, or 'file_path' for context-aware docs based on the file you're editing. Use mode='quick_reference' for compact syntax reference (recommended for context efficiency). Use max_tokens to limit documentation size to fit your context budget. file_path mode defaults to 'quick_reference' to reduce context size; use mode='full' to get complete docs. |
| xano_versionA | Get the current version of the Xano Developer MCP server. Returns the version string from package.json. |
| xano_meta_api_docsA | Get documentation for Xano's Meta API. Use this to understand how to programmatically manage Xano workspaces, databases, APIs, functions, agents, and more. Topics
Usage
|
| xano_cli_docsA | Get documentation for the Xano CLI. Use this to understand how to use the CLI for local development, code sync, and XanoScript execution. Topics
Usage
|
| xano_knowledge_listA | Get the CLI command to list a Xano workspace's knowledge base: skills, docs, and the agents.md file. This tool does not run the command itself — it returns the exact Use this to get an overview of what knowledge/skills exist before answering questions about workspace conventions, or before deciding whether a new skill/doc needs to be created (to avoid duplicating existing ones). Always-on items (mode=always) are returned by the command with full content; on-demand items are returned with just name+description — use xano_knowledge_get to get the command for fetching an on-demand item's full content when it becomes relevant. |
| xano_knowledge_getA | Get the CLI command to fetch the full content of one named knowledge item (a skill, doc, or agents.md), or one of a skill's attached reference files. This tool does not run the command itself — it returns the exact Use this after xano_knowledge_list has identified an on-demand item whose full content is now needed, or when a skill's step tells you to consult a specific reference file (via @filename syntax in the skill content). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| survival | Minimal syntax survival kit for writing valid XanoScript |
| working | Complete working reference for common XanoScript tasks |
| readme | XanoScript overview, workspace structure, and quick reference |
| essentials | Common patterns, quick reference, and common mistakes to avoid |
| syntax | Expressions, operators, and filters for all XanoScript code |
| syntax/string-filters | String filters, regex, encoding, security filters, text functions |
| syntax/array-filters | Array filters, expression-based higher-order filters (map/filter/reduce), JS lambda filters (lambda_map/lambda_reduce), and array functions |
| syntax/functions | Math filters/functions, object functions, bitwise operations |
| types | Data types, input blocks, and validation |
| tables | Database schema definitions with indexes and relationships |
| functions | Reusable function stacks with inputs and responses |
| apis | HTTP endpoint definitions with authentication and CRUD patterns |
| tasks | Scheduled and cron jobs |
| triggers | Event-driven handlers (table, realtime, workspace, agent, MCP) |
| database | All db.* operations: query, get, add, edit, patch, delete |
| agents | AI agent configuration with LLM providers and tools |
| tools | AI tools for agents and MCP servers |
| mcp-servers | MCP server definitions exposing tools |
| unit-testing | Unit tests, mocks, and assertions within functions, APIs, and middleware |
| workflow-tests | End-to-end workflow tests with data source selection and tags |
| integrations | External service integrations index - see sub-topics for details |
| integrations/cloud-storage | AWS S3, Azure Blob, and GCP Storage operations (external buckets, not native Xano storage) |
| integrations/search | Elasticsearch, OpenSearch, and Algolia search operations |
| integrations/redis | Redis caching, rate limiting, and queue operations |
| integrations/external-apis | HTTP requests with api.request patterns |
| integrations/utilities | Local storage, email, zip, and Lambda utilities |
| file-uploads | Uploading files to native Xano storage: file? input, create_attachment, sign_private_url |
| frontend | Static frontend development and deployment (static hosting) |
| addons | Reusable subqueries for fetching related data |
| debugging | Logging, inspecting, and debugging XanoScript execution |
| performance | Performance optimization best practices |
| realtime | Real-time channels and events for push updates |
| security | Security best practices for authentication and authorization |
| streaming | Streaming data from files, requests, and responses |
| middleware | Request/response interceptors for functions, queries, tasks, and tools |
| branch | Branch-level settings: middleware, history retention, visual styling |
| workspace | Workspace-level settings: environment variables, preferences, realtime |
TDQS
Scored across 7 tools
Each tool has a clearly distinct purpose: CLI docs, knowledge retrieval (list vs get), Meta API docs, XanoScript validation, version info, and XanoScript language docs. No overlapping functionalities.
All tools share the 'xano_' prefix but the naming pattern is inconsistent: some use noun_verb (knowledge_get, knowledge_list), others noun_noun (cli_docs, meta_api_docs, xanoscript_docs), one verb_noun (validate_xanoscript), and one simple noun (version).
With 7 tools, the count is well-scoped for a developer-focused MCP server. Each tool provides essential functionality without being overwhelming or too sparse.
The tool set covers documentation, knowledge management, code validation, and version info, but lacks tools for executing CLI commands or performing actual workspace operations, which may require agent workarounds.