INDIVIDUAL MCP TOOL

parse

Parse input with the tabnas engine.

tabnas.devnone authenticationAvailability not checked

LIVE ENDPOINT

https://mcp.tabnas.dev/mcp

No auth detected

Connect to this endpoint to inspect the live schema for parse and invoke it with your own arguments.

{}

Inferred read-only · medium confidence · heuristic, not a guarantee.

No write-capable action terms were found; this is not proof that invocation has no side effects.

CONNECT WITH APPROVAL

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.tabnas]
url = "https://mcp.tabnas.dev/mcp"
enabled = true

Claude Code

.mcp.json

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

Claude Desktop

Settings → Connectors → Add custom connector

Name: tabnas
Remote MCP URL: https://mcp.tabnas.dev/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

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

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "tabnas": {
      "type": "http",
      "url": "https://mcp.tabnas.dev/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "tabnas",
  "transport": "streamable-http",
  "url": "https://mcp.tabnas.dev/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

validate_grammar — Validate a serialized GrammarSpec.
explain_parse_error — Parse input and explain the failure.
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 escape-decoded, the expected column is JSON or ERROR / ERROR:<code>.
list_plugins — List every bundled tabnas plugin descriptor (tabnas.
describe_plugin — The full descriptor for one plugin, by package name ('@tabnas/csv') or bare fleet name ('csv').
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?