MCP and plug-ins
Adam MCPBeta
Connect your AI client to professional CAD and CAE applications through Adam.
Adam MCP connects your AI client to professional CAD and CAE applications. Keep the conversation in ChatGPT, Codex, Grok, or another supported client while it inspects a connected application, edits the native model, and checks the result through Adam's tools. Tasks preserve the brief, history, and output files across operations.
https://adam.new/mcp
ChatGPT and Codex use https://adam.new/mcp/chatgpt, the same endpoint as the packaged Adam plug-in. Both endpoints expose the named native application tools. Follow the client-specific setup.
Connect a client
Set up ChatGPT, Claude, Claude Code, Codex, Cursor, or another MCP client.
Adam plug-in
Learn about the private preview package, workspace browser, and CAD viewer.
Capabilities and permissions
Check what your connection can read, change, and execute.
Use tools from your client
Let your client control individual tools inside an Adam task.
Choose how work runs
| Mode | Who directs the work | What happens in Adam |
|---|---|---|
| Use Adam's tools from your client | The AI client you are using | Your client calls named tools in a task you own, including tools for supported connected CAD and CAE applications. Each direct call runs without an Adam agent loop. |
| Delegate to Adam | Adam's agent | When you ask to delegate, your client starts or continues an Adam task. Adam works asynchronously and may ask for input. |
Both modes keep work in an Adam task with history, files, and project context. You can continue the same task across clients. Wait for active work to finish before switching who controls the next operation.
Creating an empty task for client-driven work does not start inference or provision compute. Executing tools or delegating work can consume Adam usage. Direct tool execution requires an additional permission with broad access to Adam's execution environment.
Start with a connection check
After connecting, try this before starting work:
Check my Adam connection. Report the selected workspace and granted permissions. If allowed, list my paired computers, the CAD and CAE applications they report, and each application's connection status. Keep this read-only and do not create a task or run an engineering tool.
The result should identify the intended workspace and distinguish account access from application readiness. Use adam_fusion_status for Fusion's live add-in, and the integration connection for Onshape or Arena. Those workflows do not require a paired-computer ID. Signing in to MCP does not install or pair a desktop CAD application. Set up the application's Adam integration and keep the required application, license, and connection available. A missing application connection does not prevent browsing existing tasks or files.
Work in your connected application
Use Adam's tools to inspect the part currently open in SOLIDWORKS on my connected computer. Report its units and main dimensions, then wait for my edit request. You drive the tools directly; do not delegate to an Adam agent.
The client checks the computer and application, reuses or creates one task for the request, and calls the application's named tools. Later edits continue in that same task. Native files stay in the application unless you request an export; exported files can be brought back to the conversation. See direct tool execution for application coverage and result handling.
Delegate an engineering task
Start an Adam task to review a design brief for a compact two-stage gearbox. Identify the requirements needed before modeling, the main design risks, and the checks needed to validate a design. Use an available Adam model and keep me updated until the task finishes or needs my input.
Clients with MCP Tasks support can monitor Adam's work automatically. Other clients can check the existing task when you ask. If Adam requests input, answer the question or approval in that task, then continue it. Reuse the task rather than starting a duplicate when you return later.
Open tasks and results
Ask to open my Adam projects and tasks or show this Adam task when you want a panel. Clients with MCP Apps support can display the workspace browser or task conversation, including supported questions, approvals, and files. Starting or checking a task does not automatically open a panel. Clients without these interfaces can still use the ordinary MCP tools.
For output files, use the client's native file resources for text, source code, images, and PDFs. Ask to show a CAD model to open Adam's interactive viewer in a compatible client. Adam-stored models support STEP, STL, IGES, GLB, GLTF, and 3MF; GLB and GLTF must contain their referenced resources.
Opening a local attachment through the plug-in's viewer is a separate, read-only path with different format and size limits. It does not upload the file into Adam. See plug-in file previews.
Access and workspace controls
OAuth connects you to one Adam workspace. Your granted permissions, workspace policy, task ownership, and connected integrations determine what you can do. Workspace administrators can disable API/MCP access or block individual permissions, including direct tool execution.
Review or revoke the connection in Settings > Developer > Connected apps. For missing tools or authorization failures, follow connection troubleshooting.