Skip to Content

GitHub

The GitHub enables tools and to call GitHub APIs  on behalf of a .

Want to quickly get started with GitHub in your or AI app? The pre-built Arcade GitHub MCP Server is what you want!

What’s documented here

This page describes how to use and configure GitHub auth with Arcade.

This is used by:

Configuring GitHub auth

When using your own app credentials, make sure you configure your to use a custom user verifier. Without this, your end-users will not be able to use your app or in production.

In a production environment, you will most likely want to use your own GitHub app credentials. This way, your will see your application’s name requesting permission.

Before showing how to configure your GitHub app credentials, let’s go through the steps to create a GitHub app.

Create a GitHub app

  • Follow GitHub’s guide to registering a GitHub app . Make sure to use the “GitHub App” type, which provides more granular permissions control compared to the “OAuth App” type .
  • Choose the permissions you need for your app
    • At a minimum, you must enable read-only access to the > Email addresses permission
    • To access repo data, you must enable at least the Repository > Contents permission
  • Set the redirect URL to the redirect URL generated by Arcade (see below)
  • Leave “Expire authorization tokens” checked
  • Leave “Request authorization (OAuth) during installation” unchecked
  • Leave “Setup URL” blank and “Redirect on update” unchecked
  • Ensure Optional features > -to-server token expiration is enabled
  • Copy the client ID and generate a client secret to use below

If you need to access private repositories in an organization, you must also:

  1. Make the app public via Advanced > Make public
  2. Add the app to the organization via Install app

Next, add the GitHub app to Arcade.

Configuring your own GitHub Auth Provider in Arcade

Configure GitHub Auth Using the Arcade Dashboard GUI

Access the Arcade Dashboard

To access the Arcade Cloud dashboard, go to api.arcade.dev/dashboard . If you are self-hosting, by default the dashboard will be available at http://localhost:9099/dashboard . Adjust the host and port number to match your environment.

  • Under the OAuth section of the Arcade Dashboard left-side menu, click Providers.
  • Click Add OAuth Provider in the top right corner.
  • Select the Included Providers tab at the top.
  • In the Provider dropdown, select GitHub.

Enter the provider details

  • Choose a unique ID for your provider (e.g. “my-github-provider”).
  • Optionally enter a Description.
  • Enter the Client ID and Client Secret from your GitHub app.
  • Note the Redirect URL generated by Arcade. This must be added to your GitHub app’s Redirect URLs.

Create the provider

Hit the Create button and the provider will be ready to be used.

When you use tools that require GitHub auth using your Arcade credentials, Arcade will automatically use this GitHub OAuth provider. If you have multiple GitHub providers, see using multiple auth providers of the same type for more information.

Using GitHub auth in app code

Use the GitHub in your own and AI apps to get a token for the GitHub API. See authorizing agents with Arcade to understand how this works.

Use client.auth.start() to get a token for the GitHub API:

Python
import requests from arcadepy import Arcade client = Arcade() # Automatically finds the `ARCADE_API_KEY` env variable user_id = "{arcade_user_id}" """ In this example, we will use Arcade to authenticate with GitHub and retrieve the number of stargazers of the ArcadeAI/arcade-ai repository. There is a tool for that in the Arcade SDK, which simplifies the process for you to interact with GitHub either through our Python or JavaScript SDKs or via LLM tool calling. Below we are just showing how to use Arcade as an auth provider, if you ever need to. """ # Start the authorization process auth_response = client.auth.start( user_id=user_id, provider="github", ) if auth_response.status != "completed": print("Please complete the authorization challenge in your browser:") print(auth_response.url) # Wait for the authorization to complete auth_response = client.auth.wait_for_completion(auth_response) if not auth_response.context.token: raise ValueError("No token found in auth response") token = auth_response.context.token owner = "ArcadeAI" name = "arcade-ai" headers = { "Accept": "application/vnd.github+json", "Authorization": f"Bearer {token}", "X-GitHub-Api-Version": "2022-11-28", } url = f"https://api.github.com/repos/{owner}/{name}" response = requests.get(url, headers=headers) response.raise_for_status() print(response.json().get("stargazers_count"))

Using GitHub auth in custom tools

You can use the pre-built Arcade GitHub MCP Server to quickly build and AI apps that interact with GitHub.

If the pre-built tools in the GitHub Server don’t meet your needs, you can author your own custom tools that interact with the GitHub API.

Use the GitHub() auth class to specify that a requires authorization with GitHub. The context.authorization.token field will be automatically populated with the ’s GitHub token:

Python
from typing import Annotated import httpx from arcade_tdk import ToolContext, tool from arcade_tdk.auth import GitHub @tool(requires_auth=GitHub()) async def count_stargazers( context: ToolContext, owner: Annotated[str, "The owner of the repository"], name: Annotated[str, "The name of the repository"], ) -> Annotated[int, "The number of stargazers (stars) for the specified repository"]: """Count the number of stargazers (stars) for a GitHub repository.""" if not context.authorization or not context.authorization.token: raise ValueError("No token found in context") headers = { "Accept": "application/vnd.github+json", "Authorization": f"Bearer {context.authorization.token}", "X-GitHub-Api-Version": "2022-11-28", } url = f"https://api.github.com/repos/{owner}/{name}" async with httpx.AsyncClient() as client: response = await client.get(url, headers=headers) response.raise_for_status() return response.json().get("stargazers_count", 0)
Last updated on