# tabnas

> tabnas is a free MCP server for developer tools. Parse text with a tabnas grammar, validate grammars and compare grammar versions. It can run locally on your machine or as a hosted remote server.

- **Kind:** MCP server
- **Pricing:** Free
- **Platforms:** CLI, API, self-hosted
- **Website:** https://tabnas.dev/mcp
- **Repository:** https://github.com/tabnas/mcp
- **MCP Registry name:** dev.tabnas/mcp
- **Categories:** developer tools
- **Listing updated:** 2026-11-15

## About

Grammars here are data, not code, and the server is built around that. Before any operation that takes a grammar, a firewall rejects prototype-pollution keys, live function references and plugin injection. The grammar then goes through structural schema validation and a trial load. Each call uses a fresh engine, so there is no state carried between calls.

Seven tools cover parsing input with a grammar, checking a serialized grammar before running it, explaining a failed parse with its error code, position, expected tokens and rule stack, running shared TSV fixtures, listing grammar plugins and describing one in full. The seventh, compare_grammars, asks whether a changed grammar still accepts what the old one did and builds the same trees, and reports proven and observed results with a confidence value rather than a bare verdict.

The package also installs a tabnas command-line tool over the same core. Its --json output is byte-identical to the MCP result, and golden tests hold the two to that. Local stdio via npx is the recommended route. A hosted endpoint exists for clients that cannot spawn processes, with a 256 KB body cap and a per-IP rate limit, and it says it never logs or stores document content.

## Features

- **Parse with a grammar:** Returns the parse tree or a structured diagnostic for any input.
- **Grammar validation:** Checks a serialized grammar against a schema and a security scan before it runs.
- **Failure explanation:** Reports error code, position, expected tokens and rule stack with the registry entry.
- **Fixture testing:** Runs shared TSV fixtures against a grammar and returns per-row results.
- **Version comparison:** Reports whether a grammar change keeps accepting old inputs and building the same trees.
- **Matching CLI:** Provides a tabnas command whose JSON output equals the MCP tool result.

## Good for

- Debug why an input fails to parse
- Check a new grammar for errors before using it
- Regression-test a grammar edit against fixtures
- Compare two grammar versions for compatibility
- Browse available grammar plugins and their error codes

## Install

### Claude Code (Terminal)

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

### Claude Desktop (Settings → Connectors → Add custom connector)

```sh
https://mcp.tabnas.dev/mcp
```

### Cursor (~/.cursor/mcp.json)

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

### VS Code (.vscode/mcp.json)

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

### Windsurf (~/.codeium/windsurf/mcp_config.json)

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

### Other clients (your client's MCP settings (most use this shape))

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

## Tools

- `parse`: Parse input with a grammar and return the tree or a diagnostic.
- `validate_grammar`: Check a serialized grammar before running it.
- `explain_parse_error`: Explain a parse failure with code, position, expected tokens and rule stack.
- `test_grammar`: Run shared TSV fixtures against a grammar.
- `list_plugins`: List grammar plugins and what each parses.
- `describe_plugin`: Return one plugin's descriptor.
- `compare_grammars`: Check whether a grammar change still accepts the old inputs and builds the same trees.

## FAQ

### How do I run it?

Use npx --yes @tabnas/mcp mcp over stdio, or point a client at the hosted streamable-HTTP endpoint.

### Which transport is recommended?

Local stdio, which the site describes as free, private, unlimited and reproducible.

### Does the hosted endpoint keep my documents?

No. The site says document content is never logged, stored or used for training.

### Can a grammar run arbitrary code?

No. Grammars are treated as data and a firewall rejects prototype keys and non-builtin function references.

### Is tabnas free?

Yes. tabnas is free to use.

### How do I add tabnas to Claude Code?

Run this command in your terminal: claude mcp add --transport http mcp https://mcp.tabnas.dev/mcp

### What are the best alternatives to tabnas?

The closest alternatives to tabnas are REA, Codebase Memory, GitHub, Serena MCP: the IDE for your agent and XERJ.

## Alternatives

- [REA](https://ai-powered.com/mcp/rea): REA is an open-source MCP server for developer tools.
- [Codebase Memory](https://ai-powered.com/mcp/codebase-memory): Codebase Memory is an open-source MCP server for knowledge and memory.
- [GitHub](https://ai-powered.com/mcp/github-2): GitHub is an open-source MCP server for developer tools.
- [Serena MCP: the IDE for your agent](https://ai-powered.com/mcp/serena-mcp-the-ide-for-your-agent): Serena MCP: the IDE for your agent is an open-source MCP server for developer tools.
- [XERJ](https://ai-powered.com/mcp/xerj): XERJ is an open-source MCP server for knowledge and memory.
- [Ouroboros](https://ai-powered.com/mcp/ouroboros): Ouroboros is an open-source MCP server for developer tools.
- [Claude Code Ultimate Guide](https://ai-powered.com/mcp/claude-code-ultimate-guide): Claude Code Ultimate Guide is an open-source MCP server for ai models and llm tooling.
- [Concord MCP](https://ai-powered.com/mcp/concord-mcp): Concord MCP is a freemium MCP server for developer tools.

---
Source: https://ai-powered.com/mcp/tabnas
