Xano Developer MCP
OfficialThe Xano Developer MCP server provides AI assistants with tools for developing on the Xano backend platform, covering code validation, documentation, and workflow guidance.
Validate XanoScript Code: Check XanoScript for syntax errors using multiple input methods — raw code strings, single
.xsfiles, batch file arrays, or entire directories (with optional glob filtering). Returns detailed errors with line/column positions and suggestions.Access XanoScript Documentation: Retrieve context-aware, token-budget-aware docs covering 35+ topics including syntax, data types, database operations, APIs, agents, integrations (S3, Redis, Elasticsearch), security, realtime, and more. Supports full, quick-reference, or index modes, plus pre-packaged tiers (
survival~800 tokens,working~3500 tokens).Access Meta API Documentation: Get documentation for programmatically managing Xano resources — workspaces, API groups, endpoints, database tables, functions, tasks, agents, MCP servers, middleware, branches, and more. Configurable detail levels (overview, detailed, examples) with optional JSON schema inclusion.
Access CLI Documentation: Retrieve Xano CLI docs covering local development workflows, authentication, workspace sync, sandbox environments, branch management, releases, unit/workflow tests, and more. Includes an integration guide for CLI vs. Meta API usage.
Check Server Version: Get the current semantic version of the Xano Developer MCP server.
Pre-built Agent Skills: Leverage specialized skills like
xano-initfor guided project setup andxanoscript-docs-expertfor in-depth documentation reference.Direct Documentation Resource Access: Access XanoScript documentation topics directly via MCP resource URIs (e.g.,
xanoscript://docs/syntax).
Provides documentation and code validation for XanoScript, including integration guidance for Algolia search operations.
Provides documentation and code validation for XanoScript, including integration guidance for Elasticsearch search operations.
Provides documentation and code validation for XanoScript, including integration guidance for OpenSearch search operations.
Provides documentation and code validation for XanoScript, including integration guidance for Redis caching, rate limiting, and queue operations.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Xano Developer MCPGuide me through initial Xano workspace configuration."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
🚀 Xano Developer MCP
Supercharge your AI with the power of Xano
🤖 AI-Powered · 📚 Comprehensive Docs · ⚡ Instant Setup · 🔧 Built-in Tools
An MCP server and standalone library that gives AI assistants superpowers for developing on Xano — complete with documentation, code validation, and workflow guides. Use it as an MCP server or import the tools directly in your own applications.
💡 What's Xano? The fastest way to build a scalable backend for your app — no code required. Build APIs, manage databases, and deploy instantly.
🔗 Quick Links
Overview
This MCP server acts as a bridge between AI models and Xano's developer ecosystem, offering:
Meta API Documentation - Programmatically manage Xano workspaces, databases, APIs, functions, and more
CLI Documentation - Command-line interface for local development, code sync, and execution
XanoScript Documentation - Language reference with context-aware docs based on file type
Code Validation - Syntax checking with the official XanoScript language server
Workflow Guides - Step-by-step guides for common development tasks
Quick Start
Claude Code (Recommended)
claude mcp add xano -- npx -y @xano/developer-mcpThat's it! The MCP server will be automatically installed and configured.
Install via npm
You can also install the package globally from npm:
npm install -g @xano/developer-mcpThen add to Claude Code:
claude mcp add xano-developer -- xano-developer-mcpClaude Desktop
Add to your Claude Desktop configuration file:
macOS:
~/Library/Application Support/Claude/claude_desktop_config.jsonWindows:
%APPDATA%\Claude\claude_desktop_config.json
{
"mcpServers": {
"xano-developer": {
"command": "npx",
"args": ["-y", "@xano/developer-mcp"]
}
}
}Xano Skills
This repo ships two agent skills under skills/:
xano-init— guided setup that profiles a Xano workspace and builds a sandbox-first development playbookxanoscript-docs-expert— deep reference for working with XanoScript documentation and this MCP project's architecture
Using Claude Code inside this repo? You already have both skills. They're committed to .claude/skills/ and load automatically when Claude Code starts a session in this directory — no install step needed. Just invoke xano-init or xanoscript-docs-expert by name, or describe the task in natural language.
Using a different agent, or want the skills available in other projects? Skills are distributed via the open Agent Skills standard and install with a single npx command — no cloning or manual file copying.
Install xano-init globally into Claude Code:
npx skills add xano-inc/xano-developer-mcp -s xano-init -a claude-code -gInstall into multiple agents at once (Claude Code, Codex, Cursor, OpenCode, etc.):
npx skills add xano-inc/xano-developer-mcp -s xano-init \
-a claude-code -a codex -a cursor -a opencode -gDrop -s to install every skill in the repo, or drop -g to scope the install to the current project instead of your user profile. Other supported agents include gemini-cli, windsurf, continue, cline, github-copilot, and more — see the skills CLI for the full list.
Start a new agent session after installing so the skill manifest is picked up.
Checking Your Version
npx @xano/developer-mcp --versionIf installed from source:
node dist/index.js --versionInstallation from Source
Prerequisites
Node.js (ES2022+ compatible)
npm
Setup
# Clone the repository
git clone https://github.com/xano-inc/xano-developer-mcp.git
cd xano-developer-mcp
# Install dependencies
npm install
# Build the project
npm run buildUsage
Running the Server
# Production
npm start
# Development (build + run)
npm run devThe server communicates via stdio (standard input/output) using the JSON-RPC protocol, which is the standard transport for MCP servers.
Source Install Configuration
If you installed from source, configure your MCP client to use the local build:
Claude Code:
claude mcp add xano-developer node /path/to/xano-developer-mcp/dist/index.jsClaude Desktop:
{
"mcpServers": {
"xano-developer": {
"command": "node",
"args": ["/path/to/xano-developer-mcp/dist/index.js"]
}
}
}Library Usage
In addition to using this package as an MCP server, you can import and use the tools directly in your own applications.
Installation
npm install @xano/developer-mcpImporting Tools
import {
validateXanoscript,
xanoscriptDocs,
metaApiDocs,
cliDocs,
mcpVersion
} from '@xano/developer-mcp';Validate XanoScript Code
import { validateXanoscript } from '@xano/developer-mcp';
// Validate code directly
const result = validateXanoscript({ code: 'var:result = 1 + 2' });
if (result.valid) {
console.log('Code is valid!');
} else {
console.log('Validation errors:');
result.errors.forEach(error => {
console.log(` Line ${error.range.start.line + 1}: ${error.message}`);
});
}
// Validate a file
const fileResult = validateXanoscript({ file_path: './function/utils.xs' });
// Batch validate a directory
const dirResult = validateXanoscript({ directory: './api', pattern: '**/*.xs' });
console.log(`${dirResult.valid_files}/${dirResult.total_files} files valid`);Get XanoScript Documentation
import { xanoscriptDocs } from '@xano/developer-mcp';
// Get the compact topic index (the no-arg default; ~4KB / ~1K tokens)
const index = xanoscriptDocs();
console.log(index.documentation);
// Get the full prose overview (the previous no-arg default)
const overview = xanoscriptDocs({ topic: 'readme' });
// Get specific topic
const syntaxDocs = xanoscriptDocs({ topic: 'syntax' });
// Get context-aware docs for a file path
const apiDocs = xanoscriptDocs({ file_path: 'api/users/create_post.xs' });
// Get compact quick reference
const quickRef = xanoscriptDocs({ topic: 'database', mode: 'quick_reference' });Get Meta API Documentation
import { metaApiDocs } from '@xano/developer-mcp';
// Get overview
const overview = metaApiDocs({ topic: 'start' });
// Get detailed documentation with examples
const workspaceDocs = metaApiDocs({
topic: 'workspace',
detail_level: 'examples',
include_schemas: true
});
console.log(workspaceDocs.documentation);Get CLI Documentation
import { cliDocs } from '@xano/developer-mcp';
const cliSetup = cliDocs({ topic: 'start' });
console.log(cliSetup.documentation);Get Package Version
import { mcpVersion } from '@xano/developer-mcp';
const { version } = mcpVersion();
console.log(`Using version ${version}`);Available Exports
Export | Description |
| Validate XanoScript code and get detailed error information |
| Get XanoScript language documentation |
| Get Meta API documentation |
| Get CLI documentation |
| Get the package version |
| MCP tool definitions (JSON Schema, for building custom MCP servers) |
| Tool specs with Zod input/output shapes (preferred for new code — works directly with |
| Async tool dispatcher ( |
TypeScript Support
Full TypeScript support with exported types:
import type {
ValidateXanoscriptArgs,
ValidationResult,
ParserDiagnostic,
XanoscriptDocsArgs,
MetaApiDocsArgs,
CliDocsArgs,
ToolResult
} from '@xano/developer-mcp';Package Entry Points
The package provides multiple entry points:
// Main library entry (recommended)
import { validateXanoscript } from '@xano/developer-mcp';
// Tools module directly
import { validateXanoscript } from '@xano/developer-mcp/tools';
// Server module (for extending the MCP server)
import '@xano/developer-mcp/server';Available Tools
1. xano_validate_xanoscript
Validates XanoScript code for syntax errors. Supports multiple input methods. The language server auto-detects the object type from the code syntax.
Parameters:
Parameter | Type | Required | Description |
| string | No | The XanoScript code to validate as a string |
| string | No | Path to a single |
| string[] | No | Array of file paths for batch validation |
| string | No | Directory path to validate all |
| string | No | Glob pattern to filter files when using |
One of
code,file_path,file_paths, ordirectoryis required.
Examples:
// Validate code directly
xano_validate_xanoscript({ code: "var:result = 1 + 2" })
// Validate a single file
xano_validate_xanoscript({ file_path: "function/utils/format.xs" })
// Validate multiple files
xano_validate_xanoscript({ file_paths: ["api/users/get.xs", "api/users/create.xs"] })
// Validate all .xs files in a directory
xano_validate_xanoscript({ directory: "api/users" })
// Validate with a specific pattern
xano_validate_xanoscript({ directory: "src", pattern: "api/**/*.xs" })Returns: List of errors with line/column positions and helpful suggestions, or confirmation of validity.
2. xano_xanoscript_docs
Retrieves XanoScript programming language documentation with context-aware support. Called with no parameters, it returns a compact topic index (~4KB / ~1K tokens) for orientation; use topic='readme' for the full prose overview, or topic=/file_path= to drill in.
Parameters:
Parameter | Type | Required | Description |
| string | No | Specific documentation topic to retrieve |
| string | No | File path being edited for context-aware docs (e.g., |
| string | No |
|
| string | No | Pre-packaged documentation tier for context-limited models: |
| number | No | Maximum estimated token budget. Loads topics in priority order until budget is reached. Helps prevent context overflow for small-window models |
| string[] | No | Topic names to exclude from |
Available Topics:
Topic | Description |
| Minimal syntax survival kit (~5KB, ~1.2K tokens) for models with <16K context — reach via |
| Complete working reference (~17KB, ~4.4K tokens) for models with 16-64K context — reach via |
| XanoScript overview, workspace structure, and quick reference |
| Common patterns, quick reference, and common mistakes to avoid |
| Expressions, operators, and filters for all XanoScript code |
| String filters, regex, encoding, security filters, text functions |
| Array filters, functional operations, and array functions |
| Math filters/functions, object functions, bitwise operations |
| Data types, input blocks, and validation |
| Database schema definitions with indexes and relationships |
| Reusable function stacks with inputs and responses |
| HTTP endpoint definitions with authentication and CRUD patterns |
| Scheduled and cron jobs |
| Event-driven handlers (table, realtime, workspace, agent, MCP) |
| All db.* operations: query, get, add, edit, patch, delete |
| AI agent configuration with LLM providers and tools |
| AI tools for agents and MCP servers |
| MCP server definitions exposing tools |
| Unit tests, mocks, and assertions within functions, APIs, and middleware |
| End-to-end workflow tests with data sources and tags |
| External service integrations index |
| AWS S3, Azure Blob, and GCP Storage |
| Elasticsearch, OpenSearch, and Algolia |
| Redis caching, rate limiting, and queues |
| HTTP requests with api.request |
| Local storage, email, zip, and Lambda |
| Static frontend development and deployment |
| Reusable subqueries for fetching related data |
| Logging, inspecting, and debugging XanoScript execution |
| Performance optimization best practices |
| Real-time channels and events for push updates |
| Security best practices for authentication and authorization |
| Streaming data from files, requests, and responses |
| Request/response interceptors for functions, queries, tasks, and tools |
| Branch-level settings: middleware, history retention, visual styling |
| Workspace-level settings: environment variables, preferences, realtime |
Examples:
// Get the compact topic index (no-arg default)
xano_xanoscript_docs()
// Get the full prose overview (previous no-arg default)
xano_xanoscript_docs({ topic: "readme" })
// Get survival kit for small context models (~1.2K tokens)
xano_xanoscript_docs({ tier: "survival" })
// Get working reference for medium context models (~4.4K tokens)
xano_xanoscript_docs({ tier: "working" })
// Get essentials (recommended first stop)
xano_xanoscript_docs({ topic: "essentials" })
// Get specific topic
xano_xanoscript_docs({ topic: "functions" })
// Discover available topics with sizes
xano_xanoscript_docs({ mode: "index" })
// Budget-aware: load docs up to token limit
xano_xanoscript_docs({ file_path: "api/users/create_post.xs", max_tokens: 2000 })
// Context-aware: get all docs relevant to file being edited
xano_xanoscript_docs({ file_path: "api/users/create_post.xs" })
// Context-aware with exclusions (skip already-loaded topics)
xano_xanoscript_docs({ file_path: "api/users/create_post.xs", exclude_topics: ["syntax", "essentials"] })
// Compact quick reference (uses less context)
xano_xanoscript_docs({ topic: "database", mode: "quick_reference" })3. xano_version
Get the current version of the Xano Developer MCP server.
Parameters: None
Returns: The version string from package.json.
Example:
xano_version()4. xano_meta_api_docs
Get documentation for Xano's Meta API. Use this to understand how to programmatically manage Xano workspaces, databases, APIs, functions, agents, and more.
Parameters:
Parameter | Type | Required | Description |
| string | Yes | Documentation topic to retrieve |
| string | No |
|
| boolean | No | Include JSON schemas for requests/responses (default: true) |
Available Topics:
Topic | Description |
| Getting started with the Meta API |
| API authentication and authorization |
| Workspace management endpoints |
| API group operations |
| API endpoint management |
| Database table operations |
| Function management |
| Scheduled task operations |
| AI agent configuration |
| AI tool management |
| MCP server endpoints |
| Middleware configuration |
| Branch management |
| Real-time channel operations |
| File management |
| Version history |
| Step-by-step workflow guides |
Examples:
// Get overview of Meta API
xano_meta_api_docs({ topic: "start" })
// Get detailed table documentation
xano_meta_api_docs({ topic: "table", detail_level: "detailed" })
// Get examples without schemas (smaller context)
xano_meta_api_docs({ topic: "api", detail_level: "examples", include_schemas: false })
// Step-by-step workflow guides
xano_meta_api_docs({ topic: "workflows" })5. xano_cli_docs
Get documentation for the Xano CLI. The CLI is optional but recommended for local development workflows. Not all users will have it installed.
Use this tool to understand CLI commands for local development, code synchronization, and XanoScript execution.
Parameters:
Parameter | Type | Required | Description |
| string | Yes | Documentation topic to retrieve |
| string | No |
|
Available Topics:
Topic | Description |
| Getting started with the CLI - installation and setup |
| Browser-based OAuth authentication |
| Profile management - credentials and multi-environment setup |
| Workspace operations - pull/push code sync, git integration |
| Personal auto-provisioned dev environment (free-tier friendly) |
| Branch management - list, switch, create, and delete branches |
| Function management - list, get, create, edit |
| Release management - create, export, import, pull, push |
| Tenant management - CRUD, deployments, env vars, backups, clusters |
| Unit test management - list and run unit tests |
| Workflow test management - list, run, and manage workflow tests |
| Platform management - list and view platform versions |
| Static hosting - deploy frontend builds |
| Update the CLI to the latest version |
| CLI + Meta API integration guide - when to use each |
Examples:
// Get CLI setup guide
xano_cli_docs({ topic: "start" })
// Learn when to use CLI vs Meta API
xano_cli_docs({ topic: "integration" })
// Get workspace sync commands
xano_cli_docs({ topic: "workspace", detail_level: "detailed" })
// Profile management with examples
xano_cli_docs({ topic: "profile", detail_level: "examples" })MCP Resources
The server also exposes XanoScript documentation as MCP resources for direct access:
Resource URI | Description |
| Minimal syntax survival kit (~1.2K tokens) |
| Complete working reference (~4.4K tokens) |
| Overview and quick reference |
| Common patterns, quick reference, and common mistakes to avoid |
| Expressions, operators, and filters |
| String filters, regex, encoding, security filters |
| Array filters, functional operations |
| Math filters/functions, object functions, bitwise |
| Data types and validation |
| Database schema definitions |
| Reusable function stacks |
| HTTP endpoint definitions |
| Scheduled and cron jobs |
| Event-driven handlers |
| Database operations |
| AI agent configuration |
| AI tools for agents |
| MCP server definitions |
| Unit tests and mocks |
| End-to-end workflow tests |
| External service integrations index |
| AWS S3, Azure Blob, GCP Storage |
| Elasticsearch, OpenSearch, Algolia |
| Redis caching and queues |
| HTTP requests with api.request |
| Email, zip, Lambda utilities |
| Static frontend development |
| Reusable subqueries for related data |
| Logging and debugging tools |
| Performance optimization |
| Real-time channels and events |
| Security best practices |
| Data streaming operations |
| Request/response interceptors |
| Branch-level settings |
| Workspace-level settings |
npm Scripts
Script | Command | Description |
|
| Compile TypeScript and copy docs |
|
| Run the MCP server |
|
| Build and run in development |
|
| Run unit tests |
|
| Run tests in watch mode |
|
| Run tests with coverage report |
Project Structure
xano-developer-mcp/
├── src/
│ ├── index.ts # MCP server entry point
│ ├── lib.ts # Library entry point (for npm imports)
│ ├── xanoscript.ts # XanoScript documentation logic
│ ├── xanoscript.test.ts # Tests for xanoscript module
│ ├── xanoscript-language-server.d.ts # TypeScript declarations
│ ├── tools/ # Standalone tool modules
│ │ ├── index.ts # Unified tool exports & handler
│ │ ├── index.test.ts # Tests for tool handler
│ │ ├── types.ts # Common types (ToolResult)
│ │ ├── validate_xanoscript.ts # XanoScript validation tool
│ │ ├── xanoscript_docs.ts # XanoScript docs tool
│ │ ├── xanoscript_docs.test.ts # Tests for xanoscript docs tool
│ │ ├── mcp_version.ts # Version tool
│ │ ├── meta_api_docs.ts # Meta API docs tool wrapper
│ │ └── cli_docs.ts # CLI docs tool wrapper
│ ├── meta_api_docs/ # Meta API documentation
│ │ ├── index.ts # API docs handler
│ │ ├── index.test.ts # Tests for index
│ │ ├── types.ts # Type definitions
│ │ ├── types.test.ts # Tests for types
│ │ ├── format.ts # Documentation formatter
│ │ ├── format.test.ts # Tests for formatter
│ │ └── topics/ # Individual topic modules
│ ├── cli_docs/ # Xano CLI documentation
│ │ ├── index.ts # CLI docs handler
│ │ ├── types.ts # Type definitions
│ │ ├── format.ts # Documentation formatter
│ │ └── topics/ # Individual topic modules
│ └── xanoscript_docs/ # XanoScript language documentation
│ ├── docs_index.json # Machine-readable topic registry
│ ├── version.json
│ ├── README.md
│ ├── essentials.md
│ ├── syntax.md
│ ├── syntax/ # Syntax sub-topics
│ │ ├── string-filters.md
│ │ ├── array-filters.md
│ │ └── functions.md
│ └── ...
├── dist/ # Compiled JavaScript output
├── vitest.config.ts # Test configuration
├── package.json
└── tsconfig.jsonDependencies
Package | Version | Purpose |
| ^1.26.0 | Official MCP SDK |
| ^11.6.5 | XanoScript parser and validation |
| ^10.1.2 | Glob pattern matching for context-aware docs |
Dev Dependencies
Package | Version | Purpose |
| ^5.9.0 | TypeScript compiler |
| ^3.0.0 | Fast unit test framework |
| ^22.0.0 | Node.js type definitions |
| ^5.1.2 | Minimatch type definitions |
How It Works
AI Client
│
▼
MCP Protocol (JSON-RPC over stdio)
│
▼
Xano Developer MCP Server
│
├─► xano_validate_xanoscript → Parses code with XanoScript language server
│
├─► xano_xanoscript_docs → Context-aware docs from /xanoscript_docs/*.md
│
├─► xano_meta_api_docs → Meta API documentation with detail levels
│
├─► xano_cli_docs → CLI documentation for local development workflows
│
├─► xano_version → Returns server version from package.json
│
└─► MCP Resources → Direct access to XanoScript documentationAuthentication
The MCP server and library functions do not require authentication. However, when using the documented APIs (Meta API) to interact with actual Xano services, you will need appropriate Xano API credentials. See the xano_meta_api_docs tool for authentication details.
Development
Building
npm run buildCompiles TypeScript to JavaScript in the dist/ directory.
Documentation Structure
XanoScript Documentation (src/xanoscript_docs/):
Markdown files for XanoScript language reference
Configured in
src/xanoscript_docs/docs_index.jsonwith:file: The markdown file containing the documentation
applyTo: Glob patterns for context-aware matching (e.g.,
api/**/*.xs)description: Human-readable description of the topic
aliases: Alternative names for topic lookup
priority: Ordering weight for file_path matching
Meta API Documentation (src/meta_api_docs/):
TypeScript modules with structured documentation
Supports parameterized output (detail levels, schema inclusion)
Better for AI consumption due to context efficiency
Testing
The project uses Vitest as its test framework with comprehensive unit tests.
Running Tests
# Run all tests
npm test
# Run tests in watch mode (re-runs on file changes)
npm run test:watch
# Run tests with coverage report
npm run test:coverageTest Coverage
Module | Test File | Description |
|
| Core XanoScript documentation logic including file path matching and quick reference extraction |
|
| Tool handler dispatch and argument validation |
|
| XanoScript documentation tool and path resolution |
|
| Meta API documentation handler and topic management |
|
| Documentation formatting for endpoints, examples, and patterns |
|
| Type structure validation |
Test Structure
Tests are co-located with source files using the .test.ts suffix:
src/
├── xanoscript.ts
├── xanoscript.test.ts # Tests for xanoscript.ts
├── tools/
│ ├── index.ts
│ ├── index.test.ts # Tests for tool handler
│ ├── xanoscript_docs.ts
│ ├── xanoscript_docs.test.ts # Tests for xanoscript docs tool
│ └── ...
├── meta_api_docs/
│ ├── index.ts
│ ├── index.test.ts # Tests for index.ts
│ ├── format.ts
│ ├── format.test.ts # Tests for format.ts
│ └── ...Writing Tests
Tests use Vitest's API which is compatible with Jest:
import { describe, it, expect } from "vitest";
import { myFunction } from "./myModule.js";
describe("myFunction", () => {
it("should return expected result", () => {
expect(myFunction("input")).toBe("expected");
});
});Upgrading from 1.x to 2.0
Version 2 modernizes the MCP server internals and normalizes all tool names
under a single xano_ namespace. The high-level standalone library functions
(validateXanoscript, xanoscriptDocs, metaApiDocs, cliDocs, mcpVersion)
are unchanged.
Tool renames (MCP clients)
If your agent or MCP client config references tools by name, update them:
1.x | 2.0 |
|
|
|
|
|
|
|
|
|
|
The single xano_ prefix improves discoverability when multiple MCP servers
are installed and lets clients filter Xano tools by name pattern.
Library API
handleTool(name, args) is now async and returns Promise<ToolResult>
instead of ToolResult. Update call sites to use await and the new tool
names:
// 1.x
const result = handleTool("xanoscript_docs", { topic: "syntax" });
// 2.0
const result = await handleTool("xano_xanoscript_docs", { topic: "syntax" });The individual *ToolDefinition exports (validateXanoscriptToolDefinition,
xanoscriptDocsToolDefinition, mcpVersionToolDefinition,
metaApiDocsToolDefinition, cliDocsToolDefinition) were removed in favor
of a single source of truth. Use toolSpecs[name].definition instead:
// 1.x
import { validateXanoscriptToolDefinition } from "@xano/developer-mcp";
// 2.0
import { toolSpecs } from "@xano/developer-mcp";
const validateXanoscriptToolDefinition =
toolSpecs.xano_validate_xanoscript.definition;A new ToolName type export enumerates every registered tool name.
Notable fixes and additions
xano_xanoscript_docsnow correctly accepts the documentedtierandmax_tokensparameters — previously they were silently dropped before reaching the handler.The server is built on the modern
McpServerAPI with Zod-derived schemas, so the JSON Schema published over the wire can no longer drift from the runtime parser.New
toolSpecsexport exposes each tool's Zod input/output shape — use it when registering tools in a customMcpServer.xano_validate_xanoscriptresults now include awarningscount instructuredContenton success.
License
See LICENSE for details.
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
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