What can the assistant change on GitHub?

Issues, comments, labels, pull requests, reviews, branches, files and releases, and merging and deleting; each waits for a person’s approval by default. Creating or deleting repositories, collaborators and teams, webhooks, deploy keys, branch protection, secrets and variables, workflow files, and rerunning or cancelling Actions are left out on purpose.

Can it read the logs of a failed Actions job?

Not the full log. It reads the error lines Actions recorded for the job, which usually explain the failure.

Does it work with GitHub Enterprise Server?

No. The connector works with github.com only; a GitHub Enterprise Server at your own address is not covered.

Which AI assistants can use GitHub through Flowplane?

Claude, Claude Code, ChatGPT, Cursor, Codex, GitHub Copilot and Mistral Le Chat, and any other client that supports remote MCP servers with sign-in. They all reach GitHub through the same Flowplane address.

Free for one person, with up to three apps and five assistants. Personal Pro is €9 a month including VAT; companies start at €99 a month for ten active users. Prices are indicative; see the pricing page.

Building software

GitHub MCP server

For teams that keep their code on github.com. Through Flowplane an AI assistant can read files, branches, commits, comparisons, pull requests with their diffs and reviews, issues, releases, check results and the failures Actions recorded for a job, and search code and issues across repositories. It can open and edit issues and pull requests, comment, review, make branches, commit a file and publish a release; each of these, merging and every delete included, waits for your approval by default.

Connect GitHub →Set up your assistant

Tools: 25 read · 20 change
Sign-in: Own account or shared key
Approval, by default: Changes wait for you
MCP server: Flowplane’s tools

What it can do

What your assistant can do in GitHub

25 tools that read and 20 that change something in GitHub. Reads are allowed; a change marked “asks first” waits for the person’s approval by default, and your workspace’s rules decide the rest.

Reads25

Check the connectionSee which account it uses and whether it workswhoami
List repositoriesYours, an owner's, or found by namelist_repos
Get repoA repository's settings and countsget_repo
List branchesThe branches of a repositorylist_branches
Read a fileA file's text, cut to a sizeget_file
List a directoryFiles and folders, one level or all belowlist_dir
List commitsThe commits of a branch or pathlist_commits
Read a commitOne commit with the files it changedget_commit
Compare two refsThe commits and files one branch has over anothercompare
Read a commit's checksPassing or not: statuses and check runsget_status
List prsThe pull requests of a repositorylist_prs
Get prOne pull requestget_pr
List pr filesThe files a pull request changeslist_pr_files
Read a pull request's diffThe changes as a unified diff, cut to a sizeget_pr_diff
List a pull request's reviewsReviews, or the code comments on itlist_pr_reviews
List issuesThe issues of a repository, filteredlist_issues
Get issueOne issueget_issue
List commentsThe discussion on an issue or pull requestlist_comments
Search issuesIssues and pull requests across repositoriessearch_issues
Search codeFind code across repositoriessearch_code
List labelsA repository's labelslist_labels
List milestonesThe milestones of a repositorylist_milestones
List releasesReleases, or one by its tag with its noteslist_releases
List Actions runsWorkflow runs, or the jobs of one runlist_action_runs
Read a job's failuresThe error lines Actions recorded for a jobget_job_annotations

Changesasks first20

Create issueOpen a new issue, asked firstcreate_issue
Edit issueChange an issue or close it, asked firstedit_issue
Add commentComment on an issue or pull request, asked firstadd_comment
Edit commentChange a comment's text, asked firstedit_comment
Change labelsAdd or remove an issue's labels, asked firstupdate_labels
Create labelMake a new label, asked firstcreate_label
Create prOpen a pull request, asked firstcreate_pr
Edit prChange a pull request, asked firstedit_pr
Request reviewAsk people for a review, asked firstrequest_review
Submit reviewApprove, request changes or comment, asked firstsubmit_review
Reply review commentReply to a code comment, asked firstreply_review_comment
Make a branchMake a new branch, asked firstcreate_branch
Write a fileCommit a file's new text, asked firstcreate_or_update_file
Create releasePublish a release, asked firstcreate_release
Merge a pull requestMerge it into its branch, asked first by defaultmerge_pr
Delete a branchRemove a branch, asked first by defaultdelete_branch
Delete a fileRemove a file in a commit, asked first by defaultdelete_file
Delete a releaseRemove a release, asked first by defaultdelete_release
Delete a labelRemove a label, asked first by defaultdelete_label
Delete a commentRemove a comment, asked first by defaultdelete_comment

How it connects

Sign-in

Each person connects their own GitHub account, in one of two ways. Sign in with GitHub through Flowplane’s GitHub App: it reaches only the repositories the app is installed on and that you may see, and an organisation may need an owner to approve the app. Or paste a personal access token: a classic token with the repo scope also reaches repositories in someone else’s organisation that you were only invited to. Flowplane keeps the login sealed; the assistant never sees it.

In Flowplane: In the Flowplane console, add GitHub and choose Sign in with GitHub, or Use a token and paste your personal access token.

MCP

GitHub and MCP

GitHub runs an official MCP server of its own, hosted by GitHub. Flowplane does not pass it through: it talks to GitHub’s REST API directly, with a trimmed set of tools and approval on every change.

Try it

Things to ask

“Which pull requests are waiting for my review?”
“Why did the last Actions run on main fail?”
“Summarise what changed between release v2.3.0 and main.”
“Open an issue in our api repo for the broken login redirect, with the label bug.”
“Review pull request 482 and request changes on the missing tests.”

Your assistant

Connect your assistant to GitHub

One Flowplane address works in every assistant below, with the same rules and the same log. Step-by-step setup for each:

FAQ

Questions

What can the assistant change on GitHub?: Issues, comments, labels, pull requests, reviews, branches, files and releases, and merging and deleting; each waits for a person’s approval by default. Creating or deleting repositories, collaborators and teams, webhooks, deploy keys, branch protection, secrets and variables, workflow files, and rerunning or cancelling Actions are left out on purpose.
Can it read the logs of a failed Actions job?: Not the full log. It reads the error lines Actions recorded for the job, which usually explain the failure.
Does it work with GitHub Enterprise Server?: No. The connector works with github.com only; a GitHub Enterprise Server at your own address is not covered.
Which AI assistants can use GitHub through Flowplane?: Claude, Claude Code, ChatGPT, Cursor, Codex, GitHub Copilot and Mistral Le Chat, and any other client that supports remote MCP servers with sign-in. They all reach GitHub through the same Flowplane address.
What does it cost?: Free for one person, with up to three apps and five assistants. Personal Pro is €9 a month including VAT; companies start at €99 a month for ten active users. Prices are indicative; see the pricing page.

Flowplane is not affiliated with or endorsed by GitHub’s maker; the name and logo only identify the app. Pricing

Let your AI work with your data. Safely, from today.

Free for yourself, set up in a minute. For your team or company, we’re happy to help you get started.

Start free →Book a call