Troubleshooting

The client cannot connect

Use a client that supports remote Streamable HTTP MCP and OAuth. Copy the exact server URL from MCP connections, including its query parameters. Follow the agent setup instructions for that client. Complete browser sign-in yourself when prompted, then return to the client.

If the client shows a disconnected or expired session, use its reconnect or authorization flow. Never paste a password, access token, or API key into an agent prompt to complete sign-in.

A workspace or drive is missing

Check that you signed in with the right account. Review the connection’s approved workspaces and drives and your current workspace role. Reauthorize or edit the connection when needed. If permission choices fail to load, retry; a failed load is not an empty workspace.

Upload or search is not ready

Check the file’s upload and search status in the Console. Wait for pending work, and use the displayed recovery action for a failed upload. Confirm the file type and size are within the limits shown for your workspace.

A missing search result does not prove the file is missing. Open the drive to check its stored files and verify the connection’s access.

A change is refused

Read the message shown by the Console or client. Confirm your role permits the action, the connection includes the required permission, and your workspace has the required capacity or plan. Review the displayed price before confirming a paid change.

Contact support

If you need help, email support@evokoa.com with the request ID and a description of the task. Keep passwords, tokens, payment details, and private file contents out of support messages.