rvt-mcp CLAUDE.md

rvt-mcp CLAUDE.md is an instructions file for coding agents from bimwright/rvt-mcp. It costs 2,303 tokens per session, scanned A, original, Apache-2.0.

Project instructions for rvt-mcp, an MCP gateway that lets coding agents communicate with Autodesk Revit, a building-design application, from 2022 through 2027.

In plain words
What is it for?
Building, deploying, and maintaining the MCP server and all six Revit version plugins.
Why use it?
They explain the project's C# architecture, version-specific plugin shells, communication methods, and build process.

Instructions file

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add instructions/bimwright/rvt-mcp/claude-md
Clone the repo
git clone --depth 1 https://github.com/bimwright/rvt-mcp

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for rvt-mcp CLAUDE.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/bimwright/rvt-mcp/claude-md.svg)](https://agentmods.dev/instructions/bimwright/rvt-mcp/claude-md)
Your own site
<a href="https://agentmods.dev/instructions/bimwright/rvt-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/bimwright/rvt-mcp/claude-md.svg" alt="Measured on agentmods" height="20"></a>
Per session 2,303 This file is loaded in full into every session.
When invoked 2,303 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.02303 $0.02303
Opus 5 $0.01151 $0.01151
Sonnet 5 $0.00461 $0.00461
Haiku 4.5 $0.00230 $0.00230

Measured 5d ago against content hash 2e9d3b0cdaaf, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

rvt-mcp CLAUDE.md scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 5d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

CLAUDE.md · 135 lines

How it starts

The opening of the file, as written. The whole thing — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.

RvtMcp-MCP

Open-source (Apache-2.0) MCP gateway that lets Claude Code (and any MCP-capable client) drive Autodesk Revit 2022–2027.

Architecture

Full C# stack. No TypeScript. Single language, single build system. Multi-version: one plugin shell per Revit 2022–2027.

MCP client (Claude Code / Cursor / Cline / …) → stdio → C# MCP Server (.NET 8 Console App) → TCP or Named Pipe → per-version C# plugin shell → Revit 2022–2027 API

Two processes:

  • RvtMcp.Server.exe — MCP Server, runs as separate process, stdio transport (ModelContextProtocol NuGet)
  • RvtMcp.Plugin.dll — Revit addin, loads inside Revit.exe, TCP listener (R22–R24) or Named Pipe (R25–R27) + ExternalEvent marshalling. Each Revit version gets its own shell DLL compiled from the same src/shared/ source glob.

Communication: newline-delimited JSON (NDJSON). Discovery files written per Revit version in %LOCALAPPDATA%\RvtMcp\:

  • revit-2022.json / revit-2023.json / revit-2024.json — TCP transport (port OS-assigned) + auth token + PID
  • revit-2025.json / revit-2026.json / revit-2027.json — Named Pipe transport + auth token + PID

Discovery file format (schema_version=2):

{
  "schema_version": 2,
  "revit_year": 2024,
  "transport": "tcp",
  "port": 49891,
  "pipe_name": null,
  "auth_token": "...",
  "pid": 67890
}

Server auto-detects which Revit is running by scanning these files (skipping any whose pid is dead). Use --target 2022 etc. (4-digit calendar year, NOT legacy R-codes) to pin a specific version when multiple Revits run. Agents should call revit_list_available_targets to enumerate live instances and revit_get_current_target to inspect the pinned target rather than guessing version strings — revit_switch_target hard-fails with an educational error if passed an R-code like R24.

Project Structure

src/
├── RvtMcp.sln         # Solution (Server + 6 plugin shells)
│
├── server/                   # MCP Server (Console App, .NET 8)
│   ├── RvtMcp.Server.csproj
│   └── Program.cs            # MCP tools + transport client to plugin shells
│
├── shared/                   # Source shared by all plugin shells (glob-included)
│   ├── Handlers/             # One file per command (send_code, create_grid, batch_execute, …)
│   ├── Commands/             # Ribbon button commands
│   ├── Config/               # Configuration loaders
│   ├── Infrastructure/       # CommandDispatcher, McpEventHandler, ResponseSizeGuard, …
│   ├── Transport/            # TcpTransportServer, PipeTransportServer, ITransportServer
│   ├── Logging/              # McpLogger
│   ├── Security/             # AuthToken, SecretMasker
│   ├── ToolBaker/            # Self-evolution engine (list_baked_tools, run_baked_tool, adaptive suggestions)
│   └── Views/                # HistoryWindow
│
├── plugin-r22/               # Revit 2022 shell (.NET 4.8, TCP)
├── plugin-r23/               # Revit 2023 shell (.NET 4.8, TCP)
├── plugin-r24/               # Revit 2024 shell (.NET 4.8, TCP)
├── plugin-r25/               # Revit 2025 shell (.NET 8, Named Pipe)
├── plugin-r26/               # Revit 2026 shell (.NET 8, Named Pipe)
└── plugin-r27/               # Revit 2027 shell (.NET 10, Named Pipe)

Read the full file on GitHub · 135 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 5d ago First seen · 135 lines · 2,303 tokens per session scan A 2e9d3b0cdaaf

Subscribe to this mod's changes

rvt-mcp CLAUDE.md is an instructions file published in the GitHub repository bimwright/rvt-mcp (19 stars, last pushed 7d ago), licensed Apache-2.0. It adds 2,303 tokens to every session, about $0.0115 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.