# Tabnas MCP server

Source: https://glimind.com/server/mcp-registry%2Fdev.tabnas%2Fmcp
Registry id: `mcp-registry/dev.tabnas/mcp`
Status: live (checked 2026-10-26T22:32:50.825Z)

## Measurements (30 days)

- Uptime: 100%
- Checks: 4984
- Outages (90 days): 0

## Install

```json
{
  "mcpServers": {
    "tabnas-mcp-server": {
      "type": "http",
      "url": "https://mcp.tabnas.dev/mcp"
    }
  }
}
```

Claude Code:

```sh
claude mcp add --transport http tabnas-mcp-server https://mcp.tabnas.dev/mcp
```

## Tools (7)

- `compare_grammars`: Grammar compatibility (AX plan Phase 5): does candidate grammar B still accept what baseline A accepted, and does it build the same tree for inputs both accept?
- `describe_plugin`: The full descriptor for one plugin, by package name ('@tabnas/csv') or bare fleet name ('csv'). Unknown names get {ok:false, errors} naming the known plugins.
- `explain_parse_error`: Parse input and explain the failure. Returns {failed:false} when the input parses; otherwise {failed:true, diagnostic, registry} where registry is the error-cod
- `list_plugins`: List every bundled tabnas plugin descriptor (tabnas.plugin.json of each fleet repo), sorted by name. Returns {plugins:[...]}.
- `parse`: Parse input with the tabnas engine. Returns {ok:true, tree} or, on parse failure, {ok:false, diagnostic} — the structured diagnostic described by resource tabna
- `test_grammar`: Run TSV fixture content against a grammar in a fresh instance, using the fleet fixture convention (@tabnas/support): line 1 is a header, the input column is esc
- `validate_grammar`: Validate a serialized GrammarSpec. Structural validation against the bundled grammar schema, an engine load in a fresh instance, and a check that every rule ref

Measured by Glimind (https://glimind.com): MCP handshake + tool list only, no tool is ever called. CC BY 4.0.