Model Context Protocol server that wraps the CADLens REST API.
Connect Cadlens to Claude, Cursor or any other MCP client and it stops being a tab you switch to. Model Context Protocol server that wraps the CADLens REST API. The cadlens mcp server is what makes that connection.
Get an API key from the Cadlens dashboard first — keys start with cadl_ and are created in the dashboard for free.
@cadlens/mcp-server on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
cadlens_parse_file — Upload a local CAD file, poll until parsed (5 min budget), return summarycadlens_parse_url — Download a CAD file from a URL, then parse it like parse_filecadlens_get_job — Cheap status check (PENDING / PROCESSING / COMPLETED / FAILED)cadlens_get_result — Fetch parsed content. mode: summary (default), entities_by_type, entities_on_layer, fullcadlens_refresh_image_url — Re-fetch the 1h presigned PNG URL without re-downloading the full resultcadlens_list_jobs — The 100 most recent jobs for the configured API keycadlens_delete_job — Delete a job and its S3 artifacts. IrreversibleConfiguration is passed through the environment: CADLENS_API_KEY, WEBHOOK_PORT, WEBHOOK_PUBLIC_URL. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Cadlens's toolset — cadlens_parse_file, cadlens_parse_url, cadlens_get_job and 4 more — is a fair guide to whether it matches your workflow. It is maintained by cadlens-co; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| cadlens_parse_file | Upload a local CAD file, poll until parsed (5 min budget), return summary. |
| cadlens_parse_url | Download a CAD file from a URL, then parse it like parse_file. |
| cadlens_get_job | Cheap status check (PENDING / PROCESSING / COMPLETED / FAILED). |
| cadlens_get_result | Fetch parsed content. mode: summary (default), entities_by_type, entities_on_layer, full. |
| cadlens_refresh_image_url | Re-fetch the 1h presigned PNG URL without re-downloading the full result. |
| cadlens_list_jobs | The 100 most recent jobs for the configured API key. |
| cadlens_delete_job | Delete a job and its S3 artifacts. Irreversible. |
{
"mcpServers": {
"cadlens": {
"command": "npx",
"args": ["-y", "@cadlens/mcp-server"],
"env": {
"CADLENS_API_KEY": "cadl_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| CADLENS_API_KEY | Credential the server authenticates with. | Yes |
| WEBHOOK_PORT | Configuration value read at startup. | Optional |
| WEBHOOK_PUBLIC_URL | Endpoint or connection string the server talks to. | Yes |
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.