CadPlot MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CADPLOT_CONFIG | Yes | Path to the configuration YAML file. Set to $PWD\config.yaml before running. | |
| CADPLOT_PIPE_NAME | No | Named pipe used by the Python client and AutoCAD plugin. Must be the same on both sides and match [A-Za-z0-9._-]{1,128}. Only needed when running multiple AutoCAD versions. | cadplot-mcp |
| CADPLOT_AUTOCAD_PROGID | No | COM ProgID for AutoCAD, e.g. AutoCAD.Application.20.1 for 2016 or AutoCAD.Application.25.0 for 2025. Refuses ambiguous/foreign ProgIDs. | |
| CADPLOT_ENABLE_PUBLISH | No | Set to 1 to enable publish commands. Must be set before starting AutoCAD. | 0 |
| CADPLOT_WORKSPACE_ROOT | No | Trusted workspace root that must match workspace_root in the configuration file. Set before launching AutoCAD for staged-job validation. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
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
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| validate_environmentA | Validate configuration, allowed roots, and the read-only AutoCAD COM connection. |
| get_autocad_plugin_statusA | Check the installed AutoCAD plug-in through its read-only local named-pipe command. |
| scan_drawingsA | List DWG files under an explicitly allowed project root without opening them. |
| inspect_drawingA | Inspect one explicit allowed DWG/DWT read-only: layouts, plot settings, and frames. |
| inventory_office_resourcesA | Inventory exact frame/layout/page-setup/plot resource names; never approves or writes. |
| create_publish_planA | Inspect one DWG and return a deterministic dry-run plan; never modifies or plots it. |
| create_batch_publish_plansC | Inspect a restartable page of DWGs; one drawing failure does not stop the batch. |
| preview_publish_planA | Validate a ready dry-run plan with AutoCAD; never edits, saves, or plots the DWG. |
| stage_publish_jobA | Revalidate an approved plan and copy its DWG into an isolated workspace; never plots. |
| stage_publish_batchA | Stage up to 20 explicit DWG/plan-ID approvals; never plots or edits originals. |
| audit_publish_outputsA | Inspect expected PDFs and return hashes/statuses; never modifies the job or outputs. |
| validate_staged_jobA | Cross-check a staged manifest with the local plug-in; never queues or plots the job. |
| queue_publish_jobA | Queue an exact approved staged plan for PDF publishing; may create output PDFs. |
| cancel_publish_jobA | Durably cancel one exact pending job; never interrupts a running AutoCAD plot. |
| get_publish_job_statusA | Read a queued publish job state; never edits drawings or output files. |
| get_publish_batch_statusA | Read up to 20 live job states and one final queue-capacity sample; never writes. |
| read_publish_receiptA | Read persistent terminal publish evidence after AutoCAD restarts; never writes files. |
| create_publish_operations_reportA | Summarize staged jobs as a restartable page and suggest safe next actions; never writes. |
| queue_publish_batchA | Queue up to 20 approvals; capacity-full items are deferred for an exact retry. |
| match_paper_profileB | Match a frame's paper-size label to a configured office paper profile. |
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 20 tools
Most tools have clear, distinct purposes (inspect, plan, stage, queue, status, cancel, report), and batch variants are explicitly differentiated by plural names and descriptions. A few similar verbs like 'validate_environment' and 'validate_staged_job' or 'inspect_drawing' and 'inventory_office_resources' could cause minor selection uncertainty, but descriptions resolve the boundaries.
The naming follows a consistent verb_noun pattern throughout (inspect_drawing, scan_drawings, create_publish_plan, stage_publish_job, queue_publish_batch, cancel_publish_job, read_publish_receipt). All verbs are lowercase with underscores, and the pattern is predictable across the full set.
At 20 tools, the server sits in the 'heavy but justifiable' range. The detailed publishing pipeline requires many steps, but the count is above the typical well-scoped 3-15 and feels close to the boundary where consolidation (e.g., merging plan and preview) might improve usability.
The tool set covers the full lifecycle from inspection and planning through staging, queuing, status monitoring, cancellation, and receipt reading, plus environment validation and resource inventory. Minor gaps exist, such as no batch cancellation or direct job modification, but these are not critical for the core publishing workflow.