phimage
← Writing

MCP, in practice: GitHub in VS Code — checked in for the team

#ai#mcp#github#4d

A while back I asked whether anyone had actually tried MCP. Update: I have, and it stuck. The most useful day-to-day version so far is the GitHub MCP server in VS Code — so the agent can work directly with our issues, projects, pull requests, and test cases instead of me copy-pasting context into a chat.

The whole setup is one file

Drop a .vscode/mcp.json in your project:

{
  "servers": {
    "github": {
      "type": "http",
      "url": "https://api.githubcopilot.com/mcp/"
    }
  }
}

That’s it. You point VS Code at GitHub’s remote MCP server, authenticate once with OAuth (VS Code 1.101+), toggle Agent mode, and the tools show up. No Docker, no personal access token to babysit, nothing to install.

Committed to 4d/4d, so the team gets it for free

The nice part: I pushed that file into our 4d/4d repo (.vscode/mcp.json). Since our features, requirements, and test cases all live there, checking out the repo now also wires up the MCP server. Anyone on the team can open it, authenticate, and ask the agent to triage an issue, summarize a project’s progress, or pull context on a requirement — against our real data, no per-person setup.

What it can actually do

The default toolsets cover most of what you’d want, and you can trim or extend them with an X-MCP-Toolsets header (or flip the whole thing read-only for safety):

  • Repos — search code and read files without a local clone.
  • Issues & pull requests — file, triage, label, review, even merge from a prompt.
  • Projects — manage items and summarize progress (added to the server in October).
  • Actions — inspect CI/CD runs, fetch logs, re-run failed jobs.
  • Code security — surface code-scanning and Dependabot alerts.

A late-October update also added server instructions — think of it as a system prompt baked into the server itself, telling the model how to use the tools in the right order (e.g. the proper sequence for reviewing a PR). In practice the agent got noticeably better at issue and PR workflows, and the team consolidated several narrow tools into fewer, more capable ones to keep the context window lean.

PS — it doesn’t have to be per-project

.vscode/mcp.json is the per-repo route, which is what I wanted here so it travels with 4d/4d. But you can also install MCP servers globally in your VS Code user profile, or let them be discovered from a Claude config — handy for servers you want everywhere, not just in one repo.

Worth reading

This is the “has anyone tried MCP?” question answered the only way that counts: a one-file config in a shared repo, and a team that can now talk to its own issues and projects in plain language. The protocol bet is starting to pay rent. 🔌

← Back to all writing