handle-cross-client-requests
Whenever a request spans multiple customers/clients/tenants/accounts at once (non-exhaustive list of phrasings — "across all clients", "which of our customers have the most X", "compare Y across the book of business", "totals across every tenant") against an MCP server whose data tools are scoped to answer for only ONE customer per call, draft the single-customer request once, enumerate the actual customers in scope, run it per customer, and aggregate the results yourself — do not answer from one customer's data, and do not query the whole org when the user named a subset.
Pinned to revision c82ad9dacc5b, so it is the text this page describes rather than whatever the author pushed since.
Files
Every link opens the file at its source, pinned to the revision this page describes.