Disconnect MCP and rotate its credential

Disconnect MCP and rotate its credential is easier to verify when you use one controlled item and confirm the account, workspace, source, and destination at each step. This guide follows the current Dosya workflow and identifies the result you should see.

Before you start

• Open a supported MCP client configured for Dosya in the current released client.
• Confirm the active account and workspace, then identify MCP connection that should be retired.
• Use a small non-confidential test item and record its current state before changing it.
• Keep passwords, API keys, recovery codes, private links, personal data, and confidential file contents out of screenshots and support messages.

Steps: disconnect MCP and rotate its credential

1. Open a supported MCP client configured for Dosya and confirm the active account and workspace.
2. Locate MCP connection that should be retired and verify its name or identifying details.
3. Stop the server or remove the client entry, revoke the old Dosya key, create a replacement only if needed, and retest the old key.
4. Read the displayed warning, permission, progress, or confirmation state before leaving the screen.
5. Confirm that the retired connection and credential can no longer access Dosya.
6. Refresh, fetch, or reopen the relevant view once to verify the result persisted.

Expected result

The controlled workflow completes and the retired connection and credential can no longer access Dosya. The result remains visible after a refresh, reconnect, or return to the relevant screen.

Limits and important details

• Available controls depend on the current client version, account plan, workspace role, policy, and selected integration surface.
• Processing, indexing, background transfer, provider authorization, or storage accounting can delay a visible result.
• For destructive, access-changing, or automated actions, validate with disposable data before applying the workflow to important files.

Troubleshooting

The expected control is missing. Return to a supported MCP client configured for Dosya, confirm the active workspace, and check that your role and client version support the action.

The operation is rejected or stalls. Read the exact message and check permissions, locks, storage, network state, source availability, and any third-party authorization before retrying.

The result is still unclear. Repeat with one small test item, then contact support with the time, client version, workspace, and a nonsecret error, delivery, or request identifier.

Related guides

• Connect an MCP client
• Troubleshoot MCP