OmniBridge MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
OmniBridge connects you to the CAD, BIM and 3D apps running on the user's PC. You work by sending short scripts that run inside (or directly against) the app.
Start every task with cad_apps to see which apps are connected.
Read cad_skill(app) before your first script for an app: it tells you the script
language, the names already defined for you, the units, and the traps.
Use cad_read for scripts that only inspect. Use cad_modify for scripts that change
the model; the user's client may ask them to approve each one.
Keep scripts small, return data with result = ..., and check the outcome with a
read or cad_screenshot before you tell the user it is done.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| cad_appsA | List every app OmniBridge supports and whether it is reachable right now. Call this first. An app is usable when its state is "connected" or "running".
When the state is "running, bridge not loaded", tell the user the |
| cad_skillA | Return the scripting guide for one app: language, predefined names, units, how to return data, common recipes and traps. Read it before scripting an app. |
| cad_readA | Run a script that only INSPECTS the app's open model. Nothing may be changed. app: an id from cad_apps, for example "blender", "autocad", "revit".
code: the script, in the language given by cad_skill(app). Set |
| cad_modifyA | Run a script that CHANGES the app's open model (create, edit, delete, save). Where the app supports it the whole script becomes one undo step, named by
|
| cad_screenshotA | Capture the app's current viewport as an image so you can check your work. Not every app supports this. When it fails, export an image with a script instead. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool has a clearly distinct role: discovery, documentation, read-only execution, modifying execution, and visual verification. The read/modify split is explicitly differentiated by intent and side effects, leaving little chance of misselection.
All tools share a consistent 'cad_' namespace and are concise and readable. However, the suffixes mix nouns (apps, skill, screenshot) with verbs (read, modify), so the pattern is not a pure verb_noun convention.
Five tools is well-scoped for a CAD bridge: discover apps, read the scripting guide, inspect, modify, and visually verify. Each tool clearly earns its place with no redundant surface area.
The surface covers the full core workflow: app availability, scripting guidance, read-only inspection, model mutation with undo support, and screenshot verification. No obvious lifecycle gaps remain, and fallback paths are noted where capabilities vary by app.