🏗️ 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
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

11 hours ago
Voyei

an hour ago