> ## Documentation Index
> Fetch the complete documentation index at: https://docs.xano.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Developer MCP
> Install and configure the Xano Developer MCP for AI-assisted XanoScript development
export const BrowserFrame = props => {
const {url = "xano.run", maxWidth = 820, className = "", lightSrc, darkSrc, alt = "", children} = props || ({});
const style = typeof maxWidth === "number" ? {
maxWidth: `${maxWidth}px`,
margin: "16px 0"
} : {
maxWidth,
margin: "16px 0"
};
const hasSwapImages = Boolean(lightSrc && darkSrc);
return
{hasSwapImages ? <>
: children}
;
};
The Xano Developer MCP (`@xano/developer-mcp`) is an MCP server that gives AI assistants superpowers for developing on Xano. It provides XanoScript documentation, code validation, and workflow guides directly to your AI tools.
**What does it do?**
The Developer MCP is designed for **building with Xano**, not managing your Xano instance. It helps AI assistants:
* Access XanoScript language documentation and syntax references
* Validate XanoScript code for syntax errors in real-time
* Retrieve Meta API, Run API, and CLI documentation on demand
* Provide context-aware docs based on the file you're editing
***
## Pick Your Client
The Developer MCP requires [Node.js](https://nodejs.org/) 18 or later. Choose your AI client below for installation and usage instructions.
Don't see your client? The Developer MCP works with any [MCP-compatible client](https://modelcontextprotocol.io/clients). The general pattern is to register `npx -y @xano/developer-mcp` as a stdio server — see any of the pages above for reference.
### Global npm Install
If you prefer a global install instead of `npx`:
```bash theme={null}
npm install -g @xano/developer-mcp
```
Then reference the command directly in your MCP client configuration:
```json theme={null}
{
"xano": {
"command": "xano-developer-mcp"
}
}
```
***
## Xano Skills
The Developer MCP repo also ships two agent skills — portable, agent-neutral prompts that give AI assistants deeper Xano expertise on top of what the MCP provides.
| Skill | Description |
| ------------------------ | --------------------------------------------------------------------------------------------- |
| `xano-init` | Guided setup that profiles a Xano workspace and builds a sandbox-first development playbook |
| `xanoscript-docs-expert` | Deep reference for working with XanoScript documentation and the Developer MCP's architecture |
Skills are distributed via the open Agent Skills standard and install with a single `npx` command — no cloning or manual file copying.
### Install a single skill
```bash theme={null}
npx skills add xano-inc/xano-developer-mcp -s xano-init -a claude-code -g
```
### Install across multiple agents
Install the same skill into several agents at once:
```bash theme={null}
npx skills add xano-inc/xano-developer-mcp -s xano-init \
-a claude-code -a codex -a cursor -a opencode -g
```
Other supported agents include `gemini-cli`, `windsurf`, `continue`, `cline`, and `github-copilot` — see the skills CLI for the full list.
### Flags
| Flag | Purpose |
| ------------ | ---------------------------------------------------------------------------------------------------- |
| `-s ` | Install a specific skill. Drop this flag to install every skill in the repo. |
| `-a ` | Target a specific agent. Repeat the flag for multiple agents. |
| `-g` | Install globally (user profile). Drop this flag to scope the install to the current project instead. |
Start a new agent session after installing so the skill manifest is picked up. Then invoke a skill by name (`xano-init`, `xanoscript-docs-expert`) or just describe the task in natural language.
***
## No Authentication Required
The Developer MCP runs entirely locally and serves documentation and validation tools. It does **not** connect to your Xano instance and requires no access tokens or credentials. Connection to your Xano workspace is handled separately by the [Xano CLI](/xano-cli/get-started).
The APIs documented by the `meta_api_docs` and `run_api_docs` tools do require authentication when you call them directly. The MCP server itself just provides the documentation.
***
## What's Next
Explore all 6 tools available in the Developer MCP
Access MCP resources and use the package as an npm library