Release v2.2.5 · xano-inc/xano-developer-mcp

MCP server tool fields, expression language docs, and MCP registry listing

2.2.4 was published without a GitHub release, so this covers everything since v2.2.3.

xano_validate_xanoscript rejected valid MCP server documents (#68, FR-1196) — validate_xanoscript.ts imports the language-server parser directly, and on 12.8.0 that parser had no grammar for type, resource_uri or tool_meta on mcp_server tool entries. A resource-typed tool entry the backend accepts was reported as an error. Fixed by the 12.14.0 bump below.

MCP server tool connection fields documented (#68, FR-1196) — mcp-servers.md previously showed { name: "..." } as the only tool-entry shape. It now documents the full set — name, active, auth, type, resource_uri, tool_meta — with two behaviours taken from the backend transform rather than inferred from the grammar: values on the wrong type are silently dropped on the next export (resource_uri is emitted only for type: "resource", tool_meta only for type: "tool"), and type throws on anything but those two values. Server-level active and docs added to the key-fields table. Every snippet was verified against the 12.14.0 parser.
Xano expression language docs and filter reference (#67, DEV-6594) — new expressions topic covering context variables, operators, auto-flattening paths, [condition] array filtering, anchoring variables and transformer pipes; new expressions/filters topic with signatures and worked examples for all 210 expression filters; new filter parameter on xano_xanoscript_docs for fetching individual filter entries by name.
MCP registry listing (#66) — server.json registering io.github.xano-inc/xano-developer-mcp, with the npm stdio package entry and the OAuth-protected remote at https://mcp.xano.com.

xanoscript-language-server → 12.14.0 (#68) — adds type, resource_uri and tool_meta grammar on mcp_server and agent tool entries. The lockfile change is isolated; no other packages moved.
Docs version → 2.7.1, re-synced with docs_index.json.

The grammar also accepts these fields on agent tool entries, but they are deliberately left out of agents.md — resource_uri and tool_meta only mean something to an MCP client.

Full diff: v2.2.3...v2.2.5