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
Copy file name to clipboardExpand all lines: README.md
+6-15Lines changed: 6 additions & 15 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -247,24 +247,15 @@ For a complete overview of all installation options, see our **[Installation Gui
247
247
### Build from source
248
248
249
249
If you don't have Docker, you can use `go build` to build the binary in the
250
-
`cmd/github-mcp-server` directory, and use the `github-mcp-server stdio` command with the `GITHUB_PERSONAL_ACCESS_TOKEN` environment variable set to your token. To specify the output location of the build, use the `-o` flag. You should configure your server to use the built executable as its `command`. For example:
250
+
`cmd/github-mcp-server` directory and run the HTTP transport directly:
251
251
252
-
```JSON
253
-
{
254
-
"mcp": {
255
-
"servers": {
256
-
"github": {
257
-
"command": "/path/to/github-mcp-server",
258
-
"args": ["stdio"],
259
-
"env": {
260
-
"GITHUB_PERSONAL_ACCESS_TOKEN": "<YOUR_TOKEN>"
261
-
}
262
-
}
263
-
}
264
-
}
265
-
}
252
+
```bash
253
+
go build -o github-mcp-server ./cmd/github-mcp-server
254
+
./github-mcp-server http --listen :8080
266
255
```
267
256
257
+
> **Heads up:** Stdio transport and personal access tokens are no longer supported. The server must receive GitHub OAuth access tokens in the `Authorization` header on every request (for example, when running behind Pomerium).
258
+
268
259
### Run as an HTTP server
269
260
270
261
The same binary can expose the MCP server over HTTP using the streamable transport. This mode is designed for deployments behind zero-trust proxies (for example, Pomerium) that exchange OAuth tokens with GitHub on a per-request basis.
0 commit comments