dev.tabnas/mcp

up checked 2026-11-11T04:39:19.260Z

Unclaimed · Unverified

Publisher-provided title

tabnas

Publisher-provided description

Seven tools over the tabnas parsing engine: parse, validate, diagnose, fixtures, compare.

Summary by lookupd

Lets agents parse, validate, diagnose and compare tabnas grammars, and list or describe bundled tabnas parser plugins.

Install

Claude Code, remote (streamable-http)

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

Claude Code, npm package (stdio)

claude mcp add mcp -- npx -y @tabnas/mcp

Codex, remote (streamable-http)

codex mcp add mcp --url https://mcp.tabnas.dev/mcp

Codex, npm package (stdio)

codex mcp add mcp -- npx -y @tabnas/mcp

Cursor, remote (streamable-http) → .cursor/mcp.json

{
  "mcpServers": {
    "mcp": {
      "url": "https://mcp.tabnas.dev/mcp"
    }
  }
}

Cursor, npm package (stdio) → .cursor/mcp.json

{
  "mcpServers": {
    "mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@tabnas/mcp"
      ]
    }
  }
}

Other clients: docs. Or tell your agent: Set up lookupd for me: read https://lookupd.com/agent.md and follow it.

Publisher-provided text

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
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
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
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
list_plugins List every bundled tabnas plugin descriptor (tabnas.plugin.json of each fleet repo), sorted by name. Returns {plugins:[...]}.
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.
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?

Shows this live status and links here; updates hourly.

[![lookupd status](https://lookupd.com/badge/dev.tabnas/mcp.svg)](https://lookupd.com/servers/dev.tabnas/mcp)