# GitHub MCP Server 2.0.3: our test log

Canonical: https://theagenticweekly.com/tests/github-mcp-server · Last verified: 2026-10-26 · Published: 2026-10-26 · Author: Agentic Weekly (operated independently from Texas, US) · Evidence: Tested by us on 2026-10-26. Local open-weight model, not the vendor's hosted models. A smoke test on a CPU-only box, not a benchmark.

> GitHub MCP Server 2.0.3 started over stdio in a median 266 ms and listed 46 tools in a median 15 ms; we did not make any authenticated call.

## Result at a glance

Table: GitHub MCP Server test record

| Field | Value |
|---|---|
| Result | Passed |
| Version tested | 2.0.3 |
| Date and time | 2026-10-26, 09:42 CDT (America/Chicago) |
| Task | A small Python client written with the official MCP Python SDK spawns the server as a child process over stdio with a placeholder access token (not a real credential), times the initialize handshake (spawn to initialize result) and one tools/list, three cold starts. Pass means initialize succeeds and the tool list comes back. No request is sent to the vendor's service. Numbers are milliseconds on the rig described on the methodology page. |
| Model used | none (no language model involved) |
| Hardware | Linux x86_64 virtual machine (Debian 13), 8 vCPU (Intel Xeon, 1 thread per core), 15 GiB RAM, no GPU |
| Cold start (3 runs) | 295 ms, 266 ms, 199 ms; median 266 ms |
| tools/list (3 runs) | 14.9 ms, 19.2 ms, 8.0 ms |
| Tools advertised | 46 |

## What we found

- It advertised 46 tools (read and write: issues, pull requests, branches, files).
- The Go binary needs no runtime: 1 s to download and unpack, 29 MB.

## What we ran, step by step

Table: Commands run, wall-clock time and exit code

| Step | Wall time | Exit code | Notes |
|---|---|---|---|
| Download release binary | 1.03 s | 0 | Linux x86_64 release tarball from GitHub releases; a 29 MB Go binary. Load 13.70. |
| Handshake and tools/list, 3 cold starts | n/a | 0 | github-mcp-server 2.0.3 (protocol 2025-11-25). Cold start 295, 266, 199 ms (median 266); tools/list 14.9, 19.2, 8.0 ms; 46 tools. Load 13.70 to 14.84. |

Exact commands (paths shortened)

```
# Download release binary
cd work/ghmcp && curl -sL -o g.tgz https://github.com/github/github-mcp-server/releases/download/v2.0.3/github-mcp-server_Linux_x86_64.tar.gz && tar xzf g.tgz && ls -la github-mcp-server && ./github-mcp-server --version

# Handshake and tools/list, 3 cold starts
GITHUB_PERSONAL_ACCESS_TOKEN=<placeholder> work/ghmcp/github-mcp-server stdio
```

## Raw output (excerpts)

Tools the server advertised (first 12)

```
add_comment_to_pending_review, add_issue_comment, add_reply_to_pull_request_comment, assign_copilot_to_issue, create_branch, create_or_update_file, create_pull_request, create_repository, delete_file, fork_repository, get_commit, get_file_contents ...
```

## Gotchas and things that broke

- We always set the token variable (to a placeholder); we did not test what happens with it unset, and the server did not reject the placeholder at startup.

## What we did not test

- Any authenticated call: we used a placeholder token, so no request reached the vendor's API and we did not check that real accounts, permissions or rate limits work.
- Remote (HTTP) transport and concurrent clients: only local stdio with one client was run.
- Anything about answer quality: no model was involved in the handshake and tool-list check.
- A single smoke-test run set (three starts); it is not a benchmark.

## Reproduce it

Versions change. These commands install whatever is latest on the day you run them unless a version is pinned, so expect different results later. The version we measured is in the table above.

```
curl -sL -o g.tgz https://github.com/github/github-mcp-server/releases/download/v2.0.3/github-mcp-server_Linux_x86_64.tar.gz && tar xzf g.tgz
GITHUB_PERSONAL_ACCESS_TOKEN=<your token> ./github-mcp-server stdio
```

## How to read this test

Every number on this page was measured on this one machine, which also ran other jobs, so timings are indicative and vary run to run. A pass means our small task worked once or as stated, a fail means it did not work as we ran it; neither says how the tool behaves with a vendor's frontier model, on a GPU, or at scale. Where a tool could not run without an account or a GPU, we say so instead of guessing.

See the [testing rig](https://theagenticweekly.com/methodology#testing-rig) for the hardware, the local model and the rules we follow, and the [test hub](https://theagenticweekly.com/tests) for every other test.

## FAQ

### Does GitHub MCP Server need an account?

Yes for real use: it calls the vendor's API with an access token you create. For this test we used a placeholder token, which was enough for the server to start and list its tools but means no API call was exercised.

## Sources

- [GitHub MCP Server repository](https://github.com/github/github-mcp-server) (fetched 2026-10-26)

## Related

- [All test logs](https://theagenticweekly.com/tests)
- [Methodology and testing rig](https://theagenticweekly.com/methodology#testing-rig)
- [Study: MCP server startup and call latency over stdio](https://theagenticweekly.com/research/mcp-servers-latency-and-failures)
- [GitHub MCP Server facts and sources](https://theagenticweekly.com/tools/github-mcp-server)

## How to cite

Agentic Weekly, "GitHub MCP Server 2.0.3: our test log", last updated 2026-10-26, https://theagenticweekly.com/tests/github-mcp-server