imperal.io
  • How it works
  • Use cases
  • Technology
  • Pricing
Login
Webbee AIWebbee Codeimperal-mcpDevelopers & SDKSecurity & Vault
Add an app 路 Marketplace
imperal.ioICNLI Cloud OS

One OS for everything you run. Webbee is your agent inside it, she does the work, you stay in control.

Product
  • Webbee
  • Webbee Code
  • Imperal MCP
  • Marketplace
  • Use cases
  • Pricing
  • Open panel
Resources
  • Security
  • Technology
  • Success stories
  • Blog
Developers
  • Developers
  • Docs
  • Quick start
  • SDK reference
  • Developer portal
Company
  • About
  • Contact
  • Legal
Open protocol
  • ICNLI
  • SDK on GitHub
漏 2026 Imperal, Inc. 路 ICNLI published at icnli.org under CC BY-SA 4.0
TermsPrivacy
  1. Home
  2. /
  3. Marketplace
  4. /
  5. GitHub Connector

GitHub Connector Extension

馃洜 Developer Tools路by dmitrii路v0.10.0
Pay per use15-90 tok/action
Open in panel
0 capabilities385 actions4 installs

About this extension

Browse your GitHub repositories, view code and commit history, and manage pull requests and issues directly from chat.

What you get

Every capability exposed by GitHub Connector, metered per action and guarded by the two-step safety protocol.

  • connect_githubread

    Get the link to connect your GitHub account - opens GitHub's own authorization page. Use this when the user wants to connect/link their GitHub account.

  • disconnect_githubdestructive

    Disconnect your GitHub account - removes the stored access token. GitHub's own authorization record is not revoked automatically (revoke it from github.com/settings/applications if you also want that gone); this just makes Imperal forget about it. Requires an explicit confirm=true on a second call - the first call only previews.

  • list_repositoriesread

    List the GitHub repositories your connected account has access to (owned, collaborator, and organization repos).

  • create_repositorywrite

    Create a new GitHub repository - in your personal account, or inside an organization you belong to (pass org=).

  • get_file_contentsread

    Read a file's content, or list a directory's entries, from a GitHub repository at a given ref (branch/tag/commit). Pass path='' for the repo root.

  • list_recent_commitsread

    List recent commits on a GitHub repository, optionally filtered to those touching a specific path.

  • list_contributorsread

    List contributors to a GitHub repository, ranked by number of commits.

  • search_coderead

    Search for code inside a GitHub repository. Accepts GitHub's own code-search syntax (e.g. 'TODO language:python', 'def parse_args path:src') - the repo qualifier is added automatically from the repo param.

  • list_releasesread

    List releases (tags) published on a GitHub repository, newest first.

  • list_pull_requestsread

    List pull requests on a connected GitHub repository (open by default).

  • get_pull_requestread

    Get full details of a single pull request by number - title, body, state, branches, draft status, labels, assignees, and mergeable_state.

  • create_pull_requestwrite

    Open a new pull request in a connected GitHub repository (head branch into base branch).

  • merge_pull_requestdestructive

    Merge an open pull request in a connected GitHub repository. This is irreversible on GitHub's side, so it requires an explicit confirm=true on a second call - the first call only previews the merge.

  • review_pull_requestwrite

    Submit a formal review on a pull request - APPROVE, REQUEST_CHANGES, or a plain COMMENT. This is a real GitHub review (POST /pulls/{number}/reviews), distinct from comment_on_issue_or_pr's plain issue-style comment: it shows up as an actual review verdict with the green/red badge on the PR.

  • list_issuesread

    List issues on a connected GitHub repository (open by default). Pull requests are excluded - use list_pull_requests for those.

  • get_issueread

    Get full details of a single issue by number - title, body, state, comment count, labels, assignees.

  • create_issuewrite

    Open a new issue in a connected GitHub repository.

  • comment_on_issue_or_prwrite

    Add a comment to an existing issue or pull request (GitHub treats PR comments the same way as issue comments).

  • close_pull_request_or_issuedestructive

    Close an open pull request or issue in a connected GitHub repository (without merging). Requires an explicit confirm=true on a second call - the first call only previews the close.

  • close_issuesdestructive

    Close SEVERAL issues or pull requests at once in a connected GitHub repository - the batch version of close_pull_request_or_issue, for triage. Requires an explicit confirm=true on a second call; the first call only previews which ones would close.

  • get_workflow_runsread

    List recent GitHub Actions workflow runs for a connected repository - status, conclusion, and branch of each.

  • trigger_workflow_dispatchwrite

    Trigger an existing GitHub Actions workflow in a connected repository - the workflow must already declare a workflow_dispatch trigger (this doesn't create or modify workflows, only runs one that's already there). This is the 'deploy from chat' path: it runs whatever CI/CD the user already set up.

  • create_branchwrite

    Create a new branch in a connected GitHub repository, from an existing branch/tag/commit (defaults to the repo's default branch).

  • create_or_update_filewrite

    Create or update a single file in a connected GitHub repository - this IS a commit (one file per call).

  • delete_branchdestructive

    Delete a branch in a connected GitHub repository. Irreversible if the branch has no other pointer to it, so it requires an explicit confirm=true on a second call - the first call only previews the deletion.

  • delete_branchesdestructive

    Delete SEVERAL branches at once in a connected GitHub repository - the batch version of delete_branch, for cleaning up merged feature branches. Requires an explicit confirm=true on a second call; the first call only previews which branches would be deleted.

  • enable_repo_notificationswrite

    Turn on live GitHub notifications for one repo - get notified in Imperal (bell/telegram/email per your notification settings) when an issue/PR opens, your review is requested, a PR merges, CI fails, or someone pushes to the default branch. Registers a real webhook on that repo (requires admin access to it on GitHub's side).

  • disable_repo_notificationswrite

    Turn off live GitHub notifications for one repo and remove its webhook.

Related extensions

More extensions in Developer Tools ready to enable in one click.

  • Web ToolsWebsite monitoring, DNS lookup, SSL checker, and web diagnostics
  • SQL DatabaseConnect to MySQL/MariaDB databases, browse schema, run queries, execute DML/DDL, manage saved queries, and insert or update rows.
  • CO FlagsmithFlagsmith API v1 connector: feature flags, remote config, environments, and segment rules.
  • CO StatsigStatsig Console API connector: feature gates, dynamic configs, experiments, and audit metrics.

Ready to use GitHub Connector?

Enable GitHub Connector in your Imperal workspace in one click - 10,000 free starter credits included.

Open in panel