🏗️ Revit MCP Server

Created By
SamllPigYanDonga year ago
Revit MCP. A Model Context Protocol server for Revit integration, enabling seamless communication between Claude AI and Autodesk Revit.
Overview

What is Revit MCP?

Revit MCP is a Model Context Protocol server designed for seamless integration between Claude AI and Autodesk Revit, enabling real-time communication and interaction with Revit models.

How to use Revit MCP?

To use Revit MCP, install the necessary dependencies, configure the server settings, and run the server to establish a WebSocket connection with Revit. You can then interact with Revit models through the provided functionalities.

Key features of Revit MCP?

  • Real-time access to Revit model information via WebSocket.
  • Element querying and filtering capabilities.
  • View and level management for better navigation.
  • Robust error handling with fallback to mock data.

Use cases of Revit MCP?

  1. Accessing real-time model data for analysis and reporting.
  2. Querying specific elements within a Revit model for detailed inspection.
  3. Managing views and levels to enhance user experience in model navigation.

FAQ from Revit MCP?

  • What are the prerequisites for using Revit MCP?

You need Node.js (v14 or higher), npm, Autodesk Revit (2023 or later), and the Revit WebSocket Plugin.

  • How do I install Revit MCP?

Install dependencies using npm install, then build the server with npm run build.

  • What happens if the connection to Revit fails?

The server automatically falls back to mock data to ensure continued operation.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
SamllPigYanDong
Star
2
Language
TypeScript
License
MIT license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

2 days ago