durin
Book A Demo
Knowledge base
Connections & MCP

Restore provider access

Diagnose a provider error after your client has connected to Durin.

Everyone1 min read

Locate the failure

Open the affected connection and the request’s activity. Identify whether provider consent, discovery, a readiness test, or execution failed. Keep the error text, time, and request ID.

Check provider access

Use a small reviewed read to verify a correction.

  1. Check the provider’s status and the upstream account or workspace.
  2. Confirm the current credential or OAuth grant for the affected identity.
  3. Check the reviewed tool, permitted resource, and connection setup status.
  4. Resolve the reported condition, then repeat the read and inspect its outcome.

Troubleshooting

Consent succeeded but the test fails

Check the intended provider account, reviewed tool validator, allowed resource, and current team access. OAuth consent alone does not establish readiness.

Only one provider fails

Inspect that installation’s status and grant. A working connection does not establish access to a different provider.

Frequently asked questions

What should I include in a support request?

Include the error, timestamp, connection ID, request ID, and failed setup step. Exclude bearer tokens, provider secrets, and sensitive payloads.

Try Durin with your MCP workflow.

Book a demo to explore agent access, policy checks, approvals, and audit records with our team.

Book a demo

Choose which optional purposes this browser allows. Cookies that keep the site working, keep you signed in and remember this choice are always on, as is the referral cookie a referral link sets for up to 90 days. Your choice is stored in a first-party cookie for 180 days. Saving a choice that turns analytics off reloads this page if analytics was running on it. Read the privacy notice.