Agents Index

tc39-mcp

Online

Independent MCP server for the TC39 specs (ECMA-262 + ECMA-402): clauses, search, diffs, history.

Visit publisherConnectJSON

What it can do: 17 tools

  • spec.aboutSelf-description of this MCP server: package name + version, per-snapshot pin metadata (sha, fetched_at, biblio_commit, clause_count) for every supported (spec, edition), plus test262 + proposals index headers when prese
  • clause.getFetch a parsed TC39 clause as structured JSON. `spec` selects '262' (default) or '402'. `edition` defaults to 'latest'. `at: '<sha>'` pins to a historical main snapshot (only valid for edition='main'); omit to query the
  • clause.listList parsed spec clauses with optional filters (kind, section prefix, has_algorithm). `spec` selects '262' or '402'. `at: '<sha>'` queries a historical main snapshot.
  • spec.searchSearch the parsed spec by clause id / aoid / title (+ step text with `search_steps`). Aoid-exact ranks first. `at: '<sha>'` searches a historical main snapshot.
  • proposal.listList TC39 proposals from the static index (tc39/proposals). Filter by spec ('262'|'402'), stage ('0'|'1'|'2'|'2.7'|'3'|'finished'|'inactive'|'active'), champion (substring), or contains (name/slug substring).
  • proposal.getFetch one TC39 proposal by slug (exact) or name (case-insensitive).
  • spec.grammarQuery grammar productions captured from the spec's `<emu-grammar>` blocks. `{ nonterminal }` returns every production for that non-terminal (exact match); `{ contains }` filters by RHS / name substring; neither lists all
  • spec.tablesList or fetch parsed `<emu-table>` content. `{ id }` returns exactly that table (full columns + rows); otherwise list table summaries, optionally narrowed by a `filter` substring over the caption or id.
  • spec.sdo_indexIndex Syntax-Directed Operations by the grammar production they're defined on. `by: 'production'` (default) groups SDOs under each production; `by: 'sdo'` groups productions under each SDO title. `filter` narrows to keys
  • clause.outlineReturn the section tree (table of contents) for a parsed (spec, edition). `depth` caps how deep the tree descends (1 = top-level only); `under` limits the tree to descendants of one clause id.
  • spec.global_searchRun spec.search across both ECMA-262 and ECMA-402 in one call and interleave hits by score. Each hit is tagged with the spec it came from. Use it when you don't know which spec defines a symbol. `search_steps` also match
  • spec.snapshotsList the live (spec, edition, sha, fetched_at) snapshots the hosted Worker is serving from R2. Filter by `spec` ('262'|'402') or `edition` (e.g. 'main', 'es2026'). Historical SHA-pinned copies are reachable via `at:` on
  • spec.symbol_resolveResolve spec notation like `[[Prototype]]` (internal slot), `%Object.prototype%` (well-known intrinsic), or `~number~` (sigil enum): return clauses that mention or define it, ranked by occurrence with a bump for definiti
  • spec.well_known_intrinsicsEnumerate the well-known intrinsics in a spec with their probable defining clauses. Driven from the canonical §6.1.7.4 WKI table when present (ECMA-262), else a `%X%` prose scan (e.g. ECMA-402). `filter` narrows by bare-
  • spec.diffClause-level diff of one clause across two editions of a spec. Reports identical / modified / added / removed plus a field-level breakdown (title, signature, step count, reworded step indices, notes, crossrefs). `from` d
  • spec.crossrefsFor a clause id, return its outgoing references (clauses it cites) and/or incoming references (clauses that cite it — the back-reference index the parse alone doesn't expose). The reverse index is AOID-densified from ste
  • test262.searchSearch the tc39/test262 conformance suite from its indexed front-matter. `query` AND-matches whitespace tokens (case-insensitive) across each test's description + path; `esid` prefix-matches the front-matter esid. Return

Connect it

Claude Code
claude mcp add --transport http tc39-mcp https://mcp.xyzzylabs.ai/tc39/mcp
Claude.ai / ChatGPT
Settings → Connectors → Add custom connector
URL: https://mcp.xyzzylabs.ai/tc39/mcp
Cursor (~/.cursor/mcp.json)
{
  "mcpServers": {
    "tc39-mcp": {
      "url": "https://mcp.xyzzylabs.ai/tc39/mcp"
    }
  }
}
VS Code (.vscode/mcp.json)
{
  "servers": {
    "tc39-mcp": {
      "type": "http",
      "url": "https://mcp.xyzzylabs.ai/tc39/mcp"
    }
  }
}

Questions

What does tc39-mcp do?

Independent MCP server for the TC39 specs (ECMA-262 + ECMA-402): clauses, search, diffs, history. It exposes 17 tools to AI assistants.

What tools does tc39-mcp provide?

17 tools, including spec.about, clause.get, clause.list, spec.search, proposal.list, proposal.get, spec.grammar, spec.tables, spec.sdo_index, clause.outline, spec.global_search, spec.snapshots….

How do I connect tc39-mcp to Claude, ChatGPT or Cursor?

Add the remote MCP endpoint https://mcp.xyzzylabs.ai/tc39/mcp as a custom connector or MCP server. Copy-paste setup is on this page.

Does tc39-mcp require an account or API key?

No sign-in was needed to list its tools. Individual tools may still need an account or API key.

Is tc39-mcp online?

As of 2026-11-19 our probe found it online. It answered 100% of our last 3 checks.

Who publishes tc39-mcp?

@xyzzylabs on GitHub. The official MCP Registry verified that the publisher controls this GitHub account before accepting the listing.

Similar in Web Search & Scraping