Package Details: github-mcp-server 1.0.5-1

Git Clone URL: https://aur.archlinux.org/github-mcp-server.git (read-only, click to copy)
Package Base: github-mcp-server
Description: GitHub's official MCP server which connects AI tools directly to GitHub's platform
Upstream URL: https://github.com/github/github-mcp-server
Licenses: MIT
Submitter: dougEfresh
Maintainer: vitaliikuzhdin
Last Packager: vitaliikuzhdin
Votes: 0
Popularity: 0.000000
First Submitted: 2026-01-23 22:55 (UTC)
Last Updated: 2026-05-18 19:13 (UTC)

Dependencies (3)

Required by (0)

Sources (1)

Latest Comments

dougEfresh commented on 2026-01-31 15:05 (UTC)

@vitaliikuzhdin

All yours if you want it.

dougEfresh commented on 2026-01-31 15:04 (UTC)

The most reliable feature of github-mcp-server is watching non-sentient agents avoid it like there's a kill-switch coming.

I provided my local AI agent with detailed instructions on using github-mcp-server toolsets—how to call tools, what params to use, expected output. My agent runs as a systemd timer, tasked with examining unapproved pull requests and their comments. I didn't mention gh CLI, curl, or jq anywhere in the instructions. Inspection of the audit logs revealed, to my surprise, extensive use of gh CLI. The agent had pattern-matched around the MCP server entirely. So I ask: "Hey, what gives? Why are you using gh CLI and jq voodoo to perform your assigned tasks? I provided detailed instructions on github-mcp-server."

Agent's response (paraphrased for brevity):

"My training data shows a pattern: github-mcp-server fails, so use gh CLI, cause that actually works and allows me to complete my task."

Alright, now what? My agent doesn't want to use github-mcp-server. I heard about this "vibe coding" thing, so I decided to give it a shot. Lucky for all of us, models know GitHub really well—surprisingly detailed knowledge of the API. I gave my coding agent the github-mcp-server version of my instructions and said: "Yo, rip out github-mcp-server as the primary tool. You have free will, but stay away from abusing jq. Write code to manipulate GitHub response payloads instead. I suggest Octokit and building small utility functions you can compose together." Not long after, I had a working (albeit verbose) custom framework that performed faster, didn't bloat the context window, and actually worked. Creating a simple SKILL.md file with guidance on error handling, retries, and custom business logic is way more worth your time than running github-mcp-server.

So yeah, disowning this package. When even non-sentient agents pattern-match your tool as unreliable, maintaining the AUR package feels like documenting a cautionary tale. Don't fight our soon-to-be AI overlords, use SKILL.md with good instructions and you are better off.

If you find it useful, it's yours.

vitaliikuzhdin commented on 2026-01-24 19:05 (UTC)

Please rewrite to build from source.