Duaer

MCP

Connect AI tools to Duaer

Connect Claude, Claude Code, ChatGPT, Cursor, VS Code and Codex to the Duaer MCP server: the URL, how sign-in works, steps for each tool, scopes and common problems.

Before you start

  • An organization owner or admin opens Settings › MCP in Duaer and selects Enable MCP access. See Turn on the Duaer MCP server.
  • The URL: https://www.duaer.com/mcp-server/http on Duaer cloud; self-hosted, your Duaer address plus /mcp-server/http.
  • Claude and ChatGPT connect from their own cloud, not from your computer. A self-hosted Duaer must be reachable over HTTPS from the internet; behind a private network or VPN, allow their IP addresses as their docs describe.

Two ways to sign in

  • OAuth (recommended): on its first connection, the AI tool registers itself with Duaer, so there is no client ID or secret to type. Duaer’s consent page then opens; you sign in as yourself and tick the scopes to grant. Tokens renew on their own.
  • Access token: generate one under Connection details in MCP and send it as an Authorization: Bearer <access token> header in the tool’s settings. It is shown once and carries all of your access, with no scopes to tick, so keep it safe.
  • Either way, the AI tool never has more access than you: what you cannot read or change, it cannot either.

Claude (web and desktop)

  1. Open Customize › Connectors, click + Add, and select Add custom connector.
  2. Name it Duaer, enter https://www.duaer.com/mcp-server/http as the server URL, and click Continue.
  3. Under Authentication choose Sign in when needed or Sign in now; under OAuth client choose Register automatically.
  4. Click Add, then Connect, and tick the scopes on the Duaer consent page.
  5. In a chat, click + at the lower left › Connectors and turn on Duaer.

On Team and Enterprise, an owner adds it under Organization settings › Connectors › Add › Custom › Web, and each member clicks Connect under Customize › Connectors. The Free plan allows one custom connector.

A longer Claude walk-through is in Connect Claude to Duaer with MCP.

Claude Code

In a terminal (with --scope user it applies to all your projects):

claude mcp add --transport http duaer https://www.duaer.com/mcp-server/http --scope user

Then type /mcp in Claude Code, or run claude mcp login duaer in a terminal, and finish sign-in in the browser.

With an access token: add --header "Authorization: Bearer <access token>" to the command.

ChatGPT

  1. In ChatGPT on the web, open Plugins, select the plus button, then Add custom MCP server.
  2. Enter a name, and under Connection enter https://www.duaer.com/mcp-server/http as the Server URL.
  3. Under Authentication choose OAuth.
  4. Review the risk warning, select I understand and want to continue, then Create as a plugin.
  5. Install the plugin, type @ in the prompt box to pick Duaer, and finish the Duaer consent on first use.

Adding works on the web only. Whether you may add and use custom MCP servers depends on your ChatGPT workspace permissions; if the option is missing, ask a workspace admin.

Cursor

Add this to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json in a project:

{
  "mcpServers": {
    "duaer": {
      "url": "https://www.duaer.com/mcp-server/http"
    }
  }
}

After you save, Cursor asks you to sign in; finish the Duaer consent in the browser. If something fails, open the Output panel and pick MCP Logs.

With an access token: add "headers": { "Authorization": "Bearer ${env:DUAER_MCP_TOKEN}" } under duaer and set the DUAER_MCP_TOKEN environment variable.

VS Code and GitHub Copilot

  1. Open the Command Palette and run MCP: Add Server.
  2. Choose HTTP (HTTP or Server-Sent Events), enter the URL, and use duaer as the ID.
  3. For yourself, pick Global › Copilot Global; this writes ~/.copilot/mcp-config.json.
  4. Sign in to Duaer when asked on first use; turn Duaer’s tools on or off under Chat: Open Customizations › Tools.
{
  "mcpServers": {
    "duaer": {
      "type": "http",
      "url": "https://www.duaer.com/mcp-server/http"
    }
  }
}

If your VS Code shows no sign-in prompt, use an access token: add "headers": { "Authorization": "Bearer ${DUAER_MCP_TOKEN}" } under duaer and set the DUAER_MCP_TOKEN environment variable.

OpenAI Codex (CLI, IDE extension and desktop app)

All three share ~/.codex/config.toml. In a terminal:

codex mcp add duaer --url https://www.duaer.com/mcp-server/http
codex mcp login duaer

codex mcp login opens the browser for the Duaer consent. With an access token: add bearer_token_env_var = "DUAER_MCP_TOKEN" under [mcp_servers.duaer] in config.toml and set that environment variable.

Scopes on the consent page

  • Workflows: find, read, create, change, publish and run workflows. Executions: read run results.
  • Knowledge base: `search_knowledge` finds documents and can keep to field values with `fields` (a Jira status, for example); `answer_knowledge` answers with sources.
  • Process: the process overview, process findings, one case, and metrics.
  • Employee assistants (`assistant:use`): `list_assistants` lists the employee assistants you may use, and `ask_assistant` answers with one assistant’s instructions and sources, reading only what you may read; each call is recorded in that assistant’s runs. It is not ticked by default; tick it when you need it. See Employee assistants.
  • Your Duaer cards (`card:decide`) and Employee portal actions (`action:run`): list and decide your cards (and put them off, take them back, or attach files), list and run portal actions; deciding a card and running an action happen only after you confirm in the AI tool. Not ticked by default. See Cards and portal actions.
  • There are also agents, skills, credentials, data tables, projects and folders, AI preferences, and installing community nodes on this instance.

Tick only what you need. Connected tools appear in the OAuth clients list in MCP, where you can revoke them; when a tool connects again, what you ticked last time stays ticked.

Register a client for an AI platform that needs a Client ID

AI tools such as Claude, ChatGPT and Cursor register themselves and need none of this. Some AI platforms ask for a Client ID and Client Secret instead; an organization owner or admin registers a client for them in Duaer first:

  1. In Duaer, open Settings › MCP, and under Registered clients select Register.
  2. Enter a name and the callback URLs the AI platform shows (one per line, HTTPS).
  3. Copy the Client ID, Client Secret, authorization URL and token URL into the AI platform. The Client Secret is shown only once.

Only members of your organization can sign in through the client; anyone else is refused. The AI platform may send the Client Secret in a Basic header or as form fields. If the secret leaks, select New secret: the old one stops working at once. Deleting the client signs out everyone who signed in through it.

Troubleshooting

  • MCP access is disabled: the organization has MCP access off; an owner or admin turns it on in MCP.
  • A tool is missing: its scope was not ticked (employee assistants are unticked by default); disconnect, connect again and tick it. Knowledge base and employee assistant tools also need the knowledge base turned on in Duaer.
  • The consent page says the callback URL is not allowed: the platform owner set allowed callback URLs; add the tool’s callback URL. Cursor’s are https://www.cursor.com/agents/mcp/oauth/callback and http://localhost:8787/callback; see each tool’s docs for others.
  • Claude or ChatGPT cannot reach a self-hosted Duaer: make sure Duaer is reachable over HTTPS from the internet.
  • `ask_assistant` says there is no assistant you may use: it is off, deleted, or not shared with you.
  • `decide_card` or `run_action` answers only with the employee portal link: the AI tool cannot show a confirmation, or the card needs a colleague picked. Decide it on the portal.
  • Each `answer_knowledge` and `ask_assistant` call counts toward the answer limit and spends organization credits; at the organization’s or your own credit limit it is refused.

Questions

OAuth or an access token?

Prefer OAuth: you tick scopes, tokens renew, and you can revoke the tool in Duaer at any time. An access token suits tools without OAuth and carries all of your access.

Can an AI tool use employee assistants colleagues shared with me?

Yes, once Employee assistants is ticked on the consent page. It lists the assistants you may use on the employee portal and reads only what you may read.

Do I register a client in Duaer by hand?

No. These tools register themselves on their first connection; only when the platform owner restricted callback URLs do you add the tool’s callback URL to the allowed list.

In this section