[{"_1":2,"_3":-5,"_4":-5},"loaderData",{"_5":6,"_7":8,"_9":10},"actionData","errors","root",{"_122":123},"routes/modules.$creator.$moduleId",{"_14":15,"_16":17,"_18":19,"_20":21},"routes/modules.$creator.$moduleId.endpoints",{"_11":12,"_13":-5},"error","Module not found","tools","module",{"_20":22,"_23":24,"_25":26,"_27":28,"_29":30,"_31":32,"_33":34,"_35":26,"_36":37,"_38":-5,"_39":-5,"_40":-5,"_41":42,"_43":44,"_45":46,"_47":48,"_49":50,"_51":52,"_53":54,"_55":-5,"_56":48,"_57":58,"_59":60,"_61":-5,"_62":-5,"_63":-5,"_64":-5,"_65":66,"_67":68,"_69":70,"_71":72,"_73":74,"_75":-5,"_76":-5,"_77":-5,"_78":48,"_79":-5,"_80":81,"_82":83,"_84":85,"_86":87,"_88":89,"_90":91},"apiUrl","https://odel.app/api","creator","bimwright","moduleId","rvt-mcp","@bimwright/rvt-mcp","displayName","Bimwright","tagline","MCP gateway for Autodesk Revit 2022-2027 - toolset gating + Transaction-safe batch execution.","iconKey","https://avatars.githubusercontent.com/u/276485910?v=4","category","local","status","published","visibility","public","metaDescription","deploymentType","external","workerName","bindingName","mcpConfig","pricingModel","free","creatorUserId","system:external-import","createdAt",1783338238000,"updatedAt",1788778007000,"sourceRegistry","official-mcp-registry","sourceUrl","https://registry.modelcontextprotocol.io/v0/servers?search=io.github.bimwright%2Frvt-mcp","sourceVerified",true,"sourceMissingSince","importedAt","upstreamStars",19,"upstreamUpdatedAt",1787892244000,"detectedTransport","detectedAuthType","probeStatus","lastProbedAt","githubRepoUrl","https://github.com/bimwright/rvt-mcp","githubRepoFullName","bimwright/rvt-mcp","releaseId","ext-bimwright-rvt-mcp","version","0.3.0","descriptionMarkdown","\n\n

\n $\"rvt-mcp\"$ \n

\n\n

rvt-mcp

\n\n

\n MCP gateway for Autodesk Revit — local tools for agents, optional personal bake loop\n

\n\n

\n $\"build\"$ \n $\"license\"$ \n $\"Revit$ \n $\"MCP$ \n

\n\n

\n English · Tiếng Việt · 简体中文 · 日本語\n

\n\n---\n\n## Install\n\nClient machines should use the setup ZIP from [GitHub Releases](https://github.com/bimwright/rvt-mcp/releases/latest). It bundles a self-contained MCP server and Revit 2022–2027 plugins — no .NET SDK, NuGet global tool, or source clone.\n\n**AI agents:** download `RvtMcp.Setup-*-win-x64.zip` from the latest release and run the installer. Do **not** clone, build, or `dotnet tool install` unless the user asked for a developer setup. Protocol: [AGENTS.md](https://github.com/bimwright/rvt-mcp/blob/master/AGENTS.md).\n\n```powershell\n$tag = (Invoke-RestMethod https://api.github.com/repos/bimwright/rvt-mcp/releases/latest).tag_name\n$zip = \"$env:TEMP\\RvtMcp.Setup-$tag-win-x64.zip\"\n$dir = \"$env:TEMP\\RvtMcp.Setup-$tag-win-x64\"\nInvoke-WebRequest \"https://github.com/bimwright/rvt-mcp/releases/download/$tag/RvtMcp.Setup-$tag-win-x64.zip\" -OutFile $zip\nExpand-Archive $zip -DestinationPath $dir -Force\n\npowershell -ExecutionPolicy Bypass -File \"$dir\\install.ps1\" -WhatIf\npowershell -ExecutionPolicy Bypass -File \"$dir\\install.ps1\"\n```\n\nThe installer detects Revit 2022–2027, installs matching plugins, copies the server under `%LOCALAPPDATA%\\RvtMcp\\rvt\\server\\\\`, and wires detected MCP clients. Override with `-Client codex|opencode|claude|kilo|none`.\n\nDo **not** install v0.5.0 or earlier ZIPs. Do **not** `dotnet tool install -g Bimwright.Rvt.Server` (legacy 0.1–0.3). Do **not** use NuGet instead of this ZIP on a Revit client machine — the tool package has no add-in.\n\nFor AutoCAD, use [dwg-mcp](https://github.com/bimwright/dwg-mcp) separately — different product, different install.\n\n### Check that it works\n\n1. Open Revit with a model.\n2. Start the MCP connection from the ribbon (BIMwright / RvtMcp panel).\n3. From the MCP client, list tools, then call `revit_get_current_view_info`.\n\nYou should get something like:\n\n```json\n{ \"viewName\": \"Level 1\", \"viewType\": \"FloorPlan\", \"levelName\": \"Level 1\", \"scale\": 100 }\n```\n\nIf that fails, install is not done yet — fix client config / plugin load before anything else.\n\n### Uninstall\n\nFrom the setup ZIP root (or this repo’s `scripts/`):\n\n```powershell\n# Setup ZIP layout:\npowershell -ExecutionPolicy Bypass -File .\\uninstall.ps1 -WhatIf\npowershell -ExecutionPolicy Bypass -File .\\uninstall.ps1 -Yes\n\n# Clone layout:\npowershell -ExecutionPolicy Bypass -File .\\scripts\\uninstall-all.ps1 -WhatIf\npowershell -ExecutionPolicy Bypass -File .\\scripts\\uninstall-all.ps1 -Yes\n```\n\nRemoves plugins, self-contained server, client entries, discovery files, logs, and ToolBaker cache.\n\n### Developer install\n\n```powershell\ngit clone https://github.com/bimwright/rvt-mcp.git\ncd rvt-mcp\ndotnet build src/RvtMcp.sln -c Debug\npowershell -ExecutionPolicy Bypass -File .\\scripts\\install.ps1 -SourceDir . -Client none\n```\n\nClose every Revit first — the build deploys plugin DLLs into `%APPDATA%\\Autodesk\\Revit\\Addins\\\\RvtMcp\\`. `install.ps1` finds Revit 2022–2027, copies the server under `%LOCALAPPDATA%\\RvtMcp\\rvt\\server\\\\`, and wires detected MCP clients (`-Client codex|opencode|claude|kilo|none`, `-Years 2024` for one year).\n\n**Optional — NuGet server only** (does **not** install Revit plugins). Use this if the add-in is already on the machine (ZIP or a local build) and you want the MCP server on PATH:\n\n```powershell\ndotnet tool uninstall -g Bimwright.Rvt.Server # skip if you never installed the 0.1–0.3 tool\ndotnet tool install -g RvtMcp.Server --version 0.6.1\n```\n\nCommand name: `rvt-mcp`. Keep using the GitHub Release ZIP for plugins. `Bimwright.Rvt.Server` is obsolete.\n\n### Migrating from `Bimwright.Rvt.*` (v0.3 and earlier)\n\nv0.4+ renamed packages and folders to `RvtMcp.*` (repo name and brand stay bimwright).\n\n1. Close every Revit.\n2. `pwsh scripts/uninstall-old.ps1` — drops old `%APPDATA%\\…\\Bimwright\\` plugins and old server root; keeps user bake/journal data and migrates it to `%LOCALAPPDATA%\\RvtMcp\\` on first new launch.\n3. Install the current GitHub Release ZIP (Client install above). Do not install v0.5.0 or earlier packages. Uninstall the old global tool if present: `dotnet tool uninstall -g Bimwright.Rvt.Server`.\n4. Point MCP clients at entry name **`rvt-mcp`** (old per-year `bimwright-rvt-r22`… entries are removed by the installer).\n\n---\n\n## What this is\n\n`rvt-mcp` is a **local** bridge between an MCP client (Claude, Cursor, Codex, OpenCode, …) and a running Revit session.\n\nTwo processes:\n\n| Piece | Role |\n|--------|------|\n| **RvtMcp.Server** | .NET 8 MCP server on stdio. No Revit reference — builds anywhere. |\n| **RvtMcp.Plugin** | One thin add-in per Revit year (2022–2027). Runs inside Revit, executes on the UI thread. |\n\nAgent → MCP → server → localhost TCP (≤2024) or Named Pipe (≥2025) → plugin → Revit API.\n\nEverything stays on the machine. No cloud relay is required for the gateway itself.\n\nThere is no Node/TypeScript sidecar. Server, plugins, handlers, and ToolBaker are C# end to end. Shared command code lives in `src/shared/`; each year is a small shell project with `#if` where the API drifted. Details: [ARCHITECTURE.md](https://github.com/bimwright/rvt-mcp/blob/master/ARCHITECTURE.md).\n\n---\n\n## Why it exists\n\nPeople who live in Revit already know what they want automated. The friction was always shipping that idea as software: learn enough C#/Dynamo, fight the API, package an add-in, survive version upgrades — or pay someone else, or buy a fixed tool that only half-matches the office.\n\nAgents change the first half of that loop (describe the task, try it live). They do not remove transactions, units, selection, worksharing, or “did this just trash the model?” That is what this gateway is for: a **typed tool surface** for common work, plus an escape hatch when you need ad-hoc C# inside Revit, plus an **optional** path to turn repeated local patterns into personal tools (ToolBaker).\n\nIt is not a universal add-in for every firm. Offices differ. The bet is: start from a shared runtime, grow *your* tools on top.\n\n**Scope posture (honest):** we do not mint a new MCP tool for every edge case. Prefer typed tools when they exist; for everything else use `revit_send_code_to_revit` (C# only). Family *project* management is covered; full Family Editor authoring suites and Revit Viewer hosts are out of scope for now — see [docs/roadmap.md](https://github.com/bimwright/rvt-mcp/blob/master/docs/roadmap.md).\n\n---\n\n## How a normal session looks\n\n1. Revit open with a model; plugin connected (ribbon).\n2. MCP client starts `rvt-mcp` / the installed server.\n3. Agent uses tools: query view/selection, create grids/rooms, sheets, MEP, export, … Lengths in **mm** at the tool boundary.\n4. Several writes in one undo step: `revit_batch_execute`.\n5. Multiple Revits running: `revit_list_available_targets` then `revit_switch_target` with a four-digit year (`2024`, not `R24`).\n\nWhen no typed tool fits:\n\n```text\nrevit_send_code_to_revit # C# body, compiled and run inside the plugin\n```\n\nThat tool is on by default (toolset `meta`). Strip it with `--read-only` or `--disable-toolbaker` if you do not want agents compiling code in the model.\n\n### ToolBaker (optional)\n\nDefault surface includes `revit_send_code_to_revit`. `revit_list_baked_tools` / `revit_run_baked_tool` need `--toolsets toolbaker` (or `--toolsets all`).\n\n**Adaptive bake** (suggest new tools from usage) is **off** unless you enable it. When on, repeated patterns can show up under `revit_list_bake_suggestions`; you accept or dismiss explicitly. Nothing ships itself into your ribbon without that step.\n\nUseful flags (also JSON / env — see [Configuration](#configuration)):\n\n| Goal | What to turn on |\n|------|------------------|\n| Learn tools from repeated **typed** calls | `--enable-adaptive-bake` |\n| Also cluster **`send_code`** bodies for suggestions | plus `--cache-send-code-bodies` (redacted; still local) |\n| Short-lived disk journal of send_code bodies | `persistSendCodeBodies` + TTL (default privacy keeps this off) |\n\nBake compile runs **inside Revit** via Roslyn — end users do not need Visual Studio. Details and privacy notes: [docs/bake.md](https://github.com/bimwright/rvt-mcp/blob/master/docs/bake.md).\n\n### Toast (optional)\n\nCompletion toast in Revit is **off** by default. Turn on with the ribbon **Toast** button, `enableToast` in config, or `BIMWRIGHT_ENABLE_TOAST=1`. Only finished calls are shown (no “in progress” toast). Capture success can show a thumbnail when the file sits under the path allowlist. Ribbon **Status** also prints toast + bake/privacy flags so you can see what is enabled without guessing.\n\n---\n\n## Architecture (short)\n\n```text\nMCP client (stdio)\n → RvtMcp.Server (.NET 8)\n → TCP (Revit 2022–2024) or Named Pipe (2025–2027)\n → Plugin shell (per year)\n → ExternalEvent → Revit API / transactions / undo\n```\n\nHandlers return plain DTOs — never live Revit objects on the wire.\n\n---\n\n## Tools\n\nCounts (without counting personal baked tools):\n\n| Mode | Tools | Notes |\n|------|------:|-------|\n| Default | **40** | `query` + `create` + `view` + `meta` |\n| `--toolsets all` | **229** | Full catalog |\n| `all` + adaptive bake | **232** | Adds 3 suggestion-lifecycle tools |\n\nTool names are MCP-facing as `revit_*`. Wire names between server and plugin stay unprefixed snake_case.\n\n**Default-on toolsets:** `query`, `create`, `view`, `meta`\n\n**Off unless you ask:** everything else (`export`, `geometry`, `mep`, `structural`, `toolbaker`, `modify`, `delete`, …). \nExample: `--toolsets query,view,meta` or `--toolsets all`. \n`--read-only` drops every write-capable toolset (including `create`).\n\n| Toolset | What it covers | Default |\n|---------|----------------|---------|\n| `query` | View, selection, filters, stats, parameters, relationships, worksets, groups/assemblies | on |\n| `create` | Grids, levels, rooms, line/point/surface-based elements, groups | on |\n| `view` | Create views, sheets layout helpers, capture image, crop/scale | on |\n| `meta` | Batch execute (max 20), multi-Revit targets, project info, purge unused (MVP), message, send_code | on |\n| `lint` | View naming patterns, firm-profile detect, warnings summary | off |\n| `schedule` | List/create schedules, fields, formulas, data | off |\n| `families` | Load/unload, types, instances, audit, export `.rfa` (project-side) | off |\n| `modify` | Operate/color elements, set parameters, change type, workset assign | off |\n| `delete` | Delete by id | off |\n| `annotation` | Tags, text, dimensions, regions, keynotes, checks | off |\n| `export` | PDF/DWG/IFC/NWC helpers, room data, and related export tools | off |\n| `mep` | Systems, connectors, networks, place terminals/fixtures, etc. | off |\n| `graphics` | View filters, overrides, visibility/phase | off |\n| `toolbaker` | list/run baked tools; suggestion tools only if adaptive on | off |\n| `sheets` | Sheets, titleblocks, revisions, renumber | off |\n| `materials` | Materials, appearance, assignment, takeoff | off |\n| `geometry` | BBox, measure, clash, volume/area, … | off |\n| `rooms` | Rooms/areas/spaces, finishes, separators | off |\n| `links` | Revit/CAD links, coordinate audit, acquire/publish coordinates | off |\n| `parameters` | Project/shared parameters | off |\n| `organization` | Saved selections, view templates | off |\n| `workflows` | Composite clash/audit/sheet/takeoff-style flows | off |\n| `structural` | Columns, beams, foundations, rebar, loads, … | off |\n| `kei` | Active KEI project DB path, query/write SQLite (WAL-safe), equipment import | off |\n\n### Representative tools\n\nNot a full dump of 200+ schemas — just anchors agents and humans use often:\n\n| Toolset | Tool | Role |\n|---------|------|------|\n| `query` | `revit_get_current_view_info` | Active view type, level, scale |\n| `query` | `revit_get_selected_elements` | Current selection |\n| `query` | `revit_ai_element_filter` | Category + parameter filter (mm) |\n| `query` | `revit_get_element_details` | Location, bbox, workset, phase, … |\n| `create` | `revit_create_grid` / `revit_create_level` / `revit_create_room` | Core layout |\n| `create` | `revit_create_point_based_element` | Doors, furniture, … from type id |\n| `view` | `revit_capture_view_image` | Raster capture (path allowlist) |\n| `meta` | `revit_batch_execute` | One `TransactionGroup` for several commands |\n| `meta` | `revit_list_available_targets` / `revit_switch_target` | Multi-Revit |\n| `families` | `revit_load_family_from_path` | Load `.rfa` into the project |\n| `links` | `revit_get_project_coordinate_system` / `revit_get_link_coordinate_system` | Host/link origins, sites, transforms, True North |\n| `toolbaker` | `revit_send_code_to_revit` | Escape hatch (C#) |\n| `toolbaker` | `revit_list_baked_tools` / `revit_run_baked_tool` | Personal accepted tools |\n| `toolbaker` | `revit_list_bake_suggestions` | Adaptive only |\n| `lint` | `revit_analyze_view_naming_patterns` | Naming outliers |\n\nGolden snapshots in tests pin the exact surface; if counts and code disagree, trust tests/code.\n\n---\n\n## Supported Revit versions\n\n| Revit | Plugin TFM | Transport |\n|-------|------------|-----------|\n| 2022–2024 | .NET Framework 4.8 | TCP |\n| 2025–2026 | .NET 8 (`net8.0-windows7.0`) | Named Pipe |\n| 2027 | .NET 10 (`net10.0-windows7.0`) | Named Pipe |\n\nCompile matrix covers all six shells. Runtime depth still varies by year — bake and custom C# should be rechecked on the years you care about.\n\n**Host:** full Revit desktop only. Revit Viewer is not a supported target.\n\n---\n\n## Security and privacy\n\n- Transport is local by default (loopback TCP / local named pipe).\n- Discovery files under `%LOCALAPPDATA%\\RvtMcp\\` include a per-session auth token.\n- Tool arguments are schema-checked before handlers run.\n- Errors returned to the model are sanitized (path leakage reduced).\n- `send_code` can run arbitrary C# in the Revit process — powerful and risky; disable toolbaker if that is unacceptable.\n- Adaptive bake, body cache, and TTL journals are **opt-in** and stay under the user profile. Defaults do not write raw send_code bodies to long-lived logs.\n\nMore: [SECURITY.md](https://github.com/bimwright/rvt-mcp/blob/master/SECURITY.md), [docs/bake.md](https://github.com/bimwright/rvt-mcp/blob/master/docs/bake.md).\n\n---\n\n## Configuration\n\nPrecedence, high wins: **CLI → env (`BIMWRIGHT_*`) →** `%LOCALAPPDATA%\\RvtMcp\\rvtmcp.config.json`.\n\n| Setting | CLI | Env | JSON |\n|---------|-----|-----|------|\n| Target year | `--target 2024` | `BIMWRIGHT_TARGET` | `target` |\n| Toolsets | `--toolsets query,create` | `BIMWRIGHT_TOOLSETS` | `toolsets` |\n| Read-only | `--read-only` | `BIMWRIGHT_READ_ONLY=1` | `readOnly` |\n| LAN bind (plugin) | — | `BIMWRIGHT_ALLOW_LAN_BIND=1` | `allowLanBind` |\n| ToolBaker surface | `--enable-toolbaker` / `--disable-toolbaker` | `BIMWRIGHT_ENABLE_TOOLBAKER` | `enableToolbaker` |\n| Adaptive bake | `--enable-adaptive-bake` / `--disable-adaptive-bake` | `BIMWRIGHT_ENABLE_ADAPTIVE_BAKE=1` | `enableAdaptiveBake` |\n| Cache send_code bodies (bake clusters) | `--cache-send-code-bodies` / `--no-…` | `BIMWRIGHT_CACHE_SEND_CODE_BODIES=1` | `cacheSendCodeBodies` |\n| Persist send_code journal | `--persist-send-code-bodies` / `--no-…` | `BIMWRIGHT_PERSIST_SEND_CODE_BODIES=1` | `persistSendCodeBodies` |\n| Journal TTL | `--persist-send-code-bodies-for 4h` | `BIMWRIGHT_PERSIST_SEND_CODE_BODIES_TTL` | `persistSendCodeBodiesUntil` |\n| Completion toast | ribbon **Toast** | `BIMWRIGHT_ENABLE_TOAST=1` | `enableToast` |\n\nAfter changing server flags, restart the MCP connection so the client picks up the new tool list.\n\n---\n\n## MCP clients\n\n| Client | Wiring |\n|--------|--------|\n| Claude Code | project `.mcp.json` or `~/.claude.json` |\n| Claude Desktop | `%APPDATA%\\Claude\\claude_desktop_config.json` |\n| OpenCode / Codex / Kilo | `install.ps1 -Client …` (scripted) |\n| Cursor / Cline / VS Code Copilot | documented JSON layouts |\n| Gemini CLI / Antigravity | `gemini mcp add` or settings JSON |\n\nInstaller auto-detect is usually enough; see [AGENTS.md](https://github.com/bimwright/rvt-mcp/blob/master/AGENTS.md) and `docs/mcp-config-*.md` when hand-editing.\n\n---\n\n## Repo layout\n\n```text\nrvt-mcp/\n├── src/\n│ ├── RvtMcp.sln\n│ ├── server/ # MCP server\n│ ├── shared/ # Handlers, transport, ToolBaker, toast, …\n│ ├── plugin-r22/ … r27/ # One shell per Revit year\n├── tests/ # xUnit + golden tool lists\n├── scripts/ # install / uninstall / package\n├── docs/ # roadmap, bake, testing\n├── AGENTS.md\n└── ARCHITECTURE.md\n```\n\n---\n\n## Development\n\n```bash\ndotnet test tests/RvtMcp.Tests/RvtMcp.Tests.csproj\ndotnet build src/server/RvtMcp.Server.csproj -c Release\ndotnet build src/plugin-r26/RvtMcp.Plugin.R26.csproj -c Release\n```\n\nClose Revit before building plugins (DLL lock). Plugin projects deploy into `%APPDATA%\\Autodesk\\Revit\\Addins\\\\RvtMcp\\` on a normal Debug/Release build.\n\n```powershell\npwsh scripts/stage-plugin-zip.ps1 -Config Release\n```\n\nContribution norms and snapshot rules: [CONTRIBUTING.md](https://github.com/bimwright/rvt-mcp/blob/master/CONTRIBUTING.md).\n\n### Maturity\n\nUsable, not sacred. CI builds the six plugin shells and server tests. Runtime coverage is strongest on mid-range years; treat production models carefully and verify on *your* Revit build. Fresh-machine checklist: [docs/testing/fresh-install-checklist.md](https://github.com/bimwright/rvt-mcp/blob/master/docs/testing/fresh-install-checklist.md).\n\n---\n\n## More docs\n\n| Doc | Topic |\n|-----|--------|\n| [AGENTS.md](https://github.com/bimwright/rvt-mcp/blob/master/AGENTS.md) | Agent install protocol |\n| [ARCHITECTURE.md](https://github.com/bimwright/rvt-mcp/blob/master/ARCHITECTURE.md) | Processes, transport, DTO rules |\n| [docs/bake.md](https://github.com/bimwright/rvt-mcp/blob/master/docs/bake.md) | Adaptive bake and body privacy |\n| [docs/roadmap.md](https://github.com/bimwright/rvt-mcp/blob/master/docs/roadmap.md) | Near-term hardening and non-goals |\n| [docs/kei-equipment-import.md](https://github.com/bimwright/rvt-mcp/blob/master/docs/kei-equipment-import.md) | KEI SQLite tools (`--toolsets kei`) |\n| [CHANGELOG.md](https://github.com/bimwright/rvt-mcp/blob/master/CHANGELOG.md) | Release notes |\n\n---\n\n## bimwright\n\nSame house style across AEC hosts:\n\n- [rvt-mcp](https://github.com/bimwright/rvt-mcp) — Revit \n- [dwg-mcp](https://github.com/bimwright/dwg-mcp) — AutoCAD \n- [nwd-mcp](https://github.com/bimwright/nwd-mcp) — Navisworks \n- [ipt-mcp](https://github.com/bimwright/ipt-mcp) — Inventor \n- [bim-wiki](https://github.com/bimwright/bim-wiki) — Vietnamese-first BIM notes \n\n---\n\n## License\n\nApache-2.0 — [LICENSE](https://github.com/bimwright/rvt-mcp/blob/master/LICENSE).\n\nRevit and Autodesk are trademarks of Autodesk, Inc. bimwright is independent and not affiliated with Autodesk.\n","changelogMarkdown","videoKey","requiredSecretsJson","publishedAt","priceCents","trialDays",0,"upstream",{"_104":105,"_106":107,"_108":109,"_110":111,"_112":66,"_113":114},"requiredSecrets",[],"tags",[94,95,96,97,98,99,100,101,102,103],"assets",[],"stats",{"_92":81,"_93":81},"ratingAvg","reviewCount","aec","ai","autodesk","bim","claude","claude-code","csharp","dotnet","revit","stdio","topics",[94,95,96,97,98,99,100,101,120,121,102,103],"license","Apache-2.0","language","C#","registryName","io.github.bimwright/rvt-mcp","homepage","packages",[115],{"_116":117,"_118":119,"_71":72},"registryType","nuget","identifier","Bimwright.Rvt.Server","mcp","model-context-protocol","ENV",{"_124":125,"_126":127,"_128":129},"ENVIRONMENT","production","TURNSTILE_SITE_KEY","0x4AAAAAAB8-rEI2gNDf_QhU","SENTRY_DSN","https://45fd1229f78089d5c3ee78be128030e1@o4510583261757440.ingest.de.sentry.io/4510584253448272"]