Codesign vs Revit MCP

A side-by-side look at the Codesign and Revit MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Codesign logoCodesignArchitecture & Design · Local subprocess (stdio)A real design engine for your AI agent: generate designs and print-ready PDFs, over MCP.49FairAuth: not declaredRevit MCP logoRevit MCPArchitecture & Design · Local subprocess (stdio)MCP Server for Revit integration - AI-Powered Revit Control68GreatAuth: no auth required

Verdict: choose Codesign for architecture & design work as a local process; choose Revit MCP for architecture & design as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Codesign logoChoose Codesign when

  • You need dedicated capabilities in the Architecture & Design domain.
  • You prefer a local stdio subprocess transport.
Explore Codesign

Revit MCP logoChoose Revit MCP when

  • You need dedicated capabilities in the Architecture & Design domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: No auth required.
  • You want tools like add_pipe_cap, adjust_section_datums, align_titleblocks_on_sheets.
Explore Revit MCP

Feature & specification comparison

Rows where the two servers differ are marked.

SpecCodesign logoCodesignRevit MCP logoRevit MCP
CategoryArchitecture & DesignArchitecture & Design
Quality signal49/100 · Fair68/100 · Great
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNot declaredNo auth required
PricingFreeFree
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars42103
Directory activity 0 views 0 installs 0 upvotes 6 views 0 installs 0 upvotes
ToolsNot listed167

Tools & capabilities

Codesign tools

No tool names declared yet. Check the project README from the listing page.

Revit MCP tools 167

  • add_pipe_cap在管件的未連線端安裝管帽或法蘭。自動尋找開放的接頭並連接。
  • adjust_section_datums自動調整剖面視圖的網格線 (Grids) 與樓層線 (Levels) 2D 範圍與氣泡顯示。
  • align_titleblocks_on_sheets批次將多個 sheet 上的 titleblock 移動到同一個 anchor 座標。可用『referenceSheetNumber』指定要拷貝某張 sheet 上 titleblock 的位置,或用『referencePositionMm』直接給絕對座標。anchor 決定要對齊 titleblock bbox 的哪個角(top-left / top-right / bottom-left / bottom-right / center)。建議先 dryRun=true 預覽 delta,確認後再實際執行。觸發條件:使用者提到 titleblock 對齊、圖框對齊、把所有 sheet 圖框對齊到 X、change_element_type 後圖框沒跟著移動、align titleblock、move titleblock to match。
  • align_view_cropbox_to_element將指定視圖的 CropBox 對齊到目標元素(如 Detail Group 圖框)的 BoundingBox。保留原 Z 軸深度與 CropBox Transform。viewId 不指定時使用 active view。
  • analyze_beam_penetration分析特定結構梁上的套管穿孔。回傳精確的幾何數據,如距離柱心長度、梁深度、開孔直徑等。
  • analyze_corridor_width分析走廊寬度。使用 Revit 端的房間邊界線段找出平行牆對,回傳實測寬度、最小寬度與各區段檢討結果。
  • analyze_floor_slopes分析樓板頂面排水坡度:以 Solid→PlanarFace 法向量與 Z 軸夾角計算每片朝上頂面的坡度百分比,回傳每片樓板的 Min/Max 坡度,並可回寫至指定參數(預設 Comments)。未指定 elementIds 時自動收集 Function=Exterior 的樓板。
  • analyze_smoke_detectors偵煙探測器設置分析:掃描當前視圖的探測器、空調出風口(FCU/冷風機)、房間,回傳各探測器的距出風口距離、距牆/樑距離、距天花板距離,以及各房間的探測器數量與樑區格數。供 JS 端進行五項法規判定。
  • analyze_tall_partition_roomsFind rooms on target levels that share or contain TYPE partition walls taller than a threshold. Uses room boundary segment ElementIds so shared room-to-room walls are assigned to both rooms, and can add upward ray evidence from room bottom to floor underside.
  • apply_panel_pattern將面板排列模式套用到帷幕牆。需要類型映射表和排列矩陣。
  • arrange_viewports_on_sheet依指定順序排列圖紙上的視埠(僅限 DraftingView)。支援水平或垂直排列,邊緣對齊(edge-to-edge)。第一個視埠的位置作為錨點。可用 viewNames(view 名稱陣列)或 viewportIds(視埠 ID 陣列)指定順序,二擇一。
  • assign_existing_material將既有材質(透過名稱查找)套用到指定的 Type。不建立新材質。用於復原或批次指派既有材質(例如把 9 個柱子從 'White_MCP' 改回 '鋼 AISI 1015')。
  • +155 more on the listing page

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

Codesign

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "codesign": {
      "command": "npx",
      "args": [
        "-y",
        "@imgly/codesign-mcp@0.5.1"
      ]
    }
  }
}

Revit MCP

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "revit-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@shuotao/revit-mcp-server"
      ]
    }
  }
}

Frequently asked questions

Codesign is categorized under Architecture & Design and uses a local stdio subprocess. Revit MCP belongs to Architecture & Design and uses a local stdio subprocess. Pick Codesign for architecture & design work and Revit MCP for architecture & design.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.

Codesign is listed as free. Revit MCP is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add codesign and revit-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Codesign has a quality signal of 49/100 (Fair) with 0 views, 0 installs and 42 GitHub stars. Revit MCP has 68/100 (Great) with 6 views, 0 installs and 103 GitHub stars.