Skip to content
Nappai Documentation

GitHub MCP

GitHub MCP is a simple tool that lets you connect your Nappai dashboard to GitHub.
With it you can run a variety of GitHub actions—like creating issues, listing repositories, or managing pull requests—directly from your workflow, without writing any code.

How it Works

When you add the GitHub MCP component to a flow, you only need to supply a GitHub API Token (a Personal Access Token that you create in your GitHub account).
The component then talks to GitHub’s public API on your behalf.
All the heavy lifting—building the request, handling authentication, and parsing the response—is done behind the scenes.
You simply choose the GitHub tool you want to run (for example, “List Repositories” or “Create Issue”) and provide any required inputs. The component returns the result of that tool, which you can feed into other components in your workflow.

Inputs

  • GitHub API Token:
    The personal access token that gives the component permission to read or write data in your GitHub account.
    Visible in: All operations

  • Tool:
    The specific GitHub action you want to perform. The list of available tools is automatically populated based on your token’s permissions.
    Visible in: All operations

Outputs

The component outputs the raw data returned by the selected GitHub tool.
Typical outputs include:

  • A list of repositories, issues, or pull requests
  • Details of a single issue or pull request
  • Confirmation of a created or updated resource

You can use these outputs as inputs to other components, such as a data transformer, a notification sender, or a storage component.

Usage Example

  1. Add the GitHub MCP component to your flow.
  2. Enter your GitHub API Token in the “GitHub API Token” field.
  3. Select a tool from the dropdown (e.g., “List Repositories”).
  4. Run the flow.
  5. The component will return a JSON array of your repositories, which you can then pass to a “Table” component to display them in the dashboard.
  • GitHub Issue Creator – Create new issues in a repository.
  • GitHub Pull Request Manager – Open, close, or merge pull requests.
  • GitHub Repository Manager – Create or delete repositories.

Tips and Best Practices

  • Keep your token secret: Store it in Nappai’s secure variable store instead of hard‑coding it in the flow.
  • Use the least‑privilege token: Create a token that only has the permissions needed for the chosen tools.
  • Check API limits: GitHub imposes rate limits; if you run many requests, consider adding a delay or batching them.
  • Validate outputs: Use a “JSON Validator” component after GitHub MCP to ensure the data structure matches what you expect.

Security Considerations

  • Never expose your GitHub API Token in public dashboards or logs.
  • Use Nappai’s built‑in secret management to store and reference the token securely.
  • Review the permissions granted to the token regularly and revoke any that are no longer needed.