docs: correct SharePoint managed MCP page against source and production#97
Conversation
The SharePoint page made several claims the implementation does not back up. Verified every statement against cloudv2 @ 1ce9017a06 and an end-to-end run on the production deployment, then fixed what was wrong: - search_content searches all of SharePoint (driveItem, listItem, site entity types, KQL syntax), not "across a site" - file transfer is UTF-8 text only: 10 MiB download cap, 4 MiB upload cap (Graph simple-upload limit); binaries go through web_url - page-size contract: 100 default / 999 max on the three paged list tools, 25/500 on search, none on list_lists; hidden lists dropped - the authorize_url points at the gateway's /oauth/v1/authorize, not Microsoft; the Connect banner is the real first-connect UX, the Inspector only shows the raw error - create-form labels as production renders them: Create server, Auth, User OAuth, Required Scopes, Submit - Graph errors surface status + code only; added token-expiry and byte-cap troubleshooting rows - CLI example uses protojson camelCase like the other managed pages - intro no longer claims site/list write access; upload_file is the only write tool. Same fix on the catalog row.
✅ Deploy Preview for redpanda-agentic-data-plane ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Nine screenshots from a real end-to-end run: the three Entra steps that trip people up (app registration, where the client and tenant IDs live, client secret creation), the Graph permissions with admin consent granted, and the ADP side (marketplace picker, OAuth provider, create form with payload preview, Connect banner, Inspector run).
Unquoted commas in image:: alt text truncate the alt at the first comma and spill the remainder into bogus width/height attributes. Quote all nine, drop the inner quotes in the picker alt, and tighten the connect-banner alt to what the viewport actually shows.
PR Review: docs: correct SharePoint managed MCP page against source and production (#97)Files reviewed: 2 .adoc files + 9 new screenshots What this PR doesCorrects factual inaccuracies in the SharePoint managed MCP server page by verifying every claim against cloudv2 source at Jira ticket alignmentNo linked Jira ticket found in the branch name, PR title, or PR body. Critical issues (must fix)None found. Suggestions (should consider)
Non-standard external screenshotsThis PR adds 4 screenshots of the Microsoft Entra admin center (third-party UI), similar to the accepted deviation in PR #95 (MS Teams):
The remaining 5 screenshots are standard Redpanda ADP UI captures ( Decision needed: Same rationale as MS Teams — the Entra setup spans multiple portal screens and is the hardest part of the flow. The captures appear sanitized and the page's third-party integration context covers UI drift. If accepted, these 4 join the 6 from PR #95 in the external screenshot inventory that needs tracking/refresh automation. Impact on other filesNo impact detected. Nav entry exists, no pages renamed/moved, no broken xrefs. CodeRabbit findings worth consideringNo CodeRabbit review found on this PR. What works well
|
|
In @birdayz I also want to check: There's an environment dropdown in the left nav of these ADP screenshots. Will users also see this? Is I'll approve this PR for now, but we'll loop back in July to add proper automated screenshots. |
|
@JakeSCahill the screenshot is correct |
3 participants
What
Fact-check and correction pass on the SharePoint managed MCP page, plus a one-line accuracy fix to its managed-catalog row.
Why
The page shipped with claims the implementation does not back up: wrong search scope, missing file-transfer limits, and a consent-flow narrative that does not match the actual UI. Docs that misstate error behavior generate support tickets.
Every claim is now verified twice: against cloudv2 source at
1ce9017a06, and against a full end-to-end run on the production deployment (Entra app, OAuth provider, managed server, consent flow, all 8 tools, agent).Implementation details
search_contentis tenant-wide search over driveItem/listItem/site entity types with KQL syntax, not "across a site".web_urlfor binaries.list_sites,list_drive_items,list_list_items; 25/500 onsearch_content;list_liststakes none and excludes hidden lists.authorize_urlpoints at the gateway's/oauth/v1/authorizeendpoint, not Microsoft; the first-connect UX is the Connect banner on the server page, the Inspector only shows the raw error.@typeURL, matching the other managed pages.:description:, and catalog row no longer claim site/list write access;upload_fileis the only write tool.Screenshots
Nine screenshots from a real end-to-end run. Five are standard Redpanda ADP UI captures; four are non-standard external screenshots of the Microsoft Entra admin center (third-party UI), knowingly deviating from the style guide's rule against screenshots of third-party products:
sharepoint-entra-register.png— Entra app registration formsharepoint-entra-app-overview.png— Essentials pane showing client/tenant IDssharepoint-entra-client-secret.png— client secret creation dialogsharepoint-entra-permissions.png— Graph permissions with admin consent grantedSame rationale as the MS Teams page in #95: the Entra setup spans multiple portal screens and is the hardest part of the flow. Captures are sanitized. These 4 join the 6 from #95 in the external screenshot inventory that needs tracking/refresh automation.
References
apps/aigw/internal/mcp/managed/mcps/sharepoint/,proto/mcps/redpanda/mcps/sharepoint/v1/, verified at1ce9017a06apps/aigw/docs/user-docs/sharepoint-mcp-setup.md