From a019b7e233f7f634595f31839f068ddeb5df98eb Mon Sep 17 00:00:00 2001 From: Copilot <223556219+Copilot@users.noreply.github.com> Date: Thu, 12 Nov 2026 05:45:23 +0000 Subject: [PATCH 01/33] [Copilot Dreaming] Return registrable tools from SDK migrations A migrated constructor returning the documented tuple cannot enter the current tool registry. Following its ServerTool contract avoids an integration repair while preserving generic handler support. https://github.com/github/github-mcp-server/blob/6fbcd00b2034502ba3001a49dfaf93593aee7069/pkg/github/tools.go#L215-L224 https://github.com/github/github-mcp-server/blob/6fbcd00b2034502ba3001a49dfaf93593aee7069/pkg/github/dependencies.go#L229-L263 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> --- .github/agents/go-sdk-tool-migrator.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/agents/go-sdk-tool-migrator.md b/.github/agents/go-sdk-tool-migrator.md index f8003fd252..3520cf50ce 100644 --- a/.github/agents/go-sdk-tool-migrator.md +++ b/.github/agents/go-sdk-tool-migrator.md @@ -15,7 +15,7 @@ When generating the migration guide, consider the following aspects: * The initial tool file and its corresponding test file will have the `//go:build ignore` build tag, as the tests will fail if the code is not ignored. The `ignore` build tag should be removed before work begins. * The import for `github.com/mark3labs/mcp-go/mcp` should be changed to `github.com/modelcontextprotocol/go-sdk/mcp` -* The return type for the tool constructor function should be updated from `mcp.Tool, server.ToolHandlerFunc` to `(mcp.Tool, mcp.ToolHandlerFor[map[string]any, any])`. +* The return type for the tool constructor function should be updated from `mcp.Tool, server.ToolHandlerFunc` to `inventory.ServerTool`. * The tool handler function signature should be updated to use generics, changing from `func(ctx context.Context, mcp.CallToolRequest) (*mcp.CallToolResult, error)` to `func(context.Context, *mcp.CallToolRequest, map[string]any) (*mcp.CallToolResult, any, error)`. * The `RequiredParam`, `RequiredInt`, `RequiredBigInt`, `OptionalParamOK`, `OptionalParam`, `OptionalIntParam`, `OptionalIntParamWithDefault`, `OptionalBoolParamWithDefault`, `OptionalStringArrayParam`, `OptionalBigIntArrayParam` and `OptionalCursorPaginationParams` functions should be changed to use the tool arguments that are now passed as a map in the tool handler function, rather than extracting them from the `mcp.CallToolRequest`. * `mcp.NewToolResultText`, `mcp.NewToolResultError`, `mcp.NewToolResultErrorFromErr` and `mcp.NewToolResultResource` no longer available in `modelcontextprotocol/go-sdk`. There are a few helper functions available in `pkg/utils/result.go` that can be used to replace these, in the `utils` package. From 7676f7210f8e5bc4fdaa65c3b03331a74842c320 Mon Sep 17 00:00:00 2001 From: Copilot <223556219+Copilot@users.noreply.github.com> Date: Thu, 12 Nov 2026 05:45:23 +0000 Subject: [PATCH 02/33] [Copilot Dreaming] Distinguish schema components from constructor results A bare Tool example can be mistaken for the complete constructor result even though registration needs its wrapper. Identifying the component avoids that contradiction without changing the illustrated input contract. https://github.com/github/github-mcp-server/blob/6fbcd00b2034502ba3001a49dfaf93593aee7069/pkg/github/dependabot.go#L21-L51 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> --- .github/agents/go-sdk-tool-migrator.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/.github/agents/go-sdk-tool-migrator.md b/.github/agents/go-sdk-tool-migrator.md index 3520cf50ce..7ec97e8f34 100644 --- a/.github/agents/go-sdk-tool-migrator.md +++ b/.github/agents/go-sdk-tool-migrator.md @@ -60,11 +60,11 @@ return mcp.NewTool( ... ``` -The corresponding input schema in modelcontextprotocol/go-sdk would look like this: +The `mcp.Tool` component of the migrated `inventory.ServerTool` would look like this: ```go ... -return mcp.Tool{ +mcp.Tool{ Name: "list_dependabot_alerts", Description: t("TOOL_LIST_DEPENDABOT_ALERTS_DESCRIPTION", "List dependabot alerts in a GitHub repository."), Annotations: &mcp.ToolAnnotations{ From ed25d278a8bbafa942ef3fe257ba86df84c38529 Mon Sep 17 00:00:00 2001 From: Copilot <223556219+Copilot@users.noreply.github.com> Date: Thu, 12 Nov 2026 05:45:23 +0000 Subject: [PATCH 03/33] [Copilot Dreaming] Use the supported JSON default in migration examples Copying the string default does not match the repository's JSON-encoded schema default. Using the established representation avoids a compilation repair while preserving the same default value and enum. https://github.com/github/github-mcp-server/blob/6fbcd00b2034502ba3001a49dfaf93593aee7069/pkg/github/dependabot.go#L113-L118 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> --- .github/agents/go-sdk-tool-migrator.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/agents/go-sdk-tool-migrator.md b/.github/agents/go-sdk-tool-migrator.md index 7ec97e8f34..f06d129bc8 100644 --- a/.github/agents/go-sdk-tool-migrator.md +++ b/.github/agents/go-sdk-tool-migrator.md @@ -86,7 +86,7 @@ mcp.Tool{ Type: "string", Description: "Filter dependabot alerts by state. Defaults to open", Enum: []any{"open", "fixed", "dismissed", "auto_dismissed"}, - Default: "open", + Default: json.RawMessage(`"open"`), }, "severity": { Type: "string", From 5c568a1d4858d32bc8320962e5ba68d26a587139 Mon Sep 17 00:00:00 2001 From: Copilot <223556219+Copilot@users.noreply.github.com> Date: Thu, 12 Nov 2026 05:45:23 +0000 Subject: [PATCH 04/33] [Copilot Dreaming] Remove the prediction that every migration breaks snapshots Equivalent schemas pass the snapshot comparison, so predicting an inevitable failure can encourage unnecessary regeneration. The update command and intentional-change safeguard remain available when a real mismatch occurs. https://github.com/github/github-mcp-server/blob/6fbcd00b2034502ba3001a49dfaf93593aee7069/internal/toolsnaps/toolsnaps.go#L47-L66 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> --- .github/agents/go-sdk-tool-migrator.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/agents/go-sdk-tool-migrator.md b/.github/agents/go-sdk-tool-migrator.md index f06d129bc8..ce13a7fe12 100644 --- a/.github/agents/go-sdk-tool-migrator.md +++ b/.github/agents/go-sdk-tool-migrator.md @@ -103,7 +103,7 @@ mcp.Tool{ After migrating the tool code and test file, ensure that all tests pass successfully. If any tests fail, review the error messages and adjust the migrated code as necessary to resolve any issues. If you encounter any challenges or need further assistance during the migration process, please let me know. -At the end of your changes, you will continue to have an issue with the `toolsnaps` tests, these validate that the schema has not changed unexpectedly. You can update the snapshots by setting `UPDATE_TOOLSNAPS=true` before running the tests, e.g.: +You can update the snapshots by setting `UPDATE_TOOLSNAPS=true` before running the tests, e.g.: ```bash UPDATE_TOOLSNAPS=true go test ./... From 9c0c5297cba14beeb9bb3c6f760708140c126d5c Mon Sep 17 00:00:00 2001 From: Copilot <223556219+Copilot@users.noreply.github.com> Date: Thu, 12 Nov 2026 05:45:23 +0000 Subject: [PATCH 05/33] [Copilot Dreaming] Remove argument ordering as a required snapshot change The snapshot comparator ignores array order. Treating ordering as an unavoidable mismatch can prompt needless snapshot churn; the requirement for logically equivalent schemas remains in the same paragraph. https://github.com/github/github-mcp-server/blob/6fbcd00b2034502ba3001a49dfaf93593aee7069/internal/toolsnaps/toolsnaps.go#L58-L66 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> --- .github/agents/go-sdk-tool-migrator.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/agents/go-sdk-tool-migrator.md b/.github/agents/go-sdk-tool-migrator.md index ce13a7fe12..3415c511a7 100644 --- a/.github/agents/go-sdk-tool-migrator.md +++ b/.github/agents/go-sdk-tool-migrator.md @@ -109,4 +109,4 @@ You can update the snapshots by setting `UPDATE_TOOLSNAPS=true` before running t UPDATE_TOOLSNAPS=true go test ./... ``` -You should however, only update the toolsnaps after confirming that the schema changes are intentional and correct. Some schema changes are unavoidable, such as argument ordering, however the schemas themselves should remain logically equivalent. +You should however, only update the toolsnaps after confirming that the schema changes are intentional and correct. Some schema changes are unavoidable, however the schemas themselves should remain logically equivalent. From 77a1159c5c3dfd5ecd52e0a0948fd3b780246e9d Mon Sep 17 00:00:00 2001 From: Copilot <223556219+Copilot@users.noreply.github.com> Date: Thu, 12 Nov 2026 05:45:23 +0000 Subject: [PATCH 06/33] [Copilot Dreaming] Remove the misleading repository-size shortcut The tracked Go-file inventory is larger than this fixed total. A stale size shortcut risks narrowing exploration prematurely and adds upkeep as the repository grows; current tracked paths remain the authority. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> --- .github/copilot-instructions.md | 1 - 1 file changed, 1 deletion(-) diff --git a/.github/copilot-instructions.md b/.github/copilot-instructions.md index 0db7990bc4..b11e7e8b5f 100644 --- a/.github/copilot-instructions.md +++ b/.github/copilot-instructions.md @@ -10,7 +10,6 @@ This is the **GitHub MCP Server**, a Model Context Protocol (MCP) server that co - **Primary Package:** github-mcp-server (stdio MCP server - **this is the main focus**) - **Secondary Package:** mcpcurl (testing utility - don't break it, but not the priority) - **Framework:** Uses modelcontextprotocol/go-sdk for MCP protocol, google/go-github for GitHub API -- **Size:** ~60MB repository, 70 Go files - **Library Usage:** This repository is also used as a library by the remote server. Functions that could be called by other repositories should be exported (capitalized), even if not required internally. Preserve existing export patterns. **Code Quality Standards:** From f6e4e03fb17ef0a46b22e998a7b93b7dde5de472 Mon Sep 17 00:00:00 2001 From: Copilot <223556219+Copilot@users.noreply.github.com> Date: Thu, 12 Nov 2026 05:45:23 +0000 Subject: [PATCH 07/33] [Copilot Dreaming] Make the focused unit-test example select a real test The old selector names no test in the stated package and can return success without exercising GetMe. Selecting the defined unit test avoids that falsely reassuring result. https://github.com/github/github-mcp-server/blob/6fbcd00b2034502ba3001a49dfaf93593aee7069/pkg/github/context_tools_test.go#L22-L31 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> --- .github/copilot-instructions.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/copilot-instructions.md b/.github/copilot-instructions.md index b11e7e8b5f..c23e07407b 100644 --- a/.github/copilot-instructions.md +++ b/.github/copilot-instructions.md @@ -55,7 +55,7 @@ go build -v ./cmd/github-mcp-server go test ./pkg/github -v # Run specific test -go test ./pkg/github -run TestGetMe +go test ./pkg/github -run Test_GetMe ``` ## Project Structure From 72db01b4f737fa8334d57bc445d265e0546ea76a Mon Sep 17 00:00:00 2001 From: Copilot <223556219+Copilot@users.noreply.github.com> Date: Thu, 12 Nov 2026 05:45:23 +0000 Subject: [PATCH 08/33] [Copilot Dreaming] Point toolset exploration at its existing package pkg/toolsets is absent from the tracked checkout. The inventory builder owns toolset configuration, so directing exploration there avoids a dead-end package search. https://github.com/github/github-mcp-server/blob/6fbcd00b2034502ba3001a49dfaf93593aee7069/pkg/inventory/builder.go#L98-L120 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> --- .github/copilot-instructions.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/copilot-instructions.md b/.github/copilot-instructions.md index c23e07407b..36cebbd86c 100644 --- a/.github/copilot-instructions.md +++ b/.github/copilot-instructions.md @@ -70,7 +70,7 @@ go test ./pkg/github -run Test_GetMe ├── pkg/ # Public API packages │ ├── github/ # GitHub API MCP tools implementation │ │ └── __toolsnaps__/ # Tool schema snapshots (*.snap files) -│ ├── toolsets/ # Toolset configuration & management +│ ├── inventory/ # Toolset configuration & management │ ├── errors/ # Error handling utilities │ ├── sanitize/ # HTML/content sanitization │ ├── log/ # Logging utilities From cf7fb340f363ad7833a0f8e79e8e8f3b711c17b7 Mon Sep 17 00:00:00 2001 From: Copilot <223556219+Copilot@users.noreply.github.com> Date: Thu, 12 Nov 2026 05:45:23 +0000 Subject: [PATCH 09/33] [Copilot Dreaming] Match ignore guidance to the configured filename pattern The wider wildcard can make Copilot assume filenames are ignored that the actual pattern does not match. Following the owning ignore entry avoids that staging assumption. https://github.com/github/github-mcp-server/blob/6fbcd00b2034502ba3001a49dfaf93593aee7069/.gitignore#L16-L17 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> --- .github/copilot-instructions.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/copilot-instructions.md b/.github/copilot-instructions.md index 36cebbd86c..9d6d3dad25 100644 --- a/.github/copilot-instructions.md +++ b/.github/copilot-instructions.md @@ -96,7 +96,7 @@ go test ./pkg/github -run Test_GetMe - **Dockerfile:** Multi-stage build (golang:1.27.3-alpine → distroless) - **server.json:** MCP server metadata for registry - **.goreleaser.yaml:** Release automation config -- **.gitignore:** Excludes bin/, dist/, vendor/, *.DS_Store, github-mcp-server binary +- **.gitignore:** Excludes bin/, dist/, vendor/, .DS_Store, github-mcp-server binary ### Important Scripts (script/ directory) From 8ecde4827b0d0ef9c41ce9cf1c788c9b985ce400 Mon Sep 17 00:00:00 2001 From: Copilot <223556219+Copilot@users.noreply.github.com> Date: Thu, 12 Nov 2026 05:45:23 +0000 Subject: [PATCH 10/33] [Copilot Dreaming] Remove the repeated catalogue lint mandate The same reader already receives the exact lint script and pre-commit obligation in the required command sequence. Another copy adds upkeep without a different trigger; that sequence still requires lint before finishing or committing. https://github.com/github/github-mcp-server/blob/6fbcd00b2034502ba3001a49dfaf93593aee7069/.github/copilot-instructions.md#L25-L30 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> --- .github/copilot-instructions.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/copilot-instructions.md b/.github/copilot-instructions.md index 9d6d3dad25..27146e1500 100644 --- a/.github/copilot-instructions.md +++ b/.github/copilot-instructions.md @@ -100,7 +100,7 @@ go test ./pkg/github -run Test_GetMe ### Important Scripts (script/ directory) -- **script/lint** - Runs `gofmt` + `golangci-lint`. **MUST RUN** before committing +- **script/lint** - Runs `gofmt` + `golangci-lint`. - **script/test** - Runs `go test -race ./...` (full test suite) - **script/generate-docs** - Updates README.md tool documentation. Run after tool changes - **script/licenses** - Updates third-party license files when dependencies change From fc38e1fb257cd80bd050a12116870e4134c6c951 Mon Sep 17 00:00:00 2001 From: Copilot <223556219+Copilot@users.noreply.github.com> Date: Thu, 12 Nov 2026 05:45:23 +0000 Subject: [PATCH 11/33] [Copilot Dreaming] Remove the repeated catalogue documentation mandate The required command sequence already covers documentation generation after tool or toolset changes for the same reader. Maintaining the narrower catalogue repeat adds upkeep; the generation obligation remains in that sequence. https://github.com/github/github-mcp-server/blob/6fbcd00b2034502ba3001a49dfaf93593aee7069/.github/copilot-instructions.md#L25-L31 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> --- .github/copilot-instructions.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/copilot-instructions.md b/.github/copilot-instructions.md index 27146e1500..72ecd79ab0 100644 --- a/.github/copilot-instructions.md +++ b/.github/copilot-instructions.md @@ -102,7 +102,7 @@ go test ./pkg/github -run Test_GetMe - **script/lint** - Runs `gofmt` + `golangci-lint`. - **script/test** - Runs `go test -race ./...` (full test suite) -- **script/generate-docs** - Updates README.md tool documentation. Run after tool changes +- **script/generate-docs** - Updates README.md tool documentation. - **script/licenses** - Updates third-party license files when dependencies change - **script/licenses-check** - Validates license compliance (runs in CI) - **script/get-me** - Quick test script for get_me tool From 5be8ccb31fad0f995907c3fb1757c37040034a18 Mon Sep 17 00:00:00 2001 From: Copilot <223556219+Copilot@users.noreply.github.com> Date: Thu, 12 Nov 2026 05:45:23 +0000 Subject: [PATCH 12/33] [Copilot Dreaming] Remove the blanket workflow-trigger assertion Release-only workflows are not selected by ordinary branch or pull-request updates. Removing the universal event assertion avoids expecting those release jobs during routine development; the separate merge-policy sentence remains unchanged. https://github.com/github/github-mcp-server/blob/6fbcd00b2034502ba3001a49dfaf93593aee7069/.github/workflows/goreleaser.yml#L1-L5 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> --- .github/copilot-instructions.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/copilot-instructions.md b/.github/copilot-instructions.md index 72ecd79ab0..bdfbaaeb7f 100644 --- a/.github/copilot-instructions.md +++ b/.github/copilot-instructions.md @@ -111,7 +111,7 @@ go test ./pkg/github -run Test_GetMe ## GitHub Workflows (CI/CD) -All workflows run on push/PR unless noted. Located in `.github/workflows/`: +Located in `.github/workflows/`: 1. **go.yml** - Build and test on ubuntu/windows/macos. Runs `script/test` and builds binary 2. **lint.yml** - Runs golangci-lint-action v2.5 (GitHub Action) with actions/setup-go stable From a71cbe89ce67e8d6b1e58e4f2a92342719d174d8 Mon Sep 17 00:00:00 2001 From: Copilot <223556219+Copilot@users.noreply.github.com> Date: Thu, 12 Nov 2026 05:45:23 +0000 Subject: [PATCH 13/33] [Copilot Dreaming] Match documented lint setup to configured CI Lint CI reads the Go version from go.mod and uses action v9. Accurate setup references avoid directing Copilot toward a different lint runtime. https://github.com/github/github-mcp-server/blob/6fbcd00b2034502ba3001a49dfaf93593aee7069/.github/workflows/lint.yml#L19-L26 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> --- .github/copilot-instructions.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/copilot-instructions.md b/.github/copilot-instructions.md index bdfbaaeb7f..1b05917964 100644 --- a/.github/copilot-instructions.md +++ b/.github/copilot-instructions.md @@ -114,7 +114,7 @@ go test ./pkg/github -run Test_GetMe Located in `.github/workflows/`: 1. **go.yml** - Build and test on ubuntu/windows/macos. Runs `script/test` and builds binary -2. **lint.yml** - Runs golangci-lint-action v2.5 (GitHub Action) with actions/setup-go stable +2. **lint.yml** - Runs golangci-lint-action v9 (GitHub Action) with actions/setup-go reading `go.mod` 3. **docs-check.yml** - Verifies README.md is up-to-date by running generate-docs and checking git diff 4. **code-scanning.yml** - CodeQL security analysis for Go and GitHub Actions 5. **license-check.yml** - Runs `script/licenses-check` to validate compliance From fb62d5946e3084c61b845151710a356a0aa9b821 Mon Sep 17 00:00:00 2001 From: Copilot <223556219+Copilot@users.noreply.github.com> Date: Thu, 12 Nov 2026 05:45:23 +0000 Subject: [PATCH 14/33] [Copilot Dreaming] Identify the actual release trigger The release workflow selects version-tag pushes rather than main-branch pushes. Correct trigger guidance avoids expecting releases from routine branch updates; prohibitions on the release script and tag pushes remain in the instructions. https://github.com/github/github-mcp-server/blob/6fbcd00b2034502ba3001a49dfaf93593aee7069/.github/workflows/goreleaser.yml#L1-L5 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> --- .github/copilot-instructions.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/copilot-instructions.md b/.github/copilot-instructions.md index 1b05917964..67ccaf38c6 100644 --- a/.github/copilot-instructions.md +++ b/.github/copilot-instructions.md @@ -119,7 +119,7 @@ Located in `.github/workflows/`: 4. **code-scanning.yml** - CodeQL security analysis for Go and GitHub Actions 5. **license-check.yml** - Runs `script/licenses-check` to validate compliance 6. **docker-publish.yml** - Publishes container image to ghcr.io -7. **goreleaser.yml** - Creates releases (main branch only) +7. **goreleaser.yml** - Creates releases (version tags) 8. **registry-releaser.yml** - Updates MCP registry **All of these must pass for PR merge.** If docs-check fails, run `script/generate-docs` and commit changes. From 567c4cd2be104e486407c60874e547b6d0784ffc Mon Sep 17 00:00:00 2001 From: Copilot <223556219+Copilot@users.noreply.github.com> Date: Thu, 12 Nov 2026 05:45:23 +0000 Subject: [PATCH 15/33] [Copilot Dreaming] Remove the categorical exclusion of external test packages The repository has unit tests in an external package. The categorical aside could prompt needless package rewrites during maintenance; alongside-file placement and the test framework guidance remain. https://github.com/github/github-mcp-server/blob/6fbcd00b2034502ba3001a49dfaf93593aee7069/pkg/github/dependencies_test.go#L1-L18 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> --- .github/copilot-instructions.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/copilot-instructions.md b/.github/copilot-instructions.md index 67ccaf38c6..6d2e0fd540 100644 --- a/.github/copilot-instructions.md +++ b/.github/copilot-instructions.md @@ -129,7 +129,7 @@ Located in `.github/workflows/`: ### Unit Tests - Use `testify` for assertions (`require` for critical checks, `assert` for non-blocking) -- Tests are in `*_test.go` files alongside implementation (internal tests, not `_test` package) +- Tests are in `*_test.go` files alongside implementation - Mock GitHub API with `go-github-mock` (REST) or `githubv4mock` (GraphQL) - Test structure for tools: 1. Test tool snapshot From 3c5977fd93f6194b37c2ec07e328e7d8684eba70 Mon Sep 17 00:00:00 2001 From: Copilot <223556219+Copilot@users.noreply.github.com> Date: Thu, 12 Nov 2026 05:45:23 +0000 Subject: [PATCH 16/33] [Copilot Dreaming] Use the repository REST mocking helper The repository replaced the former mock dependency with local HTTP helpers. Directing new tests to the current helper avoids rediscovering that replacement while leaving GraphQL mocking unchanged. https://github.com/github/github-mcp-server/blob/6fbcd00b2034502ba3001a49dfaf93593aee7069/pkg/github/helper_test.go#L681-L695 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> --- .github/copilot-instructions.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/copilot-instructions.md b/.github/copilot-instructions.md index 6d2e0fd540..7e596df8fe 100644 --- a/.github/copilot-instructions.md +++ b/.github/copilot-instructions.md @@ -130,7 +130,7 @@ Located in `.github/workflows/`: - Use `testify` for assertions (`require` for critical checks, `assert` for non-blocking) - Tests are in `*_test.go` files alongside implementation -- Mock GitHub API with `go-github-mock` (REST) or `githubv4mock` (GraphQL) +- Mock GitHub API with `MockHTTPClientWithHandlers` (REST) or `githubv4mock` (GraphQL) - Test structure for tools: 1. Test tool snapshot 2. Verify critical schema properties (e.g., ReadOnly annotation) From f41418d59ed885418300dbf4bb3beac623574528 Mon Sep 17 00:00:00 2001 From: Copilot <223556219+Copilot@users.noreply.github.com> Date: Thu, 12 Nov 2026 05:45:23 +0000 Subject: [PATCH 17/33] [Copilot Dreaming] Remove the repeated wide-audience clarity rule The same reader already receives the wide-audience clarity duty in the repository-wide quality standards. Keeping another equivalent mandate adds upkeep without a separate task trigger; that quality rule remains. https://github.com/github/github-mcp-server/blob/6fbcd00b2034502ba3001a49dfaf93593aee7069/.github/copilot-instructions.md#L18-L18 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> --- .github/copilot-instructions.md | 1 - 1 file changed, 1 deletion(-) diff --git a/.github/copilot-instructions.md b/.github/copilot-instructions.md index 7e596df8fe..1ad5166849 100644 --- a/.github/copilot-instructions.md +++ b/.github/copilot-instructions.md @@ -173,7 +173,6 @@ Located in `.github/workflows/`: ### Code Patterns - **Keep changes minimal and focused** on the specific issue being addressed -- **Prefer clarity over cleverness** - code must be understandable by a wide audience - **Atomic commits** - each commit should be a complete, logical change - **Maintain or improve structure** - never degrade code organization - Use table-driven tests for behavioral testing From 6ede3c7aaef0a7789b1da9109a00e8fee5ba63cc Mon Sep 17 00:00:00 2001 From: Copilot <223556219+Copilot@users.noreply.github.com> Date: Thu, 12 Nov 2026 05:45:23 +0000 Subject: [PATCH 18/33] [Copilot Dreaming] Remove the repeated atomic-commit rule The repository-wide clean-commit standard already gives the same reader the atomic, focused commit duty. Another copy adds upkeep without changing the action; that standard remains. https://github.com/github/github-mcp-server/blob/6fbcd00b2034502ba3001a49dfaf93593aee7069/.github/copilot-instructions.md#L19-L19 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> --- .github/copilot-instructions.md | 1 - 1 file changed, 1 deletion(-) diff --git a/.github/copilot-instructions.md b/.github/copilot-instructions.md index 1ad5166849..a4e25b4458 100644 --- a/.github/copilot-instructions.md +++ b/.github/copilot-instructions.md @@ -173,7 +173,6 @@ Located in `.github/workflows/`: ### Code Patterns - **Keep changes minimal and focused** on the specific issue being addressed -- **Atomic commits** - each commit should be a complete, logical change - **Maintain or improve structure** - never degrade code organization - Use table-driven tests for behavioral testing - Comment sparingly - code should be self-documenting From aa2d75f9b4ad9a51503cbd6ddb7d0be73e1149a3 Mon Sep 17 00:00:00 2001 From: Copilot <223556219+Copilot@users.noreply.github.com> Date: Thu, 12 Nov 2026 05:45:23 +0000 Subject: [PATCH 19/33] [Copilot Dreaming] Remove the repeated structure-protection rule The repository-wide quality standard already gives the same reader the maintain-or-improve duty and the prohibition on degradation. Maintaining a second equivalent rule adds upkeep; the original protection remains. https://github.com/github/github-mcp-server/blob/6fbcd00b2034502ba3001a49dfaf93593aee7069/.github/copilot-instructions.md#L20-L20 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> --- .github/copilot-instructions.md | 1 - 1 file changed, 1 deletion(-) diff --git a/.github/copilot-instructions.md b/.github/copilot-instructions.md index a4e25b4458..7700762899 100644 --- a/.github/copilot-instructions.md +++ b/.github/copilot-instructions.md @@ -173,7 +173,6 @@ Located in `.github/workflows/`: ### Code Patterns - **Keep changes minimal and focused** on the specific issue being addressed -- **Maintain or improve structure** - never degrade code organization - Use table-driven tests for behavioral testing - Comment sparingly - code should be self-documenting - Follow standard Go conventions (Effective Go, Go proverbs) From c0c8f1971791c9ed131197136d495b77edea6f48 Mon Sep 17 00:00:00 2001 From: Copilot <223556219+Copilot@users.noreply.github.com> Date: Thu, 12 Nov 2026 05:45:23 +0000 Subject: [PATCH 20/33] [Copilot Dreaming] Remove the repeated comment-restraint rule The repository-wide self-documenting-code standard already limits the same reader to necessary comments. The extra copy adds upkeep without another condition; that restriction remains in the quality standards. https://github.com/github/github-mcp-server/blob/6fbcd00b2034502ba3001a49dfaf93593aee7069/.github/copilot-instructions.md#L21-L21 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> --- .github/copilot-instructions.md | 1 - 1 file changed, 1 deletion(-) diff --git a/.github/copilot-instructions.md b/.github/copilot-instructions.md index 7700762899..9b88580d49 100644 --- a/.github/copilot-instructions.md +++ b/.github/copilot-instructions.md @@ -174,7 +174,6 @@ Located in `.github/workflows/`: - **Keep changes minimal and focused** on the specific issue being addressed - Use table-driven tests for behavioral testing -- Comment sparingly - code should be self-documenting - Follow standard Go conventions (Effective Go, Go proverbs) - **Test changes thoroughly** before committing - Export functions (capitalize) if they could be used by other repos as a library From c3496015e8a84be73425cc384b0d136878472a73 Mon Sep 17 00:00:00 2001 From: Copilot <223556219+Copilot@users.noreply.github.com> Date: Thu, 12 Nov 2026 05:45:23 +0000 Subject: [PATCH 21/33] [Copilot Dreaming] Remove the repeated library-export rule The library-usage standard already requires exports for potential external callers and protects existing export patterns. Maintaining a narrower copy adds upkeep; the complete duty remains in that standard. https://github.com/github/github-mcp-server/blob/6fbcd00b2034502ba3001a49dfaf93593aee7069/.github/copilot-instructions.md#L14-L14 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> --- .github/copilot-instructions.md | 1 - 1 file changed, 1 deletion(-) diff --git a/.github/copilot-instructions.md b/.github/copilot-instructions.md index 9b88580d49..9567105144 100644 --- a/.github/copilot-instructions.md +++ b/.github/copilot-instructions.md @@ -176,7 +176,6 @@ Located in `.github/workflows/`: - Use table-driven tests for behavioral testing - Follow standard Go conventions (Effective Go, Go proverbs) - **Test changes thoroughly** before committing -- Export functions (capitalize) if they could be used by other repos as a library ## Common Development Workflows From 7593fc4a061181ab995b0abadd17493f980835a6 Mon Sep 17 00:00:00 2001 From: Copilot <223556219+Copilot@users.noreply.github.com> Date: Thu, 12 Nov 2026 05:45:23 +0000 Subject: [PATCH 22/33] [Copilot Dreaming] Register new tools at the existing registry pkg/toolsets is absent from the checkout, while the tool registry collects constructors in pkg/github/tools.go. Naming the actual registration owner avoids a dead-end branch of the new-tool recipe. https://github.com/github/github-mcp-server/blob/6fbcd00b2034502ba3001a49dfaf93593aee7069/pkg/github/tools.go#L215-L224 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> --- .github/copilot-instructions.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/copilot-instructions.md b/.github/copilot-instructions.md index 9567105144..60757a029b 100644 --- a/.github/copilot-instructions.md +++ b/.github/copilot-instructions.md @@ -182,7 +182,7 @@ Located in `.github/workflows/`: ### Adding a New MCP Tool 1. Add tool implementation in `pkg/github/` (e.g., `foo_tools.go`) -2. Register tool in appropriate toolset in `pkg/github/` or `pkg/toolsets/` +2. Register tool in appropriate toolset in `pkg/github/tools.go` 3. Write unit tests following the tool test pattern 4. Run `UPDATE_TOOLSNAPS=true go test ./...` to create snapshot 5. Run `script/generate-docs` to update README From e79d948b83957d7d89de71abca31d7341d97519a Mon Sep 17 00:00:00 2001 From: Copilot <223556219+Copilot@users.noreply.github.com> Date: Thu, 12 Nov 2026 05:45:23 +0000 Subject: [PATCH 23/33] [Copilot Dreaming] Document PAT authentication without making it mandatory Stdio supports personal tokens, OAuth, and GitHub App authentication. Treating one input as universally required can prompt unnecessary setup; its supported optional role remains documented alongside the separate E2E input. https://github.com/github/github-mcp-server/blob/6fbcd00b2034502ba3001a49dfaf93593aee7069/cmd/github-mcp-server/main.go#L49-L77 https://github.com/github/github-mcp-server/blob/6fbcd00b2034502ba3001a49dfaf93593aee7069/e2e/e2e_test.go#L47-L55 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> --- .github/copilot-instructions.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/copilot-instructions.md b/.github/copilot-instructions.md index 60757a029b..592f6114a0 100644 --- a/.github/copilot-instructions.md +++ b/.github/copilot-instructions.md @@ -233,7 +233,7 @@ Located in `.github/workflows/`: ## Environment Variables -- **GITHUB_PERSONAL_ACCESS_TOKEN** - Required for server operation and e2e tests +- **GITHUB_PERSONAL_ACCESS_TOKEN** - Optional PAT authentication for the stdio server; OAuth and GitHub App authentication are alternatives. - **GITHUB_HOST** - For GitHub Enterprise Server (prefix with `https://`) - **GITHUB_TOOLSETS** - Comma-separated toolset list (overrides --toolsets flag) - **GITHUB_READ_ONLY** - Set to "1" for read-only mode From b893875325821b4d3fc72a39fd5faa2c6f279219 Mon Sep 17 00:00:00 2001 From: Copilot <223556219+Copilot@users.noreply.github.com> Date: Thu, 12 Nov 2026 05:45:23 +0000 Subject: [PATCH 24/33] [Copilot Dreaming] Remove the false default-stdio qualifier The native root command has no server run action; stdio is an explicit subcommand. Removing the qualifier avoids expecting bare invocation to start the server, without changing the stdio command or Docker's distinct default. https://github.com/github/github-mcp-server/blob/6fbcd00b2034502ba3001a49dfaf93593aee7069/cmd/github-mcp-server/main.go#L30-L42 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> --- .github/copilot-instructions.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/copilot-instructions.md b/.github/copilot-instructions.md index 592f6114a0..87e03a1038 100644 --- a/.github/copilot-instructions.md +++ b/.github/copilot-instructions.md @@ -264,7 +264,7 @@ server.json - MCP server registry metadata ### Main Entry Point `cmd/github-mcp-server/main.go` - Uses cobra for CLI, viper for config, supports: -- `stdio` command (default) - MCP stdio transport +- `stdio` command - MCP stdio transport - `generate-docs` command - Documentation generation - Flags: --toolsets, --read-only, --gh-host, --log-file From d89361e0a5254673a07c05ac80d6442434c194f9 Mon Sep 17 00:00:00 2001 From: Copilot <223556219+Copilot@users.noreply.github.com> Date: Thu, 12 Nov 2026 05:45:23 +0000 Subject: [PATCH 25/33] [Copilot Dreaming] Remove the repeated local-server priority reminder The same reader already receives the local stdio server's primary-package priority at the start of the instructions. Maintaining a second reminder adds upkeep without a new audience or trigger; the primary-package rule remains. https://github.com/github/github-mcp-server/blob/6fbcd00b2034502ba3001a49dfaf93593aee7069/.github/copilot-instructions.md#L10-L10 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> --- .github/copilot-instructions.md | 1 - 1 file changed, 1 deletion(-) diff --git a/.github/copilot-instructions.md b/.github/copilot-instructions.md index 87e03a1038..d145cc36fc 100644 --- a/.github/copilot-instructions.md +++ b/.github/copilot-instructions.md @@ -270,7 +270,6 @@ server.json - MCP server registry metadata ## Important Reminders -1. **PRIMARY FOCUS:** The local stdio MCP server (github-mcp-server) - this is what you should work on and test with 2. **REMOTE SERVER:** Ignore remote server instructions when making code changes (unless specifically asked). This repo is used as a library by the remote server, so keep functions exported (capitalized) if they could be called by other repos, even if not needed internally. 3. **ALWAYS** trust these instructions first - only search if information is incomplete or incorrect 4. **NEVER** use `script/tag-release` or push tags From 36f7cc6f6b8ff3f49b9dd6ad3a51c396c296e240 Mon Sep 17 00:00:00 2001 From: Copilot <223556219+Copilot@users.noreply.github.com> Date: Thu, 12 Nov 2026 05:45:23 +0000 Subject: [PATCH 26/33] [Copilot Dreaming] Remove the repeated export sentence from the remote reminder The library-usage standard already gives the same reader this export duty, including functions unused internally. Another copy adds upkeep; that complete duty remains, and the reminder's explicit-request exception for remote work is untouched. https://github.com/github/github-mcp-server/blob/6fbcd00b2034502ba3001a49dfaf93593aee7069/.github/copilot-instructions.md#L14-L14 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> --- .github/copilot-instructions.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/copilot-instructions.md b/.github/copilot-instructions.md index d145cc36fc..3ff433bfe7 100644 --- a/.github/copilot-instructions.md +++ b/.github/copilot-instructions.md @@ -270,7 +270,7 @@ server.json - MCP server registry metadata ## Important Reminders -2. **REMOTE SERVER:** Ignore remote server instructions when making code changes (unless specifically asked). This repo is used as a library by the remote server, so keep functions exported (capitalized) if they could be called by other repos, even if not needed internally. +2. **REMOTE SERVER:** Ignore remote server instructions when making code changes (unless specifically asked). 3. **ALWAYS** trust these instructions first - only search if information is incomplete or incorrect 4. **NEVER** use `script/tag-release` or push tags 5. **NEVER** skip `script/lint` before committing Go code changes From fa238bf8653962394ea29393174499e7265a6870 Mon Sep 17 00:00:00 2001 From: Copilot <223556219+Copilot@users.noreply.github.com> Date: Thu, 12 Nov 2026 05:45:23 +0000 Subject: [PATCH 27/33] [Copilot Dreaming] Remove the repeated pre-commit lint reminder The required command sequence already names this exact script and covers finishing and committing for the same reader. A second mandate adds upkeep without another trigger; the original sequence still forbids skipping lint. https://github.com/github/github-mcp-server/blob/6fbcd00b2034502ba3001a49dfaf93593aee7069/.github/copilot-instructions.md#L25-L30 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> --- .github/copilot-instructions.md | 1 - 1 file changed, 1 deletion(-) diff --git a/.github/copilot-instructions.md b/.github/copilot-instructions.md index 3ff433bfe7..d6cbd9690c 100644 --- a/.github/copilot-instructions.md +++ b/.github/copilot-instructions.md @@ -273,7 +273,6 @@ server.json - MCP server registry metadata 2. **REMOTE SERVER:** Ignore remote server instructions when making code changes (unless specifically asked). 3. **ALWAYS** trust these instructions first - only search if information is incomplete or incorrect 4. **NEVER** use `script/tag-release` or push tags -5. **NEVER** skip `script/lint` before committing Go code changes 6. **ALWAYS** update toolsnaps when changing MCP tool schemas 7. **ALWAYS** run `script/generate-docs` after modifying tools 8. For specific test files, use `go test ./path -run TestName` not full suite From a59dbf718bf1d937822da0050403081c539de707 Mon Sep 17 00:00:00 2001 From: Copilot <223556219+Copilot@users.noreply.github.com> Date: Thu, 12 Nov 2026 05:45:23 +0000 Subject: [PATCH 28/33] [Copilot Dreaming] Remove the repeated schema-snapshot reminder The tool-change procedure already tells the same reader when to regenerate snapshots and to commit them. The reminder adds upkeep without another action; those schema-change and commit requirements remain in that procedure. https://github.com/github/github-mcp-server/blob/6fbcd00b2034502ba3001a49dfaf93593aee7069/.github/copilot-instructions.md#L35-L40 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> --- .github/copilot-instructions.md | 1 - 1 file changed, 1 deletion(-) diff --git a/.github/copilot-instructions.md b/.github/copilot-instructions.md index d6cbd9690c..b367fdfa0e 100644 --- a/.github/copilot-instructions.md +++ b/.github/copilot-instructions.md @@ -273,7 +273,6 @@ server.json - MCP server registry metadata 2. **REMOTE SERVER:** Ignore remote server instructions when making code changes (unless specifically asked). 3. **ALWAYS** trust these instructions first - only search if information is incomplete or incorrect 4. **NEVER** use `script/tag-release` or push tags -6. **ALWAYS** update toolsnaps when changing MCP tool schemas 7. **ALWAYS** run `script/generate-docs` after modifying tools 8. For specific test files, use `go test ./path -run TestName` not full suite 9. E2E tests require PAT token - you likely cannot run them From 928c667d86c1a5252c6e8eecc1f3e5ef27a4ab8e Mon Sep 17 00:00:00 2001 From: Copilot <223556219+Copilot@users.noreply.github.com> Date: Thu, 12 Nov 2026 05:45:23 +0000 Subject: [PATCH 29/33] [Copilot Dreaming] Remove the repeated generated-documentation reminder The required command sequence already covers documentation generation after tool and toolset changes for the same reader. A narrower reminder adds upkeep without another trigger; the broader obligation remains in that sequence. https://github.com/github/github-mcp-server/blob/6fbcd00b2034502ba3001a49dfaf93593aee7069/.github/copilot-instructions.md#L25-L31 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> --- .github/copilot-instructions.md | 1 - 1 file changed, 1 deletion(-) diff --git a/.github/copilot-instructions.md b/.github/copilot-instructions.md index b367fdfa0e..bcff3cd90b 100644 --- a/.github/copilot-instructions.md +++ b/.github/copilot-instructions.md @@ -273,7 +273,6 @@ server.json - MCP server registry metadata 2. **REMOTE SERVER:** Ignore remote server instructions when making code changes (unless specifically asked). 3. **ALWAYS** trust these instructions first - only search if information is incomplete or incorrect 4. **NEVER** use `script/tag-release` or push tags -7. **ALWAYS** run `script/generate-docs` after modifying tools 8. For specific test files, use `go test ./path -run TestName` not full suite 9. E2E tests require PAT token - you likely cannot run them 10. Toolsnaps are API documentation - treat changes seriously From 9dbdef54b27b04846786b425889e40c4c6b2e71d Mon Sep 17 00:00:00 2001 From: Copilot <223556219+Copilot@users.noreply.github.com> Date: Thu, 12 Nov 2026 05:45:23 +0000 Subject: [PATCH 30/33] [Copilot Dreaming] Remove the repeated live-test prerequisite reminder The E2E section already gives the same reader the token prerequisite, dedicated variable, invocation, and in-process debug exception. The extra reminder adds upkeep without another duty; those prerequisites and exception remain there. https://github.com/github/github-mcp-server/blob/6fbcd00b2034502ba3001a49dfaf93593aee7069/.github/copilot-instructions.md#L150-L156 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> --- .github/copilot-instructions.md | 1 - 1 file changed, 1 deletion(-) diff --git a/.github/copilot-instructions.md b/.github/copilot-instructions.md index bcff3cd90b..124367cf05 100644 --- a/.github/copilot-instructions.md +++ b/.github/copilot-instructions.md @@ -274,7 +274,6 @@ server.json - MCP server registry metadata 3. **ALWAYS** trust these instructions first - only search if information is incomplete or incorrect 4. **NEVER** use `script/tag-release` or push tags 8. For specific test files, use `go test ./path -run TestName` not full suite -9. E2E tests require PAT token - you likely cannot run them 10. Toolsnaps are API documentation - treat changes seriously 11. Build/test/lint are very fast (~1s each) - run frequently 12. CI failures for docs-check or license-check have simple fixes (run the script) From 873d48e0a38821ac408f15438ae0f1348a5b9ed3 Mon Sep 17 00:00:00 2001 From: Copilot <223556219+Copilot@users.noreply.github.com> Date: Thu, 12 Nov 2026 05:45:23 +0000 Subject: [PATCH 31/33] [Copilot Dreaming] Remove the repeated testing-utility priority reminder The secondary-package rule already tells the same reader not to break mcpcurl and keeps its lower priority explicit. Another reminder adds upkeep without changing scope; that protection remains in the package overview. https://github.com/github/github-mcp-server/blob/6fbcd00b2034502ba3001a49dfaf93593aee7069/.github/copilot-instructions.md#L11-L11 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> --- .github/copilot-instructions.md | 1 - 1 file changed, 1 deletion(-) diff --git a/.github/copilot-instructions.md b/.github/copilot-instructions.md index 124367cf05..d3e0f2660a 100644 --- a/.github/copilot-instructions.md +++ b/.github/copilot-instructions.md @@ -277,4 +277,3 @@ server.json - MCP server registry metadata 10. Toolsnaps are API documentation - treat changes seriously 11. Build/test/lint are very fast (~1s each) - run frequently 12. CI failures for docs-check or license-check have simple fixes (run the script) -13. mcpcurl is secondary - don't break it, but it's not the priority \ No newline at end of file From b2336924b6e0c225b943dd84e3693a6c25db6412 Mon Sep 17 00:00:00 2001 From: Copilot <223556219+Copilot@users.noreply.github.com> Date: Thu, 12 Nov 2026 05:45:23 +0000 Subject: [PATCH 32/33] [Copilot Dreaming] Keep the remaining reminder sequence readable After duplicate reminders are removed, sequential source labels make the remaining duties easier to reference. This dependent numbering cleanup changes no trigger, prohibition, exception, or validation requirement. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> --- .github/copilot-instructions.md | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/.github/copilot-instructions.md b/.github/copilot-instructions.md index d3e0f2660a..65304a60d4 100644 --- a/.github/copilot-instructions.md +++ b/.github/copilot-instructions.md @@ -270,10 +270,10 @@ server.json - MCP server registry metadata ## Important Reminders -2. **REMOTE SERVER:** Ignore remote server instructions when making code changes (unless specifically asked). -3. **ALWAYS** trust these instructions first - only search if information is incomplete or incorrect -4. **NEVER** use `script/tag-release` or push tags -8. For specific test files, use `go test ./path -run TestName` not full suite -10. Toolsnaps are API documentation - treat changes seriously -11. Build/test/lint are very fast (~1s each) - run frequently -12. CI failures for docs-check or license-check have simple fixes (run the script) +1. **REMOTE SERVER:** Ignore remote server instructions when making code changes (unless specifically asked). +2. **ALWAYS** trust these instructions first - only search if information is incomplete or incorrect +3. **NEVER** use `script/tag-release` or push tags +4. For specific test files, use `go test ./path -run TestName` not full suite +5. Toolsnaps are API documentation - treat changes seriously +6. Build/test/lint are very fast (~1s each) - run frequently +7. CI failures for docs-check or license-check have simple fixes (run the script) \ No newline at end of file From 3325166f9d82e5ae8e8ef93a2b2893a40392d540 Mon Sep 17 00:00:00 2001 From: Copilot <223556219+Copilot@users.noreply.github.com> Date: Thu, 12 Nov 2026 05:45:23 +0000 Subject: [PATCH 33/33] [Copilot Dreaming] Recover mcpcurl commands blocked by unrelated schemas During a local issue-field read, broad discovery produced no generated command and prompted source inspection. The client decodes the whole schema response before registering commands, so an incompatible schema can block the requested tool. https://github.com/github/github-mcp-server/blob/6fbcd00b2034502ba3001a49dfaf93593aee7069/cmd/mcpcurl/main.go#L39-L64 https://github.com/github/github-mcp-server/blob/6fbcd00b2034502ba3001a49dfaf93593aee7069/cmd/mcpcurl/main.go#L177-L193 Selecting only the requested tool avoids that unrelated schema. Explicit tools suppress default toolsets only when a toolset selection is not also supplied, which is why the recovery replaces the broad selection. https://github.com/github/github-mcp-server/blob/6fbcd00b2034502ba3001a49dfaf93593aee7069/pkg/github/server.go#L152-L165 https://github.com/github/github-mcp-server/blob/6fbcd00b2034502ba3001a49dfaf93593aee7069/pkg/inventory/builder.go#L98-L120 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> --- cmd/mcpcurl/README.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/cmd/mcpcurl/README.md b/cmd/mcpcurl/README.md index cf24a74358..21969dc04b 100644 --- a/cmd/mcpcurl/README.md +++ b/cmd/mcpcurl/README.md @@ -133,7 +133,9 @@ Use one of the tools: ## Dynamic Commands -All tools provided by the MCP server are automatically available as subcommands under the `tools` command. Each generated command has: +To recover a missing `mcpcurl` subcommand blocked by another tool's schema, replace `--toolsets=` with `--tools=` in the `--stdio-server-cmd` server command. + +Each generated command has: - Appropriate flags matching the tool's input schema - Validation for required parameters