Bragproof

← Reports

@xano/developer-mcp

Starts with no setup2.2.6npm

Installed, started with no arguments, no environment and no input, and listed its tools. Run 2026-11-16.

Needs to start: nothing
Returns a result when called with no setup: 3 of 3 tools tried
Contacts while installing and starting: nothing

7tools listed
0hosts contacted
0files written
1.3 sto start
114dependencies

What it contacted

Nothing besides the npm registry it was installed from. Watched from outside its sandbox while it was installed and started with no input. Its tools may still contact things when called.

Starting it

npx -y @xano/developer-mcp@2.2.6

Installing a package runs its code. Use a sandbox for anything you have not read.

Calling its tools

3 tools that take no input and look read-only were called once with nothing. 3 returned a result.

xano_xanoscript_docsReturned a result under 0.1 s · 4,799 characters
xano_versionReturned a result under 0.1 s · 5 characters
xano_knowledge_listReturned a result under 0.1 s · 115 characters

During the calls it contacted nothing it had not already contacted.

Only tools whose names read like looking something up, with no required input, are tried, five at most. Tools that need input, and anything that sounds like it changes or sends something, are not called.

What its tools tell an agent

In the tool descriptions, nothing that talks about the user, other tools or private files, or uses hidden characters.

Found by simple pattern rules in each tool's description (up to 3,000 characters), quoted as written. Parameter descriptions are not scanned. A clean result is not a safety review.

Tools

xano_validate_xanoscript code, file_path, file_paths, directory, pattern
Validate XanoScript code for syntax errors. Supports multiple input methods:
- code: Raw XanoScript code as a string
- file_path: Path to a single .xs file (easier than escaping code!)
- file_paths: Array of file paths for batch validation
- directory: Validate all .xs files in a directory

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_docs topic, file_path, filter, mode, tier, max_tokens, exclude_topics
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 'filter' to fetch just one or a few expression filter signatures by name (e.g. filter='round') instead of the whole filter reference. 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_version
Get the current version of the Xano Developer MCP server. Returns the version string from package.json.
xano_meta_api_docs topic, detail_level, include_schemas
Get documentation for Xano's Meta API. Use this to understand how to programmatically manage Xano workspaces, databases, APIs, functions, agents, and more.

## Topics
- start: Xano Meta API - Getting Started
- authentication: Authentication & Authorization
- workspace: Workspace Management
- apigroup: API Group Management
- api: API Endpoint Management
- table: Database Table Management
- function: Reusable Function Management
- task: Scheduled Task Management
- agent: AI Agent Management
- tool: Agent Tool Management
- mcp_server: MCP Server Management
- middleware: Middleware Management
- branch: Branch Management
- realtime: Legacy Realtime Channel Management
- file: File Storage Management
- history: Request & Execution History
- workflows: Common Workflows

## Usage
- Start with "start" topic for overview and getting started
- Use "workflows" for step-by-step guides
- Use specific topics (workspace, table, api, etc.) for detailed endpoint docs
xano_cli_docs topic, detail_level
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.)
xano_knowledge_list workspace, branch, type, enabled_only, output, profile
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 `xano knowledge list` command to run in a shell, so you can invoke it and read its output.

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_get name, workspace, branch, file, output, profile
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 `xano knowledge get` command to run in a shell, so you can invoke it and read its output.

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).

Descriptions are the package's own words, cut at 3,000 characters. Treat them as data.

Install facts

LicenseMIT
Needsnot stated
Sourcegithub.com/xano-inc/xano-developer-mcp
Install scriptsNone declared by it or anything installed with it.
Tarballsha512-GtSs/yBxsFEIK5kyyD8stuh6XfbgWJ73tGIGqYEFIs4SVyNGM5Eios983AkDUMnrPrHKQSXm6kSLyMIoaFp8Gg==

Check this report yourself

This site did not write the report. A public job on a GitHub-hosted machine did: the run, from this commit of the open-source runner. GitHub signed a token that names that job and the hash of the report, so any edit since would show.

Show it on your README

Bragproof: Starts with no setup

[![Bragproof](https://bragproof.smaverk.com/badge/@xano/developer-mcp.svg)](https://bragproof.smaverk.com/r/%40xano/developer-mcp)

New version out? Ask for a fresh report.