Connect GitHub to Llama (Meta) to unlock the power of AI automation

GitHub MCP tools

Use GitHub tools through chat to streamline your workflows.

GitHub connector for other AI models (LLMs)

Ravenala support other LLMs to connect with GitHub.

ChatGPT

By OpenAI

Grok

By xAI

Gemini

By Google

Sonar

By Anthropic

Claude Sonnet

By Anthropic

Claude Opus

By Anthropic

Mistral

By MistralAI

DeepSeek Chat

By DeepSeek

Need inspiration? What's in your stack?

Explore use cases that combine GitHub with other apps in your stack.

Airtable

17 actions

Canva

32 actions

Gmail

24 actions

1 trigger

Google Drive

51 actions

1 trigger

HubSpot

329 actions

2 triggers

Notion

28 actions

5 triggers

Salesforce

97 actions

2 triggers

Slack

133 actions

9 triggers

View more apps

Conversational AI use cases to explore

SalesAI use cases
MarketingAI use cases
ProductAI use cases
Customer SupportAI use cases
EngineeringAI use cases
DesignAI use cases
Human ResourcesAI use cases
FinanceAI use cases
LegalAI use cases
OperationsAI use cases

Connect GitHub to Llama (Meta) to unlock the power of AI automation

GitHub MCP tools

accept-a-repository-invitationAccepts a pending repository invitation that has been issued to the authenticated user.

accept-a-repository-invitation

activity-list-repo-s-starred-by-authenticated-userDeprecated: lists repositories starred by the authenticated user, including star creation timestamps; use 'list repositories starred by the authenticated user' instead.

activity-list-repo-s-starred-by-authenticated-user

activity-list-stargazers-for-repoDeprecated: lists users who have starred a repository; use `list stargazers` instead.

activity-list-stargazers-for-repo

activity-star-repo-for-authenticated-userDeprecated: stars a repository for the authenticated user; use `star a repository for the authenticated user` instead.

activity-star-repo-for-authenticated-user

add-an-email-address-for-the-authenticated-user

add-app-access-restrictionsReplaces GitHub app access restrictions for an existing protected branch; requires a json array of app slugs in the request body, where apps must be installed and have 'contents' write permissions.

add-app-access-restrictions

add-a-repository-collaborator

add-a-repository-to-an-app-installationAdds a repository to a GitHub app installation, granting the app access; requires authenticated user to have admin rights for the repository and access to the installation.

add-a-repository-to-an-app-installation

add-a-selected-repository-to-a-user-secretGrants a specified repository access to an authenticated user's existing codespaces secret, enabling codespaces created for that repository to use the secret.

add-a-selected-repository-to-a-user-secret

add-assignees-to-an-issueAdds or removes assignees for a GitHub issue; changes are silently ignored if the authenticated user lacks push access to the repository.

add-assignees-to-an-issue

add-labels-to-an-issueAdds labels (provided in the request body) to a repository issue; labels that do not already exist are created.

add-labels-to-an-issue

add-org-runner-labelsAdds new custom labels to an existing self-hosted runner for an organization; existing labels are not removed, and duplicates are not added.

add-org-runner-labels

add-or-update-team-membership-for-a-userAdds a GitHub user to a team or updates their role (member or maintainer), inviting them to the organization if not already a member; idempotent, returning current details if no change is made.

add-or-update-team-membership-for-a-user

add-or-update-team-project-permissionsGrants or updates a team's permissions ('read', 'write', or 'admin') for a specific project, which must exist within the specified organization and be linked to it.

add-or-update-team-project-permissions

add-or-update-team-repository-permissionsSets or updates a team's permission level for a repository within an organization; the team must be a member of the organization.

add-or-update-team-repository-permissions

add-project-collaboratorAdds a specified GitHub user as a collaborator to an existing organization project with a given permission level.

add-project-collaborator

add-repo-to-org-secret-with-selected-accessAdds a repository to an existing organization-level GitHub actions secret that is configured for 'selected' repository access.

add-repo-to-org-secret-with-selected-access

add-repo-to-org-secret-with-selected-visibilityGrants an existing repository access to an existing organization-level dependabot secret; the repository must belong to the organization, and the call succeeds without change if access already exists.

add-repo-to-org-secret-with-selected-visibility

add-runner-labelsAdds and appends custom labels to a self-hosted repository runner, which must be registered and active.

add-runner-labels

add-selected-repository-to-an-organization-secretAdds a repository to an organization secret's access list when the secret's visibility is 'selected'; this operation is idempotent.

add-selected-repository-to-an-organization-secret

add-selected-repository-to-an-organization-variableGrants a repository access to an organization-level GitHub actions variable, if that variable's visibility is set to 'selected repositories'.

add-selected-repository-to-an-organization-variable

add-social-accounts-for-the-authenticated-userAdds one or more social media links (which must be valid, full urls for platforms supported by GitHub) to the authenticated user's public GitHub profile.

add-social-accounts-for-the-authenticated-user

add-status-check-contextsAdds status check contexts (provided in the request body, e.

add-status-check-contexts

add-team-access-restrictionsOverwrites the list of teams (and their child teams) granted push access to a protected branch; the list of team slugs must be provided in the http post request body.

add-team-access-restrictions

add-user-access-restrictionsSets/replaces list of users allowed to push to a protected branch; usernames (e.

add-user-access-restrictions

add-users-to-codespaces-access-for-an-organizationSets or replaces the list of organization members granted codespaces access billed to the organization; ensure the organization's billing settings allow access for selected members.

add-users-to-codespaces-access-for-an-organization

approve-a-workflow-run-for-a-fork-pull-requestApproves a workflow run from a forked repository's pull request; call this when such a run requires manual approval due to workflow configuration.

approve-a-workflow-run-for-a-fork-pull-request

assign-an-organization-role-to-a-teamAssigns an existing organization-level role (identified by `role id`) to a team (identified by `team slug`) within a GitHub organization (`org`), provided the organization, team, and role already exist.

assign-an-organization-role-to-a-team

assign-an-organization-role-to-a-userAssigns a specific organization role to a user who is a member or an outside collaborator in a GitHub organization, using a valid role id.

assign-an-organization-role-to-a-user

auth-user-docker-conflict-packages-listLists docker packages for the authenticated user that encountered conflicts during the docker migration process.

auth-user-docker-conflict-packages-list

block-a-userBlocks an existing individual GitHub user (not an organization or your own account), preventing them from interacting with your account and repositories.

block-a-user

block-a-user-from-an-organizationBlocks an existing GitHub user from an existing organization, preventing their contributions, collaboration, and forking of the organization's repositories.

block-a-user-from-an-organization

cancel-a-github-pages-deploymentCancels an existing, ongoing or queued GitHub pages deployment for a repository using its `pages deployment id`.

cancel-a-github-pages-deployment

cancel-a-workflow-runCancels a workflow run in a GitHub repository if it is in a cancellable state (e.

cancel-a-workflow-run

check-a-tokenChecks if a GitHub app or oauth access token is valid for the specified client id and retrieves its details, typically to verify its active status and grants.

check-a-token

check-if-a-gist-is-starredChecks if a gist, identified by `gist id`, is starred by the authenticated user, returning an empty response (204) if starred, or a 404 error if not starred or not found.

check-if-a-gist-is-starred

check-if-a-person-is-followed-by-the-authenticated-userChecks if the authenticated GitHub user follows a target GitHub user; an http 204 status indicates the user is followed, while an http 404 status indicates the user is not followed or the target user does not exist.

check-if-a-person-is-followed-by-the-authenticated-user

check-if-a-pull-request-has-been-mergedChecks if a specified GitHub pull request has been merged, indicated by a 204 http status (merged) or 404 (not merged/found).

check-if-a-pull-request-has-been-merged

check-if-a-repository-is-starred-by-the-authenticated-userUse to determine if the authenticated user has starred a specific GitHub repository, which is confirmed by an http 204 status (resulting in an empty dictionary in the response data); the action fails (e.

check-if-a-repository-is-starred-by-the-authenticated-user

check-if-a-user-can-be-assignedVerifies if a GitHub user can be assigned to issues in a repository; assignability is confirmed by an http 204 (no content) response, resulting in an empty 'data' field in the response.

check-if-a-user-can-be-assigned