# Connect an MCP client

Connect your MCP client to the hosted Adam server. Use the endpoint for your client:

```text
https://adam.new/mcp
```

ChatGPT and Codex use `https://adam.new/mcp/chatgpt`, which exposes each supported operation as a named tool. Other clients use `/mcp`, which includes the named native tools and the existing task-tool discovery interface.

The recommended setup uses OAuth. You do not need to create an API key or
register an OAuth application first.

**ChatGPT**
In a ChatGPT surface that supports custom MCP plug-ins, open **Plugins**, select the plus button, and choose **Add custom MCP server**. Name it **Adam**, enter `https://adam.new/mcp/chatgpt`, and use OAuth authentication.

Create and install the personal plug-in, then complete Adam's sign-in, workspace selection, and permission review. Invoke it from a Work chat to run the read-only connection check below. Custom plug-in access can depend on your host and workspace policy.

See [OpenAI's custom MCP setup guide](https://developers.openai.com/plugins/quickstart) for the current host flow. This creates a connection to the hosted server; the separately packaged [Adam plug-in preview](/mcp/plugin) also includes workflow skills.
**Claude**
**Add a custom connector**
Open **Customize > Connectors** and add a custom web connector named **Adam** with `https://adam.new/mcp` as the server URL. Depending on your Claude version, the entry may appear under **Add > Custom > Web** or **Add custom connector**.
**Use OAuth and automatic registration**
Choose a sign-in option. If Claude asks how to identify its OAuth client, choose **Register automatically**. Adam supports automatic registration, so you do not need your own Client ID or secret.
**Connect Adam**
Start the connection, sign in to Adam, choose the workspace Claude may
access, and approve the permissions.
**Claude Code**
Add Adam for your user account:

```bash
claude mcp add --transport http --scope user adam https://adam.new/mcp
```

Start Claude Code, enter `/mcp`, select **adam**, and authenticate. Sign in
to Adam, choose a workspace, and approve the permissions.

See [Claude Code's MCP guide](https://code.claude.com/docs/en/mcp) for client configuration and scope options.
**Codex CLI**
Add the remote server, then start the OAuth connection:

```bash
codex mcp add adam --url https://adam.new/mcp/chatgpt
codex mcp login adam
```

Sign in to Adam, choose a workspace, and approve the permissions. The
server is then available to Codex as `adam`.

Use `codex mcp list` or `/mcp` to inspect the connection. See [OpenAI's MCP guide](https://developers.openai.com/codex/mcp) for desktop and IDE setup options.
**Cursor**
Add Adam to `.cursor/mcp.json` in your project, or `~/.cursor/mcp.json` for your user account:

```json
{
  "mcpServers": {
    "adam": {
      "url": "https://adam.new/mcp"
    }
  }
}
```

Enable the server in Cursor, then complete the Adam sign-in, workspace
selection, and permission screens.

See [Cursor's MCP guide](https://cursor.com/docs/mcp) for current configuration and authentication options.
**Grok**
Open [Grok Connectors](https://grok.com/connectors), choose **New Connector > Custom**, and enter `https://adam.new/mcp`. Complete Adam's OAuth sign-in, workspace selection, and permission review, then enable the connector in your conversation.

Use the connection check below before starting engineering work. See [Grok's connector guide](https://docs.x.ai/grok/connectors) for current availability and workspace controls.
**Other clients**
Use these connection settings:

| Setting | Value |
| --- | --- |
| Transport | Streamable HTTP |
| Server URL | `https://adam.new/mcp` |
| Authentication | OAuth 2.1 with PKCE |
| Client registration | Automatic registration supported |

Adam publishes the discovery metadata the client needs. If your client
cannot use OAuth but supports custom HTTP headers, you can instead send a
[personal API key](/api-reference/introduction) as
`Authorization: Bearer <key>`.

For managed Claude workspaces, an authorized administrator may need to add the connector before members connect their accounts. Follow [Claude's current custom connector guide](https://support.claude.com/en/articles/11175166-get-started-with-custom-connectors-using-remote-mcp) if the controls differ.

## Verify the connection

```text
Use Adam to identify my connected workspace and granted permissions. If permitted, list my paired computers and the connection status of their CAD and CAE applications. Keep this read-only; do not start an Adam task, launch an application, or run an engineering operation.
```

Check that the returned workspace is the one you intended. `adam_list_devices` reports paired computers and their reported application status without creating a task. Use `adam_fusion_status` for Fusion's live add-in; keep its Adam panel open and signed into the same account. A null generic integration connection is expected for Fusion and does not report whether the add-in is live. Onshape and Arena use cloud account connections and need no paired computer. `adam_list_integrations` reports account connection metadata; a connected account alone does not establish that a desktop application is online. Follow the [application connection guide](/supported-software) when needed. MCP sign-in does not install or pair a CAD application.

## What you approve

During OAuth, Adam asks you to choose one workspace. The permission screen may
include project, task, file, billing, integration, automation, and tool-execution access. Tools that are not covered by the connection's effective permissions do not appear to the client.

`tools:execute` enables [direct tool execution](/mcp/direct-tools), including commands, connected accounts, paired devices, stored credentials, and billable tools. It grants broader authority than the individual read/write scopes. Workspace administrators can disable API/MCP access or block permissions for both new and existing connections.

To remove access, open **Settings → Developer → Connected apps** in Adam and
revoke the client. You can also remove its configuration in the client. Connect again to choose a different workspace or request a different set of permissions allowed by the workspace.

Only connect clients you trust. An approved client can read or change data in
the selected workspace within the permissions shown by Adam.

## Troubleshooting

**The client asks for an OAuth Client ID**
Use automatic registration instead of a manually registered client. In Claude, choose **Register automatically** if that option appears. Confirm the exact URL `https://adam.new/mcp` and update the client if needed. Do not invent a Client ID or paste an API key into that field.
**The wrong workspace is connected**
Disconnect Adam in the MCP client and reconnect it. Choose the intended
workspace on the Adam authorization screen.
**A capability is unavailable**
Check the connection's effective permissions and the workspace's **Admin > API & MCP** policy. If the workspace allows the capability, reconnect and approve its required scopes. Reconnecting cannot override blocked permissions. For direct calls, also check task ownership and `tools:execute` access.
**An administrator has disabled API or MCP access**
Ask a workspace owner or admin to review **Admin > API & MCP**. They can disable all API/MCP access or individual permissions. This applies to existing connections too; reinstalling the client will not restore blocked access.
**The task panel or CAD viewer does not appear**
Ask explicitly to show the task or CAD model. The host must support the relevant MCP Apps interface. Ordinary MCP tools can still retrieve task data in clients without panels. Host attachment previews additionally need the plug-in file-viewer entry point; see [plug-in requirements](/mcp/plugin).
**A task has not finished**
Adam tasks can continue working after the initial request. Ask the client to
check the existing task rather than starting it again. Clients with live
progress support do this automatically.
**The client receives a rate-limit error**
Wait for the retry time shown by the client before continuing. Repeatedly
requesting the same task or list can exhaust the connection's allowance.
**A direct tool call ended with an unknown outcome**
Keep its call ID and inspect the task, files, and native document before retrying. The operation may already have taken effect. Do not automatically submit it again with a new idempotency key. Follow [direct tool recovery](/mcp/direct-tools#read-the-result-before-continuing).

If the connection still fails, check [Adam status](https://status.adam.new) or
contact [hello@adam.new](mailto:hello@adam.new).