dosya.dev Help

Troubleshoot an MCP connection

Check client version, server address, authorization, scopes, workspace and tool errors when a Dosya MCP client cannot connect or act.

Last reviewed

Reduce MCP diagnosis to connection, authorization, tool discovery and one harmless read operation.

Before you start

  • Use the current released client or web app and sign in to the intended account.
  • Select the correct workspace and use non-confidential test data.
  • Record the current setting or result before changing it.
  • Keep passwords, API keys, recovery keys and private links out of screenshots and support messages.

Steps: troubleshoot an mcp connection

  1. Check the client supports the current MCP transport.
  2. Copy the server address from current documentation.
  3. Reconnect authorization for the intended workspace.
  4. List available tools and compare requested scope.
  5. Run one harmless read call.
  6. Disconnect and reauthorize only after preserving the nonsecret error.
Dosya credential restriction controls used to limit a technical client to the required workspace, permission and protocol.
Use a separate least-privilege credential for each client. Open full-size screenshot.

Expected result

The troubleshoot an mcp connection workflow completes for the test item and its result remains visible after a refresh or reconnect.

Limits and important details

  • Available controls depend on the current client version, plan, role and workspace policy.
  • A successful connection does not grant permissions beyond its credential and workspace boundary.
  • Verify important results with a harmless test before relying on the workflow.

Troubleshooting

The expected control is missing. Confirm the current client, active workspace and role, then check the relevant settings page.

The operation is rejected. Read the exact error and compare credentials, permissions, quota and workspace policy.

The result is still unclear. Repeat with one small test item and contact private support with the time, client version and nonsecret error.

Continue with another task

Was this helpful?

Loading helpfulness results…

Voting saves a necessary ballot cookie for up to 180 days so you can change your answer.

About views and your privacy

Views count page openings, not reading or task completion.

View measurement is off by default. If you enable it, a separate 30-minute cookie prevents repeat openings from increasing the count. We do not use fingerprinting or connect this session to uploads or shares.

Questions and replies

Ask about the steps in this guide. Questions are reviewed before publication.

Keep account details, credentials and private files out of public questions. Use private support for those.

Loading questions…

    Sign in to your Dosya account to ask a question.