Connecting Claude Desktop to Dureach via MCP means registering an OAuth client, completing workspace consent, adding the streamable-HTTP server, and running a first bounded search. Plan about 20 minutes plus approval time for write scopes.
What should you prepare before opening Claude Desktop?
Select the workspace, confirm the agent platform capability, and decide the job: research-only access needs workspace:read, companies:read, and trade:read; contact lookup adds contacts:read. Keep leads:create, campaigns:create, and send scopes out of the first grant. Name an owner who will review candidate data before it changes authoritative records.
How do you register and consent the client?
- Register an OAuth client for the workspace with the chosen scopes.
- Start the authorization grant and complete consent in the browser as a workspace member.
- Store credentials in the client’s protected credential store or a server-side secret manager. Never paste a token into a conversation, shared document, screenshot, or ticket.
- Confirm the token audience is the
/mcpresource and the workspace ID matches the intended workspace.
Full field tables are in Connect an AI client via MCP.
How do you add the server in Claude Desktop?
- Add a streamable-HTTP MCP server with URL
https://app.dureach.com/mcp. - Select OAuth authentication and enter the client registration values; use the MCP resource metadata URL when the connector asks for discovery.
- Complete consent and confirm the tool list includes
dureach.workspace.context,dureach.workspace.capabilities, and the granted read tools. - Call
dureach.workspace.contextfirst and check the returned workspace ID, role, and scopes.
How do you run a first bounded search?
Use tools/list to discover the tools available to your connection. Availability depends on the granted permissions and workspace access. Start with read scopes; ask a workspace administrator to review missing access rather than requesting broad permissions.
What checks close the setup?
Review access grants, policy changes, and available activity records before expanding access. Keep only redacted request IDs and operational metadata in shared notes. Remove the connection when the project ends or access is no longer needed; revoke and replace any credential that may have leaked.
What are common questions about Claude Desktop setup?
How long does setup take?
Registration and consent take minutes; allow extra time when write scopes need owner review.
Why is the tool list empty?
Use tools/list to discover the tools available to your connection. Availability depends on the granted permissions and workspace access. Start with read scopes; ask a workspace administrator to review missing access rather than requesting broad permissions.
Can one connector serve two workspaces?
No. Tokens are bound to the consent workspace. Register and consent separately per workspace.
Should the connector get send scopes on day one?
No. Add sends only after read behavior, dry runs, and the standing policy review are complete.
What proves the setup worked?
workspace.context returns the expected workspace, capabilities lists the expected tools, and a bounded search returns reviewable rows.
Where do failed calls go for review?
Keep the request_id, timestamp, tool name, and error code; never keep the token beside result rows in shared notes.