You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Changes Since Last Report: +1 new (list_issue_fields), 0 removed, 56 unchanged
Note: this read-only session exposes only read tools. Write tools (issue_write, create_pull_request, label_write, ...) exist in the server and remain in the JSON mapping but are not visible here.
Inconsistency Detection
✅ All tools are properly categorized with no detected duplicates, miscategorization, naming inconsistencies, or orphaned tools. Naming follows the expected verb_noun convention (e.g. list_*, get_*, search_*) and consolidated multi-method tools (issue_read, pull_request_read, actions_get, projects_get).
JSON Mapping Comparison
Summary — comparing the live MCP server against the JSON mapping:
Total Discrepancies: 1
Missing Tools (in JSON, not in MCP): 0 read tools (write tools omitted by design)
Extra Tools (in MCP, not in JSON): 1
Moved Tools: 0
Extra Tools (in MCP but not in JSON)
Toolset
Tool Name
Action Taken
issues
list_issue_fields
Added to JSON mapping
Action: Created pull request #aw_pr1 ([mcp-tools] Add list_issue_fields to issues toolset mapping) adding list_issue_fields to the issues toolset in alphabetical order.
Changes Since Last Report
New Tools Added ✨
Toolset
Tool Name
Purpose
issues
list_issue_fields
List issue field definitions (name, type — text/number/date/single_select — and valid option names) for a repo or org
Removed Tools 🗑️ · Moved Tools 🔄
None — no tools were removed or re-categorized since the last report.
context — identity/team awareness (get_me, get_teams), essential for any GitHub-aware agent.
repos — core file/commit/branch reads needed by most workflows.
issues — read/comment/create, common in CI/CD and automation.
pull_requests — read/create/review, critical for code-review and merge automation.
These match the current [default] set; no change recommended. The new list_issue_fields lands in the already-default issues toolset, so defaults stay current automatically.
Specialized (enable explicitly): actions (CI), discussions, the four security toolsets (audits), projects (requires PAT, not GITHUB_TOKEN), notifications, gists, labels, orgs, stargazers, users, and the remote-only copilot_spaces / github_support_docs_search.
Notes and Observations
The single delta this cycle (list_issue_fields) reflects GitHub's rollout of custom issue field definitions; it complements list_issue_types and pairs with list_issues field filtering.
⚠️ Per the instructions file, do not use mode: remote in GitHub Actions — GITHUB_TOKEN lacks MCP access; default mode: local (Docker) should be used. This report enumerates the remote surface for documentation parity only.
Methodology
Self-inspection of mcp__github__* tools in the read-only remote session. Diff: baseline = cached 2026-05-31 (56 tools); current = 57 → added list_issue_fields. Mapping: github_toolsets_permissions.json · server source: github/github-mcp-server.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Generated: 2026-06-07 · MCP Mode: Remote (read-only session) · Toolsets: All · Previous Report: 2026-05-31
Executive Summary
list_issue_fields), 0 removed, 56 unchangedInconsistency Detection
✅ All tools are properly categorized with no detected duplicates, miscategorization, naming inconsistencies, or orphaned tools. Naming follows the expected
verb_nounconvention (e.g.list_*,get_*,search_*) and consolidated multi-method tools (issue_read,pull_request_read,actions_get,projects_get).JSON Mapping Comparison
Summary — comparing the live MCP server against the JSON mapping:
Extra Tools (in MCP but not in JSON)
list_issue_fieldsAction: Created pull request #aw_pr1 (
[mcp-tools] Add list_issue_fields to issues toolset mapping) addinglist_issue_fieldsto theissuestoolset in alphabetical order.Changes Since Last Report
New Tools Added ✨
list_issue_fieldsRemoved Tools 🗑️ · Moved Tools 🔄
None — no tools were removed or re-categorized since the last report.
Tools by Toolset
Core: context · repos · issues · pull_requests (click to expand)
repos Toolset — Repository operations
Source: repositories.go
get_commitget_file_contentsget_latest_releaseget_release_by_tagget_taglist_brancheslist_commitslist_releaseslist_repository_collaboratorslist_tagsissues Toolset — Issue management
Source: issues.go
issue_readlist_issue_fields✨list_issue_typeslist_issuessearch_issuespull_requests Toolset — PR operations
Source: pullrequests.go
list_pull_requestspull_request_readsearch_pull_requestsSearch & discovery: search · users · orgs · stargazers · gists · git (click to expand)
search Toolset — Source: search.go
search_codesearch_commitssearch_orgssearch_repositoriessearch_userssemantic_issue_similarity_searchsemantic_issues_searchorgs · gists · git · stargazers
list_org_repository_security_advisoriesget_gist,list_gistsget_repository_treelist_starred_repositoriesAutomation: actions · notifications · projects · discussions · labels (click to expand)
actions_get,actions_list,get_job_logsget_notification_details,list_notificationsprojects_get,projects_listget_discussion,get_discussion_comments,list_discussion_categories,list_discussionsget_label,list_labelSecurity: code_security · dependabot · secret_protection · security_advisories (click to expand)
get_code_scanning_alert,list_code_scanning_alertsget_dependabot_alert,list_dependabot_alertsget_secret_scanning_alert,list_secret_scanning_alerts,run_secret_scanningcheck_dependency_vulnerabilities,get_global_security_advisory,list_global_security_advisories,list_repository_security_advisoriesRemote-only: copilot_spaces · github_support_docs_search (click to expand)
get_copilot_space,list_copilot_spacesgithub_support_docs_searchRecommended Default Toolsets
Recommended Defaults:
context,repos,issues,pull_requestsRationale:
context— identity/team awareness (get_me,get_teams), essential for any GitHub-aware agent.repos— core file/commit/branch reads needed by most workflows.issues— read/comment/create, common in CI/CD and automation.pull_requests— read/create/review, critical for code-review and merge automation.These match the current
[default]set; no change recommended. The newlist_issue_fieldslands in the already-defaultissuestoolset, so defaults stay current automatically.Specialized (enable explicitly):
actions(CI),discussions, the four security toolsets (audits),projects(requires PAT, notGITHUB_TOKEN),notifications,gists,labels,orgs,stargazers,users, and the remote-onlycopilot_spaces/github_support_docs_search.Notes and Observations
list_issue_fields) reflects GitHub's rollout of custom issue field definitions; it complementslist_issue_typesand pairs withlist_issuesfield filtering.mode: remotein GitHub Actions —GITHUB_TOKENlacks MCP access; defaultmode: local(Docker) should be used. This report enumerates the remote surface for documentation parity only.Methodology
Self-inspection of
mcp__github__*tools in the read-only remote session. Diff: baseline = cached 2026-05-31 (56 tools); current = 57 → addedlist_issue_fields. Mapping: github_toolsets_permissions.json · server source: github/github-mcp-server.References:
Beta Was this translation helpful? Give feedback.
All reactions