revit_export_ifc — Revit MCP MCP Tool
revit_export_ifc
(revit export ifc) is one of 8 tools on the
Revit MCP
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call revit_export_ifc from your client
- Claude Code Revit MCP revit_export_ifc run in your project directory
- Claude Desktop Revit MCP revit_export_ifc ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Revit MCP revit_export_ifc ~/.cursor/mcp.json
- VS Code Revit MCP revit_export_ifc .vscode/mcp.json
- Zed Revit MCP revit_export_ifc ~/.config/zed/settings.json
- Windsurf Revit MCP revit_export_ifc ~/.codeium/windsurf/mcp_config.json
- Cline Revit MCP revit_export_ifc ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Revit MCP revit_export_ifc ~/.gemini/settings.json
- Grok Revit MCP revit_export_ifc .mcp.json (in your project root)
- ChatGPT Revit MCP revit_export_ifc Settings → Connectors → Advanced → Developer mode
- Claude.ai Revit MCP revit_export_ifc Settings → Connectors → Add custom connector
- LangChain Revit MCP revit_export_ifc pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http revit-mcp https://revit-mcp.itmartin24.workers.dev/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.