Skip to content
Nappai Documentation

GitHub MCP

GitHub MCP connects your flow to GitHub’s official MCP server. It gives you the tools that server publishes to work with repositories, issues, pull requests and more.

You pick a tool in the Tool field and can use it in two ways: as a step in the flow, filling in its data yourself, or as a tool for an agent, which decides when to use it.

When to use it

  • You want an agent to check the status of a project’s issues or pull requests.
  • You need to create GitHub issues from what a customer reports.
  • Your team wants an assistant that answers questions about its repositories.

Configuration

FieldWhat it does
API KeyYour GitHub personal access token. Both classic tokens (starting with ghp_) and fine-grained tokens (starting with github_pat_) are accepted. When you enter it, the Tool list loads.
Tool (required)The GitHub server tool you want to use. The list comes from the server itself. When you pick one, the data that tool needs appears below.

When the component is used as an agent tool, the agent can fill in that data for you. More on this in Tools.

Output

  • Data: the text returned by the chosen tool.
  • Tool: the tool ready for an agent. Connect it to the agent’s Tools input.

Example

A support team wants customers’ technical issues to end up in GitHub.

  1. Add GitHub MCP and enter in API Key a token with access to the repository.
  2. In Tool, pick the tool for creating issues.
  3. Write the repository owner and name, and let the agent fill in the title and description.
  4. Connect the Tool output to the support agent’s Tools input.
  5. When a customer describes a fault, the agent opens the issue with the details.

Good practices

  • Use a token with only the permissions the flow needs, ideally read-only if you are only going to query.
  • If you want the agent to use several GitHub tools, add one component per tool.