tabnas MCP server

tabnas is an MCP server with 7 tools an agent can call, among them compare_grammars, describe_plugin, explain_parse_error. It answers at https://mcp.tabnas.dev/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 6 of 6 times since 10 September 2026; the last check, on 19 October 2026, succeeded.

Status

Answering

Tools

Official

yes, served from tabnas.dev

Reliability

6 of 6 checks

Response time

192 ms

Transport

streamable HTTP

Last checked

19 October 2026

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

Description as the publisher wrote it.

The 7 tools tabnas offers

Tool	What it does
`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? Returns EVIDENCE AND CONFIDENCE, never a bare verdict: {normalForm, proven[], o Inputs: a, b, corpus, options, depth
`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. Inputs: name
`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-code registry entry {code,message,hint} for the diagnostic code (resource tabnas:// Inputs: input, grammar
`list_plugins`	List every bundled tabnas plugin descriptor (tabnas.plugin.json of each fleet repo), sorted by name. Returns {plugins:[...]}.
`parse`	Parse 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:[{pat Inputs: input, grammar, options
`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>. Returns {pass, Inputs: spec, grammar, options
`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 reference (`p`, `r`) names a rule the grammar actually defines — a dangling referen Inputs: grammar

Add tabnas to your AI client

Every block below points at https://mcp.tabnas.dev/mcp. Pick your client and copy.

Claude Code: one command in your terminal

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

Claude Desktop: claude_desktop_config.json

{
  "mcpServers": {
    "tabnas": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://mcp.tabnas.dev/mcp"]
    }
  }
}

Cursor: ~/.cursor/mcp.json, or .cursor/mcp.json in a project

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

VS Code and GitHub Copilot: .vscode/mcp.json

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

Zed: Zed settings.json

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

Windsurf: ~/.codeium/mcp_config.json

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

JetBrains AI Assistant: Settings, Tools, AI Assistant, MCP, New MCP Server, as JSON

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

Continue: .continue/mcpServers/neuronto.yaml

name: tabnas
version: 0.0.1
schema: v1
mcpServers:
  - name: tabnas
    type: streamable-http
    url: https://mcp.tabnas.dev/mcp

Gemini CLI: ~/.gemini/settings.json

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

Codex CLI: MCP server config

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

Warp: MCP servers, + Add, paste JSON

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

Goose: a one-click extension link

goose://extension?url=https%3A%2F%2Fmcp.tabnas.dev%2Fmcp&type=streamable_http&id=tabnas&name=tabnas

Is tabnas up right now?

It answered our last check on 19 October 2026 in 192 ms. Over 6 checks since 10 September 2026 it answered 6. Status here comes from Neuronto's own probes, not from the publisher.

MCP servers similar to tabnas

TaScan80 tools AISOTools5 tools Gtm Tools4 tools ToolsMonk tool catalog5 tools Atisbo8 tools KnownFix17 tools

Questions about tabnas

Is there an official tabnas MCP server?

Yes. It is published by tabnas.dev and served from mcp.tabnas.dev, the vendor's own domain: https://mcp.tabnas.dev/mcp.

How many tools does tabnas have?

7, as returned by the server's own tools/list on 11 September 2026: compare_grammars, describe_plugin, explain_parse_error, list_plugins, parse, test_grammar, validate_grammar.

Is tabnas down?

It answered our last check on 19 October 2026 in 192 ms. Over 6 checks since 10 September 2026 it answered 6.

How do I add tabnas to Cursor?

Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://mcp.tabnas.dev/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.

Does tabnas need an API key?

It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.

Where this comes from

Publisher: dev.tabnas. Endpoint host: mcp.tabnas.dev. ARD identifier: urn:air:dev.tabnas:mcp:mcp. First indexed 10 September 2026. The tools are exactly what the server returned; nothing on this page is inferred from its name. Ranking in Neuronto search is never for sale.

Is this your server? Get a message the day it stops answering or its tools change: monitoring, 14 days free. Or claim the domain to manage how it is listed.