MCP returns 404 for projects when authenticated user (with workspace admin rights) is not a project member

Hi! I wanted to say thank you for the Plane and MCP connector, we as a team love it, but have faced several issues with the MCP.
Self-hosted version + subscription.

When the authenticated user has workspace-level access but is not listed on a specific project's Members, retrieve_project returns 404 Not Found and list_projects omits the project from results.

Expected behavior

• The API surfaces the project as read-visible (or at least listable) for users with workspace access, matching what they see in the UI;
  or
• The API returns a more specific error (e.g. 403 with a "not a project member" reason) instead of 404, so callers can distinguish "doesn't exist" from "you can't see it."

Actual behavior

404 Not Found is returned, which is indistinguishable from the project not existing at all. Downstream operations (creating work items, modules, cycles, comments, states) are all hard-blocked with no actionable signal about why.

Start by tracing the retrieve_project and list_projects entry points and the authorization checks for workspace admins who are not project members. Reproduce the 404 with an authenticated non-member, then verify the completed behavior against the stated read-visible or actionable-permission-error expectation for downstream operations.