I'm trying to understand which layer this as acting at: is this a git MCP server that uses the git tooling, or a GitHub MCP server that acts via the GitHub HTTP API?
I've noticed that several forks of modelcontextprotocol/server-github work as a kind of "look at information on github" kind of a service, while what I'm looking for is more of a direct "let's actually git fetch the data from the remote github server" and maybe even create a git worktree with it. At a high level, what I want to do is pull down a Git PR's branch and include some or all of the files in the project in an LLM's context--the project after the PR's diffs have been applied. That way, the LLM has more information about the whole context, as opposed to just the diff itself which narrowly shows changes made only.
Would this project be able to fetch a PR, make a temporary local branch for it, and create a git worktree (local dir) of the branch?
I'm trying to understand which layer this as acting at: is this a git MCP server that uses the git tooling, or a GitHub MCP server that acts via the GitHub HTTP API?
I've noticed that several forks of modelcontextprotocol/server-github work as a kind of "look at information on github" kind of a service, while what I'm looking for is more of a direct "let's actually git fetch the data from the remote github server" and maybe even create a git worktree with it. At a high level, what I want to do is pull down a Git PR's branch and include some or all of the files in the project in an LLM's context--the project after the PR's diffs have been applied. That way, the LLM has more information about the whole context, as opposed to just the diff itself which narrowly shows changes made only.
Would this project be able to fetch a PR, make a temporary local branch for it, and create a
git worktree(local dir) of the branch?