feat(mcp)!: rename to ooxml convention; refresh public surface#4
Merged
Conversation
Renames every MCP tool to a single ooxml_* prefix and groups them into two visible families: prose search (ooxml_search, ooxml_section, ooxml_parts) over the spec PDFs, and schema lookup (ooxml_element, ooxml_type, ooxml_children, ooxml_attributes, ooxml_enum, ooxml_namespace) over the parsed XSDs. Drops the redundant lookup_ and _info suffixes. Server-level rename: ecma-spec-mcp -> ooxml-mcp (wrangler), MCP server name -> "ooxml". Connect command becomes "claude mcp add --transport http ooxml https://api.ooxml.dev/mcp". DNS at api.ooxml.dev/mcp is unchanged; the deploy creates a new worker and the route binding needs to be repointed once. Drops the duplicate hard-coded tool list in handleMcpInfo so the GET debug endpoint and the JSON-RPC tools/list response can no longer drift. Refreshes the /mcp page, prerender HTML, llms.txt, mcp-server README, and brand.md to reflect both tool families. Adds Codex CLI install instructions next to Claude Code and Cursor. Replaces the homepage NEW callout to announce the schema-lookup launch. BREAKING CHANGE: every existing MCP client config that connects to api.ooxml.dev/mcp must update its tool names. Old names (search_ecma_spec, get_section, list_parts, ooxml_lookup_element, ooxml_lookup_type, ooxml_namespace_info) are not aliased.
caio-pizzol
force-pushed
the
caio/rename-ooxml-mcp
branch
from
42ad606 to
255a35c
Compare
Codex CLI takes --url for HTTP MCP servers, not --transport http (that's Claude Code's flag). The previous setup command exited with 'unexpected argument --transport' for anyone following the docs. Spotted in PR review.
- Add tools/list + initialize snapshot tests so any future drift between TOOLS, OOXML_TOOL_DEFS, and the docs fails CI. Asserts the 9 expected ooxml_* names in documented order and serverInfo.name === 'ooxml'. - Extract ToolDef interface and annotate both TOOLS and OOXML_TOOL_DEFS so a future field on either array (annotations, outputSchema) widens both consistently. - Restore one prose example query so the /mcp page reads as 1 newcomer prose + 1 implementer prose + 2 schema, not jargon-heavy across the board. - Bump root README MCP server badge from v0.0.1 to v0.14.0. Worker auto-deploy concern (route still pointing at the old name) is acknowledged as a manual route swap on merge per author's call.
caio-pizzol
pushed a commit
that referenced
this pull request
Apr 27, 2026
wrangler.toml now claims api.ooxml.dev as a custom_domain so the next deploy moves ownership from ecma-spec-mcp to ooxml-mcp via the Cloudflare API, bypassing the dashboard's "could not be added" error. README intro now mentions the MCP server alongside live previews and implementation notes, since the prose-search + schema-lookup tools are a first-class part of the offering after PR #4.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Renames every MCP tool to a single `ooxml_*` prefix and groups them into two visible families. The two layers of truth become obvious from the names alone:
Drops the redundant `lookup_` and `_info` suffixes since the verb already tells you the action. Doing it now while the consumer set is small enough to migrate without pain.
Server-level: wrangler worker name `ecma-spec-mcp` becomes `ooxml-mcp` and the MCP server identity becomes `ooxml`. The connect command becomes `claude mcp add --transport http ooxml https://api.ooxml.dev/mcp\`. Cleaned up the duplicate hard-coded tool list in `handleMcpInfo` so the GET debug endpoint and JSON-RPC `tools/list` can no longer drift.
Public surface refreshed everywhere it touches reality: the `/mcp` page, prerender, `llms.txt`, root `README`, mcp-server `README`, `brand.md`, and the homepage NEW callout. Codex CLI install is now documented next to Claude Code and Cursor.
Deploy note: `api.ooxml.dev/mcp` DNS is unchanged, but renaming the worker creates a new one rather than renaming the existing one. After auto-deploy, the route binding in the Cloudflare dashboard needs to be repointed to `ooxml-mcp`. Keep the old `ecma-spec-mcp` around briefly as a rollback path.
Breaking: existing MCP client configs that connect to `api.ooxml.dev/mcp` must update their tool names. Old names are not aliased.