🩺Troubleshooting
Common Dapta MCP problems and how to fix them, from key creation errors to 401 responses and missing skills.
Last updated
Common Dapta MCP problems and how to fix them, from key creation errors to 401 responses and missing skills.
Most issues come down to the API key, the plugin, or the skills. This table covers the common cases.
Key creation fails with a connection error
Identity service unreachable (for example, VPN off)
Reconnect and retry
401 or 403 on tool calls
Invalid or revoked key, or a non-owner action
Re-check the key; mint a new one if needed
"Create key" button missing
You are not a workspace owner
Ask your workspace owner to mint a key
Nothing happens in the regular Claude.ai chat
The plugin runs in Claude Cowork and Claude Code, not the standard chat
Use Claude Cowork or Claude Code
Claude Desktop "Add custom connector" fails
That dialog is now OAuth-only, the old connector URL no longer connects
Use the plugin instead: download it from the key dialog and upload it under Personal plugins
Plugin upload is rejected
The .zip was unzipped before uploading
Upload dapta-ai-plugin.zip as-is, do not unzip it
Can't download the plugin again
The plugin is generated once, from the key reveal dialog
Revoke the key and mint a new one to get a fresh plugin
Claude Code does not know how to do a task
Skills bundle not installed (Claude Code)
Re-download and unzip the bundle into .claude/skills/
Claude Code reaches tools but skips the guided workflow
Skills bundle not installed or not paired
Reinstall the bundle, then start a new session
Can't mint a new key
An active key already exists
Revoke the current key first (one per workspace)
If none of the above fixes it, open a tracked ticket from your AI client. Just say:
Open a support ticket: the Dapta MCP isn't connecting.
The create_support_ticket skill will preview the ticket and file it once you confirm. See Support for details.
Last updated