Connect SuperNinja to GitHub

Last updated: March 10, 2026

SuperNinja allows you to interact with GitHub repositories directly from your workspace using the MCP GitHub Server connector. This feature lets you clone, commit, push, and manage repositories efficiently without leaving SuperNinja. Below are the most detailed steps to help you integrate GitHub with SuperNinja.

Connect GitHub to SuperNinja

Before using any GitHub prompts, you need to connect your account:

  1. In the SuperNinja prompt box, click the Connect dropdown menu.

  2. Click Connect next to GitHub

Screenshot 2026-02-16 at 9.30.37 PM.png
  1. Connect and authorize the SuperNinja GitHub App. 

A pop-up will appear prompting you to log in and authorize SuperNinja with your GitHub account. You’ll be asked whether you want to:

  • All repositories → Grants access to all current and future repositories (public repos are read-only).

  • Only selected repositories → Grants access to specific repositories you select (also includes read-only access for public repos).

Screenshot 2026-02-16 at 9.13.30 PM.pngScreenshot 2026-02-16 at 9.14.16 PM.pngScreenshot 2026-02-16 at 9.13.58 PM.png
  1. Then, in the SuperNinja prompt box, click the Connect dropdown menu, toggle GitHub to ON, select the repository and branches and click save.

Screenshot 2026-03-03 at 2.40.49 PM.pngScreenshot 2026-03-03 at 2.44.05 PM.pngScreenshot 2026-03-03 at 2.49.27 PM.png

Once done, you’ll be able to use GitHub.

To disconnect GitHub:

  1. In the SuperNinja prompt box, click the Connect dropdown menu.

  2. Click on the GitHub text.

  3. In the pop-up window, open the Connected dropdown menu.

  4. Select Disconnect.

Screenshot 2026-03-03 at 2.51.27 PM.pngScreenshot 2026-02-16 at 9.29.30 PM.png

Clone a Repository

Once connected, you can clone a repository into your SuperNinja workspace.

Example prompt:

Use MCP GitHub Server to clone the repository [repository name]

Screenshot 2026-02-16 at 3.44.03 PM.png


Create a Repository and Commit Files

You can also create new repositories and commit files using the MCP token.

Example prompt:

Create a GitHub repository named [repository name] and commit a [file name] file to it. Use the MCP token, and once pushed to the origin, verify that the commit succeeded.

Push Changes

After editing files in your workspace, you can push updates to the remote repository.

Example prompt:

Push all changes from my SuperNinja workspace to GitHub repository [repository name] on branch [branch name] using MCP token.

Best Practices

  • Always specify the repository name and branch in your prompt.

  • Always clearly mention that you want to use the MCP GitHub Server.

  • Mention any specific files or changes you want the AI to work with.

  • Use General Agent for file creation and modification tasks; Chat Agent is limited to conversation.

Troubleshooting

  • If the AI cannot access the repository, check your MCP GitHub Server connection and permissions.

    Go to GitHub Settings, then select Applications and check whether SuperNinja is installed and authorized.

Screenshot 2026-02-16 at 9.17.06 PM.pngScreenshot 2026-02-16 at 9.16.10 PM.png
  • Ensure your prompt explicitly mentions the repository and branch.

  • For repeated failures, provide screenshots and exact prompts used—this helps the support team investigate.

If you have any questions, please contact us at support@ninjatech.ai or submit a request through this form. We’re here to help!