MCP Server
Paracore-Gen is the generalist Model Context Protocol (MCP) server for Paracore. It lets AI coding tools — Claude Desktop, Cline in VS Code, Cursor, and any other MCP-compatible client — interact with Revit directly: explore your model's schema and execute C# scripts, with you in control at every step.
Install Paracore-Gen
Paracore-Gen ships as its own installer, separate from the Revit add-in.
Run Paracore-Gen-v2.0.0.exe. It installs the server to:
%APPDATA%\paracore-data\mcp-servers\paracore-gen.exe
which is C:\Users\<YourName>\AppData\Roaming\paracore-data\mcp-servers\paracore-gen.exe. Use that full path in the client configs below.
Prerequisites
- The Paracore Revit Add-in must be installed (v4.8.0).
- The Paracore Server toggle in the Revit ribbon must be On.
- Revit must be running with a document open.
The Paracore Desktop App is not required for MCP usage — the MCP server talks directly to the Revit Add-in. However, having the Desktop App is useful for experimenting with agent-generated REPL snippets, viewing charts, and managing your script library.
Claude Desktop
-
Open or create the Claude Desktop configuration file:
-
Windows Store version:
%LOCALAPPDATA%\Packages\Claude_pzs8sxrjxfjjc\LocalCache\Roaming\Claude\claude_desktop_config.json -
MSI/Installer version:
%APPDATA%\Claude\claude_desktop_config.json
-
-
Add the
paracoreserver entry:
{
"mcpServers": {
"paracore": {
"command": "C:\\Users\\<YourName>\\AppData\\Roaming\\paracore-data\\mcp-servers\\paracore-gen.exe"
}
}
}
- Restart Claude Desktop. You should see a hammer icon in the chat input — Paracore tools are now available.
Verify It's Working
In Claude Desktop, ask: "List the wall types in my Revit model." If Claude can explore your model, the MCP connection is active.
Cline (VS Code)
-
Open VS Code with Cline installed.
-
Open or create the Cline MCP settings file at:
%APPDATA%\Code\User\globalStorage\saoudrizwan.claude-dev\settings\cline_mcp_settings.json -
Add the
paracoreserver entry:
{
"mcpServers": {
"paracore": {
"autoApprove": [
"ping",
"execute_dynamic_query",
"search_schema",
"read_extension_methods"
],
"disabled": false,
"timeout": 60,
"type": "stdio",
"command": "C:\\Users\\<YourName>\\AppData\\Roaming\\paracore-data\\mcp-servers\\paracore-gen.exe",
"args": [],
"env": {}
}
}
}
- Save and restart Cline. Paracore tools will appear in Cline's tool list.
Cursor
- Open Cursor.
- Go to Settings → MCP and add a new MCP server.
- Set the command to
C:\Users\<YourName>\AppData\Roaming\paracore-data\mcp-servers\paracore-gen.exe. - Paracore tools will appear in Cursor's agent panel.
Available Tools
Once connected, the MCP server provides these tools to the AI client:
| Tool | Description |
|---|---|
ping | Verify the connection to Revit — it distinguishes "Revit is closed" from "the server is toggled off". |
get_context | The current project, active view, selection and levels — so "the walls" or "this level" is not a guess. Read-only. |
pick_object | Ask you to click an element in Revit and get it back. ⚠ Blocks until you pick or press Escape. |
export_view | Render a Revit view to an image so the agent can see the model. |
explore_revit_data | Runs read-only C# snippets to inspect your Revit model — parameters, categories, element properties. Results are summarized to avoid token flooding. |
execute_dynamic_query | Generates and executes C# code in Revit. Requires your approval before running — the AI cannot mutate your model without confirmation. |
search_schema | Fast parameter lookup from an in-memory cache. Returns parameter names, storage types, and type vs instance classification. |
read_extension_methods | Returns Paracore's fluent DSL reference so the AI knows which extension methods are available (with fuzzy keyword search). |
The MCP server also exposes Paracore's DSL documentation as MCP Resources — the AI client can read paracore://extension-methods and paracore://repl-guide to learn the correct syntax before generating code.
A Note on the In-App Agent
Paracore's in-app AI agent was retired in v4.7.0. MCP clients (Claude Desktop, Cursor, Cline) provide a far better harness — parallel tool calls, structured output, and skill-based resource loading. For an editor-side workflow, use the AI Script Generation path in VS Code instead.
Troubleshooting
| Problem | Solution |
|---|---|
| Tools don't appear in Claude Desktop | Check the JSON path in claude_desktop_config.json — use double backslashes (\\). Make sure the file is valid JSON (trailing commas will break it). |
| MCP server starts but can't reach Revit | Ensure Revit is running with a document open and the Paracore Server toggle is On. |
explore_revit_data returns empty results | The document must have elements loaded. Open a view with model elements visible. |