Back to Home

Troubleshooting

Common fixes when MCP tools fail to appear or the Memxus API returns errors.

MCP server

  • Use an absolute path to dist/index.js in Claude Desktop config — relative paths often break.
  • Confirm AIMEMORY_API_KEY, SUPABASE_URL, and SUPABASE_SERVICE_ROLE_KEY are set in the same env block (see MCP setup).
  • Fully quit and restart Claude Desktop after editing the config file.
  • Run npm run build inside packages/mcp so dist/ exists.
  • Verify Node is on PATH for the process launching MCP (same terminal/session Claude uses).

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

  • OpenAI requires public HTTPS; localhost URLs will fail in production Actions.
  • OpenAPI schema must match real routes — compare with API Reference.
  • Ensure Bearer / API key auth matches what the Memxus API expects.

More depth may live in the repo under docs/TROUBLESHOOTING.md. For account-specific issues, contact support from the dashboard.