Skip to content

Latest commit

 

History

History
80 lines (52 loc) · 3.07 KB

File metadata and controls

80 lines (52 loc) · 3.07 KB
logo

Web MCP Server License: MIT

The OOXML spec, explained by people who actually implemented it.

What is this?

An interactive reference for OOXML, built by the team behind SuperDoc. Every page combines XML structure, live rendered previews, and implementation notes the spec leaves out. The MCP server exposes the same knowledge to AI assistants: prose search across the spec PDFs and deterministic schema lookup over the parsed XSDs.

  • Live previews - Edit XML and see it render in real-time. Every example is a working document.
  • Implementation notes - Where Word diverges from the spec, what will break your code, and what to do about it.
  • Semantic spec search - 18,000+ spec chunks searchable by meaning via MCP server.
  • Structural schema lookup - Element children, attributes, types, enums, namespaces. Same MCP server, deterministic answers from the parsed XSDs.

Why?

The ECMA-376 spec is 5,000+ pages and it lies. Word's actual behavior diverges from the standard in ways you only discover by building against it. The knowledge to implement OOXML correctly is locked inside a handful of companies that have no incentive to share it.

We faced this at SuperDoc — building a document engine on native OOXML with no roadmap beyond an unreliable spec. We wrote down everything we learned and made it public. No one should have to reverse-engineer Word alone.

MCP Server

Ask questions in natural language and get answers grounded in the spec, or query the schema graph for precise structural answers. Works with Claude Code, Codex CLI, Cursor, and any MCP-compatible client.

Claude Code

claude mcp add --transport http ooxml https://api.ooxml.dev/mcp

Codex CLI

codex mcp add ooxml --url https://api.ooxml.dev/mcp

Or in ~/.codex/config.toml:

[mcp_servers.ooxml]
url = "https://api.ooxml.dev/mcp"

Cursor — add to your MCP settings:

{
  "mcpServers": {
    "ooxml": { "url": "https://api.ooxml.dev/mcp" }
  }
}

Two tool families share one server:

  • Prose search (over the spec PDFs): ooxml_search, ooxml_section, ooxml_parts
  • Schema lookup (over the parsed XSDs): ooxml_element, ooxml_type, ooxml_children, ooxml_attributes, ooxml_enum, ooxml_namespace

Development

bun install    # Install dependencies
bun dev        # Dev server at http://localhost:5173
bun run build  # Production build

Contributing

Contributions welcome. Add implementation notes, fix examples, or improve the reference.

License

MIT


Built by 🦋 SuperDoc — DOCX editing and tooling