Skip to content

docs(github): remove stale PAT/notifications references from GitHub MCP server docs#996

Draft
jottakka wants to merge 1 commit into
mainfrom
cursor/remove-github-mcp-pat-notifications-b9e7
Draft

docs(github): remove stale PAT/notifications references from GitHub MCP server docs#996
jottakka wants to merge 1 commit into
mainfrom
cursor/remove-github-mcp-pat-notifications-b9e7

Conversation

@jottakka
Copy link
Copy Markdown
Contributor

@jottakka jottakka commented Jun 5, 2026

What & why

The GitHub MCP server docs still described notification tools and a classic Personal Access Token (PAT) requirement, but those tools (GetNotificationSummary / ListNotifications) have been removed from the toolkit. The PAT (GITHUB_CLASSIC_PERSONAL_ACCESS_TOKEN) was only ever needed for those notification tools, so all of that content is now stale and misleading.

This PR removes the stale content from both the generated toolkit docs and the hand-authored GitHub auth provider page, and tidies up the affected sections.

How docs are generated (context)

The GitHub MCP server page is rendered from toolkit-docs-generator/data/toolkits/github.json. The prose (documentationChunks) is hand-curated content that the generator carries forward from the committed JSON when no custom-sections file is supplied (the scheduled generate-toolkit-docs workflow runs with --skip-unchanged and no --custom-sections). Editing the committed JSON directly is therefore the durable fix. Tool definitions/parameters come from the Engine API.

The separate GitHub API toolkit (githubapi.json) genuinely still has notification tools and was intentionally left untouched.

Changes

Generated docs — toolkit-docs-generator/data/toolkits/github.json

  • Removed the "⚠️ Special: Notifications (Requires Classic PAT)" block from the GitHub App Permissions Summary.
  • Removed the GITHUB_CLASSIC_PERSONAL_ACCESS_TOKEN secrets-table row and the "For Notifications Tools" PAT warning callout.
  • Clarified that GITHUB_SERVER_URL is the only (optional) secret, now that the PAT is gone.
  • Fixed the ListIssues since parameter description that incorrectly said "notifications" instead of "issues".

Hand-authored docs — app/en/references/auth-providers/github/page.mdx

  • Removed the Notifications row from the permissions summary table and the troubleshooting table.
  • Removed the notifications/PAT content from the last permissions tab and renamed it from "Special Cases" to "Act on Behalf of User" (the remaining valid content).
  • Removed the "Why can't I access notifications?" FAQ entry.

Heading text for anchored sections (e.g. #creating-a-github-app, #configuring-github-auth-in-arcade, #why-arcade-uses-github-apps-not-oauth-apps, #tool-permissions-reference) was preserved to avoid breaking internal links.

Verification

  • github.json re-validated as parseable JSON; no remaining notification / PAT / CLASSIC references in either file.
  • tests/internal-link-check.test.ts, tests/broken-link-check.test.ts, tests/sitemap.test.ts, tests/filter-params.test.ts pass.
  • Generator tests/stale-summaries.test.ts and tests/merger/secret-coherence.test.ts pass.

Note: pnpm vale:check could not run in this environment because the Vale binary isn't installed; the pre-commit hook reports Vale style issues as non-blocking. Worth a quick Vale pass before merge.

Open in Web Open in Cursor 

…CP server docs

The GitHub MCP server no longer ships notification tools (GetNotificationSummary,
ListNotifications), which were the only tools that required a classic Personal
Access Token. Remove the now-stale PAT and notifications content from both the
generated toolkit docs (github.json documentation chunks) and the hand-authored
GitHub auth provider page:

- Drop the 'Special: Notifications' permissions block and the
  GITHUB_CLASSIC_PERSONAL_ACCESS_TOKEN secret row/callout.
- Remove the Notifications rows from the permissions and troubleshooting tables
  and the notifications FAQ entry; rename the trailing permissions tab to
  'Act on Behalf of User'.
- Fix the ListIssues 'since' parameter description that wrongly referenced
  notifications.
- Clarify that GITHUB_SERVER_URL is the only (optional) secret, since the PAT
  was the only required one.
@vercel
Copy link
Copy Markdown

vercel Bot commented Jun 5, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
docs Ready Ready Preview, Comment Jun 5, 2026 12:11am

Request Review

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants