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: docs/remote-server.md
+3-1Lines changed: 3 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -121,13 +121,15 @@ The Remote GitHub MCP server supports the following URL path patterns:
121
121
-`/` - Default toolset (see ["default" toolset](../README.md#default-toolset))
122
122
-`/readonly` - Default toolset in read-only mode
123
123
-`/insiders` - Default toolset with insiders mode enabled
124
-
-`/insiders/readonly` - Default toolset with insiders mode in read-only mode
124
+
-`/readonly/insiders` - Default toolset in read-only mode with insiders mode enabled
125
125
-`/x/all` - All available toolsets
126
126
-`/x/all/readonly` - All available toolsets in read-only mode
127
127
-`/x/all/insiders` - All available toolsets with insiders mode enabled
128
+
-`/x/all/readonly/insiders` - All available toolsets in read-only mode with insiders mode enabled
128
129
-`/x/{toolset}` - Single specific toolset
129
130
-`/x/{toolset}/readonly` - Single specific toolset in read-only mode
130
131
-`/x/{toolset}/insiders` - Single specific toolset with insiders mode enabled
132
+
-`/x/{toolset}/readonly/insiders` - Single specific toolset in read-only mode with insiders mode enabled
131
133
132
134
Note: `{toolset}` can only be a single toolset, not a comma-separated list. To combine multiple toolsets, use the `X-MCP-Toolsets` header instead. Path modifiers like `/readonly` and `/insiders` can be combined with the `X-MCP-Insiders` or `X-MCP-Readonly` headers.
The Streamable HTTP mode enables the GitHub MCP Server to run as an HTTP service, allowing clients to connect via standard HTTP protocols. This mode is ideal for deployment scenarios where stdio transport isn't suitable, such as reverse proxy setups, containerized environments, or distributed architectures.
4
+
5
+
## Features
6
+
7
+
-**Streamable HTTP Transport** — Full HTTP server with streaming support for real-time tool responses
8
+
-**OAuth Metadata Endpoints** — Standard `.well-known/oauth-protected-resource` discovery for OAuth clients
9
+
-**Scope Challenge Support** — Automatic scope validation with proper HTTP 403 responses and `WWW-Authenticate` headers
10
+
-**Scope Filtering** — Restrict available tools based on authenticated credentials and permissions
11
+
-**Custom Base Paths** — Support for reverse proxy deployments with customizable base URLs
12
+
13
+
## Running the Server
14
+
15
+
### Basic HTTP Server
16
+
17
+
Start the server on the default port (8082):
18
+
19
+
```bash
20
+
github-mcp-server http
21
+
```
22
+
23
+
The server will be available at `http://localhost:8082`.
24
+
25
+
### With Scope Challenge
26
+
27
+
Enable scope validation to enforce GitHub permission checks:
28
+
29
+
```bash
30
+
github-mcp-server http --scope-challenge
31
+
```
32
+
33
+
When `--scope-challenge` is enabled, requests with insufficient scopes receive a `403 Forbidden` response with a `WWW-Authenticate` header indicating the required scopes.
34
+
35
+
### With OAuth Metadata Discovery
36
+
37
+
For use behind reverse proxies or with custom domains, expose OAuth metadata endpoints:
0 commit comments