
IFC MCP
io.github.flinker-app由 GitHub 账号 flinker-app 发布v0.2.0更新于 Oct 24, 2026
Local IFC/BIM MCP server with IfcOpenShell Python in Pyodide and an IFC viewer.
概览
让助手在本地检查并创建 IFC/BIM 建筑模型、生成报告,并在本地 IFC 查看器中打开模型。
- 可以做什么
- IFC MCP 在本地 Pyodide 运行时中通过 IfcOpenShell 执行 IFC 逻辑。它可以读取 IFC 文件、汇总模型、统计墙体、门、窗和空间等构件,并找出缺失的名称、分类或可疑的属性值。它还能创建简单的 IFC 文件、生成 CSV 式报告、打开本地 IFC 查看器并应用 BCF 视点。生成的报告、BCF 文件和 IFC 文件以临时本地下载链接的形式返回。
- 适用场景
- 当你处理 IFC/BIM 模型,并希望助手在不离开对话的情况下检查、校验或汇总模型,或生成小型 IFC 文件和房间面积报告时,适合使用。它面向支持本地 STDIO MCP 服务器的桌面客户端。
- 运行要求
- 桌面机器上需安装 Node.js 20 或更高版本(含 npx)。服务器通过 npx ifc-mcp 以 STDIO 方式在本地运行;未声明任何账户、API 密钥或环境变量。打开本地查看器或下载链接需要浏览器。
安装
在 SourceWeft 中
- 打开 控制台中的 IFC MCP,将其添加到工作区。
- 为需要使用其工具的对话启用该服务。
Desktop only,通过 STDIO。 STDIO 服务会启动本地进程,因此需要 SourceWeft 桌面宿主。
其他 MCP 客户端
参照 仓库 中的启动说明。
README
IFC MCP
IFC MCP lets your AI assistant inspect IFC/BIM files, create IFC files, create reports, open IFC models in a viewer, and apply BCF viewpoints.
How It Works
After installation, ask your AI client in normal language. The AI client starts IFC MCP when it needs the IFC tools and sends your request to the local server. IFC MCP reads IFC files locally, runs the needed IFC logic in a local Pyodide runtime with IfcOpenShell, and returns the answer to the chat.
[Watch IFC MCP with Claude demo on YouTube]
Good example prompts:
Open examples/sample.ifc and summarize the model.Count the walls, doors, windows, spaces, and property sets in examples/sample.ifc.Find missing names, classifications, and suspicious property values in this IFC file.Create a CSV room-area report from this IFC file.Create a simple IFC file with one building, one storey, and four walls.Open the IFC viewer and show examples/sample.ifc.Apply C:\path\to\viewpoint.bcfzip in the open IFC viewer.Clear the IFC viewer.
If IFC MCP creates a report, BCF file, or new IFC file, it returns a local download link. If you ask to view a model, IFC MCP opens a local viewer link. If your AI client does not open that link automatically, open it in your browser.
Large IFC files can take more than a minute to process. Cancelling a request does not stop Python already running; wait for it to finish before trying again.
Installation
1. Prerequisites
Install Node.js 20 or newer from the official Node.js download page. Choose the LTS version for your operating system, run the installer, then reopen the app where you want to use IFC MCP.
IFC MCP uses npx, which is included with Node.js. If your app later says
node or npx is not found, reinstall Node.js LTS and reopen the app.
2. Choose your client
ChatGPT desktop app
ChatGPT desktop supports local MCP servers over STDIO.
- Open the ChatGPT desktop app.
- Open
Settings. - Select
Plugins, thenMCPs. - Click
Add. If prompted for a server type, chooseSTDIO. - Enter:
- Name:
ifc-mcp - Command to launch:
npx - First argument:
-y - Second argument:
ifc-mcp
- Name:
- Leave the environment variable fields empty and save the server.
- Restart the ChatGPT desktop app.
- Start a new chat, type
/mcp, and confirm thatifc-mcpis connected.
For more detail, see OpenAI's MCP documentation.
Claude Desktop
Option 1: Use the Claude Desktop UI
- Open Claude Desktop.
- Open
Settings. - Open
DeveloperorDesktop appdeveloper settings. - Click
Edit Configif that button is available. This opens the Claude Desktop MCP config file. - Paste the JSON below, save the file, then fully quit and reopen Claude Desktop.
If the file already contains JSON, add only the ifc-mcp entry inside the
existing mcpServers object. Do not create a second mcpServers object.
Option 2: Open the config file directly
Use this only if you do not see Edit Config in Claude Desktop:
- Windows:
%APPDATA%\Claude\claude_desktop_config.json - macOS:
~/Library/Application Support/Claude/claude_desktop_config.json
Paste the same JSON from Option 1, save the file, then fully quit and reopen Claude Desktop.
Check
To check the setup, open Claude Desktop, start a new chat, click the + button
near the chat box, and look for Connectors. IFC MCP should appear there after
Claude Desktop has restarted. You should see the tools listed in the
How It Works section above.
For more detail, see Claude's local MCP server guide.
VS Code Copilot
Option 1: Use the install button
This opens VS Code and adds IFC MCP.
If VS Code asks whether you trust the server, accept it. Reload VS Code if the tools do not appear. Open Chat and use the tools/configure-tools button to see the IFC MCP tools.
Option 2: Add .vscode/mcp.json manually
Reload VS Code after saving the file.
Open Chat and use the tools/configure-tools button to see the IFC MCP tools.
For more detail, see the VS Code MCP server docs.
VS Code Codex
Option 1: Use the Codex settings UI
- Open VS Code.
- Open the Codex panel.
- Open Codex settings.
- Select
MCP servers. - Click
Add server. - Enter:
- Name:
ifc-mcp - Command:
npx - Arguments:
-y ifc-mcp
- Name:
- Save the server.
- Reload VS Code or start a new Codex session.
- Check that the IFC MCP tools are available in the new Codex session.
Option 2: Use the terminal command
- Open
Terminal -> New Terminalin VS Code. - Paste and run:
- Reload VS Code or start a new Codex session.
- Check that the IFC MCP tools are available in the new Codex session.
For more detail, see the Codex MCP docs.
VS Code Claude Code
Option 1: Use a project JSON file
- Open your project in VS Code.
- Create or edit
.mcp.jsonin the project root. - Add this JSON and save the file:
- Reopen Claude Code in VS Code.
- Type
/mcpand approve the project server if Claude asks. - Check that
ifc-mcpis connected.
Option 2: Use the terminal command for all projects
Then reopen Claude Code in VS Code, type /mcp, and check that ifc-mcp is
connected.
If the claude command is not found, install Claude Code first.
For more detail, see the Claude Code VS Code docs and Claude Code MCP docs.
Other MCP clients
Add this server entry to your MCP client config:
Restart the MCP client after saving the config.
For more detail, see the Model Context Protocol docs.
Use Your Own Viewer
If your app already has an IFC viewer, you can reuse IFC MCP's normal tool
interface and apply viewer actions in your app instead of opening the default
local viewer. The MCP client still calls tools like show-ifc-file and
set-bcf-view; your app only defines what those viewer tools do.
Node MCP server
Provide handlers that receive local file paths. Replace the functions below with your app's viewer actions:
Return MCP tool results from your handlers: content contains feedback, and
isError: true indicates failure.
Browser app
Pass files selected in your app and callbacks for your existing viewer.
Here, file is a selected IFC File, and viewer is your viewer instance:
File callbacks receive a filename and Uint8Array bytes. The BCF callback
must return an MCP tool result describing whether the viewpoint was applied.
Use host.tools for the tool definitions and host.getGeneratedFiles() for
generated downloads. Call host.clearFiles() when those downloads are no longer needed.
Local Development
For local development from this checkout:
The workspace includes .vscode/mcp.json, so VS Code can run the server from
this checkout.
Security
IFC MCP keeps the IFC work on your own machine. It reads your IFC files locally, runs the IFC analysis locally, and opens a local viewer. It does not publish the viewer to the public internet.
Generated reports, BCF files, and IFC files are temporary local download links. IFC MCP does not write generated output files into your project folder by default.
Use IFC MCP only with IFC/BIM files and project folders you trust. It can read the files you ask it to use, and incorrect or misleading model data can lead to wrong reports or generated IFC files.
来源:README.md,提交 e28a02b
工具
0版本历史
2- v0.2.0最新Sep 24, 2026
- v0.1.17Sep 16, 2026
评分
已满足适用检查项的 50%
该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。
- 近 30 天内可连通25 分
请保持端点能够响应 MCP 握手;SourceWeft 每 30 天探测一次。
- 已声明认证方式10 分
请在注册中心条目中声明凭据请求头,或保持端点能够响应探测,以便判定其认证方式。
- 已列出工具15 分
请让服务器在无凭据时响应 tools/list,或发布可在沙箱中无凭据启动的软件包。
- 描述必需15 分
- 图标10 分
- 文档15 分
- 许可证10 分