GitHub MCP server

What the model can do

Search issues and pull requests, read code and commit history across the repositories the token can see; can also commit files to a branch, open a pull request, review it, change it and merge it, open and update issues, and comment — each only when you ask.

Reads

• github_search_issuesSearch GitHub issues and pull requests with GitHub search syntax (e.g. "repo:acme/api is:open label:bug", "is:pr author:priya merged:>2026-09-01").
• github_get_issueGet one issue or pull request with its comments.
• github_search_codeSearch code across repositories (e.g. "handleWebhook repo:acme/api language:ts").
• github_read_fileRead a file from a repository at an optional ref (branch, tag or sha).
• github_list_reposList repositories the token can access, most recently pushed first.
• github_list_commitsRecent commits on a repository, optionally for one path, branch or since a date.

Acts, when you ask

These change something in GitHub. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.

• github_create_issueOpens an issue in a GitHub repository.
• github_commentComments on an issue or a pull request, by number.
• github_update_issueChanges an issue — its title, its labels (added or removed, the rest left alone), its assignees, or its state: close it (state "closed"…
• github_create_pull_requestOpens a pull request from a branch that already exists.
• github_commit_filesWrites files to a branch as one commit — this is the tool that actually changes code.
• github_review_pull_requestReviews a pull request — approve it, request changes, or leave a review comment, with remarks on particular lines.
• github_merge_pull_requestMerges a pull request.
• github_update_pull_requestChanges a pull request — its title or body, the branch it targets, whether it is a draft, or closes and reopens it.

Connect it

First connect GitHub on Dashboard → Connections, then add Memtro to your client once. The GitHub tools appear alongside the tools of everything else you have connected; nothing is configured per connector.

claude mcp add --transport http memtro https://platform.memtro.com/api/mcp \
  --header "Authorization: Bearer sk-memtro-..."

{
  "mcpServers": {
    "memtro": {
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

{
  "mcp": {
    "memtro": {
      "type": "remote",
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Who may use it

The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared GitHub connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.

Ask it like this

• › Which PRs touched billing since September?
• › Summarise open issues labelled P1 in acme/api
• › Who last changed the retry policy and why?

Questions

Is this an official GitHub MCP server?

No. It is Memtro's MCP server with Memtro's GitHub connector behind it: the connector reads GitHub through its API with the credentials you connect on Dashboard → Connections, and GitHub publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.

What does it cost?

Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.

Can it change anything in GitHub?

Only when you ask, and only what it has been granted: open an issue in a repository; comment on an issue or pull request; change an issue's title, labels, assignees or state (close or reopen); commit files to a branch, creating the branch if it does not exist; open a pull request from a branch; review a pull request: approve, request changes, or comment on lines; change a pull request's title, body, target branch, draft state, or close it; merge a pull request, optionally deleting the branch. Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.

Which clients work?

Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.

Other MCP servers · Engineering and operations

• AWS CloudWatch MCP server
• Sentry MCP server
• ServiceNow MCP server
• Okta MCP server
• Twilio MCP server
• AWS CloudTrail MCP server