Dureach
Channels

Connect External AI via MCP

Expose workspace company, trade, contact, lead, and campaign tools to external MCP clients with OAuth scopes, approvals, and quotas.

Give an external MCP client governed access to workspace tools

Connect External AI via MCP exposes fourteen dureach.* workspace tools over MCP streamable HTTP at https://app.dureach.com/mcp. External clients authenticate with workspace OAuth, discover only granted tools, and run reads, drafts, and policy-gated sends inside workspace quotas and approval gates.

What the connection includes

  • Workspace reads: Context, capabilities, company search and read, trade search, contact search, lead and campaign lists.
  • Read-only SQL: Filtered queries on the contacts and shipments views with a closed grammar and bounded pages.
  • Governed writes: Lead creation and campaign drafts behind creation scopes, dry-run preview, and idempotency keys.
  • Policy-gated sends: Email and SMS sends behind send scopes, a standing send policy reviewed and activated by an owner, and per-policy budget caps.

Why teams use it

Research where the team already works

Analysts and sellers can run source-backed company, trade, and contact checks inside their MCP-capable client instead of exporting lists between systems.

Fewer access surprises

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.

Review before customer impact

Before enabling sends, have an owner review the audience, sender, message claims, consent, suppression, applicable jurisdictions, licensing, and budget caps. Use an active standing policy_id for permitted sends and preview with dry_run: true. A standing policy may authorize multiple sends; it does not mean a person approves each message individually. Pause work when eligibility or authorization is unclear.

How access stays bounded

Request and usage limits depend on workspace access and the action. Check current usage with your workspace administrator. For quota_exceeded, honor Retry-After and any returned reset time, then retry with bounded backoff. Do not use parallel retries, additional clients, or new policies to evade limits.

Start here

Tool results are transferred to the external client and may be processed or retained by its provider. Review the provider’s data handling, retention, and access terms before connecting. Request only the fields needed for the job; keep contact details and customer records out of shared conversations, screenshots, and logs.