tabnas MCP MCP server

The tabnas MCP server provides seven tools for parsing, validating grammars, explaining failures, running fixtures, reading the plugin catalogue, and comparing grammar versions. It allows agents to interact with the tabnas parsing engine via stdio or a hosted HTTP endpoint, ensuring grammars are treated as data rather than executable code.

Endpoint and access

No sign-in: your client connects and lists tools immediately, with no account or key.

No sign-inEndpoint checked 2026-10-05Operated by tabnas

MCP endpoint (Streamable HTTP)

https://mcp.tabnas.dev/mcp

Vendor documentation

What you can do with it

Parse input text using a specified grammar to generate an abstract syntax tree.
Validate a serialized GrammarSpec to check for errors before execution.
Explain parse failures with detailed diagnostics and registry entries.
Compare two grammar versions to detect changes in accepted inputs.

Tools advertised by the last live check:

parse
validate_grammar
explain_parse_error
test_grammar
list_plugins
describe_plugin
compare_grammars

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers a Streamable HTTP server. Use --scope project to write .mcp.json for the repo.

Claude Code configuration

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

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).

Codex configuration

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

Cursor

Merge this server into .cursor/mcp.json in your project, then enable tabnas-mcp in your MCP settings.

Cursor configuration

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

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure). The type must be streamableHttp for a remote HTTP server.

Cline configuration

{
  "mcpServers": {
    "tabnas-mcp": {
      "type": "streamableHttp",
      "url": "https://mcp.tabnas.dev/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start tabnas-mcp and inspect its tools.

VS Code configuration

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

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.

Gemini CLI configuration

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

Claude Desktop

Merge this into claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\), then restart Claude Desktop.

Claude Desktop configuration

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

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.

Windsurf configuration

{
  "mcpServers": {
    "tabnas-mcp": {
      "serverUrl": "https://mcp.tabnas.dev/mcp"
    }
  }
}

See all 957

Do you run tabnas MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing