Seven tools over the tabnas parsing engine: parse, validate, diagnose, fixtures, compare.
Connect Remote server
claude mcp add --transport http mcp https://mcp.tabnas.dev/mcp
{
"mcpServers": {
"mcp": {
"url": "https://mcp.tabnas.dev/mcp"
}
}
}
{
"servers": {
"mcp": {
"type": "http",
"url": "https://mcp.tabnas.dev/mcp"
}
}
}
Settings > Connectors > Add custom connector
URL: https://mcp.tabnas.dev/mcp
Tools 7 found in our last check
parseParse input with the tabnas engine. Returns {ok:true, tree} or, on parse failure, {ok:false, diagnostic} — the structured diagnostic described by resource tabnas://schema/diagnostic. An invalid grammar is rejected as {ok:false, errors:[{path,message}]}. Without a grammar the bar…
validate_grammarValidate a serialized GrammarSpec. Structural validation against the bundled grammar schema, an engine load in a fresh instance, and a check that every rule reference (`p`, `r`) names a rule the grammar actually defines — a dangling reference loads cleanly and then fails at pars…
explain_parse_errorParse input and explain the failure. Returns {failed:false} when the input parses; otherwise {failed:true, diagnostic, registry} where registry is the error-code registry entry {code,message,hint} for the diagnostic code (resource tabnas://errors), or null for a code the bundled…
test_grammarRun 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 escape-decoded, the expected column is JSON or ERROR / ERROR:<code>. Returns {pass, fail, rows:[{row,input,expected,got,ok…
list_pluginsList every bundled tabnas plugin descriptor (tabnas.plugin.json of each fleet repo), sorted by name. Returns {plugins:[...]}.
describe_pluginThe 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_grammarsGrammar 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? Returns EVIDENCE AND CONFIDENCE, never a bare verdict: {normalForm, proven[], observed[], changes[], counterexamples[]…
Details
| Endpoint | https://mcp.tabnas.dev/mcp (Streamable HTTP) |
| Package | @tabnas/[email protected] (NPM, stdio) |
| First published | 8 Oct 2026 |
| Last updated | 8 Oct 2026 |
| Registry name | dev.tabnas/mcp |
More developer tools servers See all
Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.
