Troubleshooting
Quickly diagnose and fix common integration issues.
Having trouble getting Milkey to work with your specific AI tool? Browse the diagnostic steps below, which cover 95% of common configuration errors.
Client Reports "Connection Failed" or "Unauthorized"
If your tool shows an error state when trying to query Milkey, it almost always points to an invalid authentication token.
- Check if you copy-pasted your
mk_live_...API key correctly. Make sure there are no trailing whitespaces. - Ensure you haven't recently deleted the key from the Dashboard.
- Confirm you are under your monthly usage quota. If your request gets a
429, your tool may surface it as a generic connection failure.
Remember that keys must remain active to keep your integration working. If a team member revokes a key, the connected instance is instantly disconnected.
Enabled Skills Aren't Showing Up
If your assistant doesn't seem to recognize the context you enabled in the platform:
- Force restart your AI application. Sometimes the MCP server connection caches states across process lifecycles.
- Log in to the dashboard and ensure the toggle for the desired skill accurately shows as
On.
I need more help
If these steps do not help, or you are experiencing persistent 500 Internal Server Error responses, please reach out to our team at:
Technical Support
Email: milkeymcp@gmail.com
Please include your Public Account ID, the snippet of the error trace, and a general description of the AI tool you are using when describing your issue.