Troubleshooting
Common fixes when Memxus MCP tools fail or the API returns errors.
Remote MCP (hosted)
Memxus uses a hosted MCP server at https://mcp.memxus.com/mcp — no local dist/index.js install required.
- Claude OAuth: retry from /install; complete Google sign-in on the dashboard when prompted.
- Cursor / VS Code: use a fresh
aimem_* key from API Keys. Delete the auto-created Default Key and create a new one to see the plaintext. - Not connected: verify the MCP URL has no trailing path errors and Bearer header is
Authorization: Bearer aimem_… - PLAN_LIMIT errors: upgrade plan or delete memories with
forget. - Restart Claude Desktop or reload Cursor after changing MCP config.
Full MCP setup →API key & dashboard
- Keys should start with
aimem_; revoke and recreate if unsure. - Check workspace billing or rate limits if responses are
429 or plan-related errors.
Custom GPT Actions
- ChatGPT uses the published Memxus GPT (not MCP). See Connect for the store link.
- OpenAI requires public HTTPS; localhost URLs fail in production Actions.
- Use low
limit (3–5) on list/search to avoid response size errors.
For marketplace reviewers, see usage examples at /docs/mcp/examples. For account-specific issues, contact support from the dashboard.