How do I review FastMCP OAuth storage before serving multiple Montage users?
FastMCP can supply direct remote access without a model, but private OAuth state must remain tied to its owner. Review the application’s client and storage association before allowing multiple users to share tool-facing code or a reused connection object. Private auth storage should be selected by the application’s user boundary, not inferred from a shared Client object. A direct session-specific check can reveal a mismatch without granting unrelated callers access or logging another person’s account state.
Help me review FastMCP OAuth storage before serving multiple Montage users. Identify which application user owns each remote request and where the authorized Client is selected. Report the checked session’s result and the remaining multi-user cases not exercised. No writes.Map the requesting identity
Identify which application user owns each remote request and where the authorized Client is selected. Keep this decision in application code, not a tool argument that a model or unrelated caller can freely replace.
Review approved auth facilities
Consult the installed FastMCP client-auth documentation for the supported OAuth path and private token storage. Do not assume URL-only construction automatically establishes the correct account, and do not place auth material in the remote URL.
Inspect storage separation
Check whether the application can distinguish authorization belonging to different users before reusing a Client. An ambiguous shared store should block private reads; another person’s successful status response is not an acceptable substitute for missing user association.
Test one intended session
Within its valid async context, use list_tools and select signals_status before calling it directly. Compare the actual workspace with the expected user context without logging token storage, callback secrets or another user’s private workspace details.
Limit the conclusion
Report the checked session’s result and the remaining multi-user cases not exercised. One correct direct read does not prove every concurrent path is isolated, and a configuration review alone cannot establish that credentials were revoked elsewhere.
Keep the boundaries clear.
- An ambiguous shared store should block private reads; another person’s successful status response is not an acceptable substitute for missing user association.
- One correct direct read does not prove every concurrent path is isolated, and a configuration review alone cannot establish that credentials were revoked elsewhere.
Start with a read-only check: ask your agent to report actual source coverage before collecting records or exporting an audience.
Primary references
Documentation reviewed 2026-11-15. Product capabilities, client availability and plans can change. Third-party marks identify their products, not an affiliation.