Troubleshooting
Verify Your Connection
After connecting, confirm the assistant can see the tools and reach your account. Ask it something read-only, for example:
- "List my Veeqo warehouses."
- "Show me my account capabilities."
- "How many orders are awaiting fulfillment?"
If the assistant returns real data from your Veeqo account, the install is working. Most clients also show a tool count or a list of veeqo_* tools in their MCP/Connectors panel.
Troubleshooting
The table below shows some common errors and how to fix them:
| Symptom | Fix |
|---|---|
| 401 / "invalid token" after login | Re-run the OAuth flow. For mcp-remote, clear its cached auth: delete ~/.mcp-auth and reconnect. |
| Browser login window never opens | Ensure the client can launch a browser; for headless setups use the API-key auth path instead. |
| npx: command not found | Install Node.js 18+ so npx/mcp-remote is available. |
| Tools don't appear after editing config | Fully restart the client (quit and reopen, not just reload). |
| Some tools are missing | Write tools require the matching Veeqo role permission; read-only access only shows read tools. |
| Rate-limit errors (HTTP 429) | The server limits requests per minute. Slow down repeated calls. |