Troubleshooting
Common Dapta MCP problems and how to fix them: workspace questions, login loops, key errors, removed web search tools and expired previews.
Most issues come down to the workspace, the login or the API key. This table covers the common cases.
Claude asks which workspace to use
You signed in and your account has several workspaces
Answer with the workspace name (not an id). Say "switch to <name>" to change later
"workspace is required" in a tool answer
A signed-in conversation that has not named its workspace yet
Tell Claude the workspace. It repeats the call
Login page loops, or the connector shows an error in claude.ai
Stale connector session
Remove the Dapta connector and add it again with https://mcp.dapta.ai/mcp
401 "Invalid or revoked API key"
Wrong or revoked key
Check the key in MCP Access. Create a new one if needed
401 that sends the client to a login although you use a key
The key was sent as Authorization: <your-key> without Bearer, or in an unknown header
Use the x-api-key header, Authorization: Bearer <your-key>, or the connector URL with the key
Create API key is missing or fails
You are not a workspace owner, or your role cannot create keys
Ask the workspace owner
Claude says a web search tool is unknown
Web search tools were removed from the server
Use your client's own web search. Otherwise Claude asks you for the company details
A write says the preview expired
Previews are single-use and short-lived
Ask Claude to preview again and confirm
Old instructions mention a plugin or a skills bundle
Both are retired
Nothing to download. Connect with a login or a key as described in Setup & Connection
Still stuck?
Write to support@daptatech.com and include the client you use, how you connected (login or API key), and the exact message you see. Never send your API key.
Related
Verify your connectionMint your API keyLast updated