Skip to content

Open-source Revit MCP server: let Claude and other AI assistants read and edit BIM models, with human approval on every change.

Merge directory-ratings fixes: mcp<2 pin, tool metadata, package data

sammohammad5782be88bd56436
diff --cc CHANGELOG.md
index 0a12470,88d8c1b..15cdd98
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@@ -2,7 -2,12 +2,12 @@@
## Unreleased
+- Release: the MCP Registry publish now starts automatically after each stable release and reads the version from `VERSION`, so the bundle hash is no longer left stale.
+ - Fix install: `mcp` is now pinned `>=1.10,<2`. An unpinned install on Python 3.12+ resolved mcp 2.x, which removed the `Server.list_tools()` decorators this server uses, so the server crashed at import. `uv.lock` was also stale (missing `anthropic`) and is refreshed.
+ - Fix packaging: module manifests, QA/QC rules and recipes were missing from the wheel, so a pip or uvx install lacked the 34 module tools. They are now package data.
+ - Tools: every tool now lists a full description, a described input schema, a title and MCP annotations (`readOnlyHint`, `destructiveHint`, `idempotentHint`, `openWorldHint`), derived from the existing approval-gate flags. The server reports its own version and usage instructions at initialize. No tool behaviour changed.
+ - Mock mode: tools backed by a legacy handler (for example `revit_health`) no longer fail with a missing `request_id`, so directories can call them without Revit.
+ - Directories: add a root `Dockerfile` (mock mode), `glama.json` and `smithery.yaml` so listing sites can build and introspect the server without Revit. README gains a quick start, a tool table and a demo placeholder; `server.json` and `manifest.json` document more environment variables and keywords.
-- Release: `publish-mcp.yml` also runs after the release workflow completes. Releases created with the workflow token do not fire `release: published`, which is why the MCP Registry stayed on 1.1.0 after 1.2.1 and 1.3.0 were released.
## 1.3.1 - 2026-10-09