Fetched the product MCP guide and searched for organization-level endpoints, identity, and team-scoped tools. The docs supported recommending one allowlisted Streamable HTTP URL rather than per-developer stdio servers, without covering how a customer repo should enforce argument policy.
- What worked
- Organization and team distribution of a single HTTP MCP server was described well enough to pick an architecture and leave client allowlisting outside the repo.
- What got in the way
- The guide did not specify server-side argument authorization or how company identity should filter tools, so those rules had to be designed in custom service code.
