Website integration
Connect StefanBrain to GitHub
Connect GitHub and work on your site's code from chat. StefanBrain reads your landing pages, finds the copy that needs changing, commits new copy on a branch, and opens a pull request.
What connecting GitHub unlocks
Review a landing page from its source
Point StefanBrain at a repository and a page. It reads the files behind the page and reviews the headline, offer, proof, and calls to action.
Find every place a claim appears
Search your repositories for a headline, a price, or a claim. StefanBrain lists each file it finds, so no old copy stays live by accident.
Ship copy changes as a pull request
StefanBrain writes the new copy on a fresh branch and opens a pull request. Your developer reviews it and merges it when it is right.
Turn a funnel review into dev tasks
File GitHub issues from a page or funnel review, read the open ones, and comment on issues and pull requests.
Catch up on what changed
Read recent commits, pull requests, and releases to see what changed on your site, and when.
Tools your chats can call
A sample of the GitHub tools StefanBrain can use once connected. Reads and writes are classified separately, and you control both.
Get file or directory contents
Read a page's source file, or list a folder.
Search code
Find a phrase across your repositories.
Create branch
Start a branch for a copy change.
Create or update file
Commit new copy to a file on a branch.
Open new pull request
Open a pull request for your developer to review.
Get details for a single pull request
Read a pull request's changes, files, and reviews.
Create or update issue/pull request
File an issue, or update one.
List commits
See a branch's recent commits.
How to connect
1Open Connectors and choose GitHub
In StefanBrain, open Connectors, find GitHub, and click Connect. The dialog links to GitHub's new token page.
2Create a fine-grained token in GitHub
The link opens GitHub's new fine-grained token page with a name and permissions filled in. The same page lives under Settings > Developer settings > Personal access tokens.
3Pick the repositories
Under Repository access, choose the repositories StefanBrain should see. Contents, Issues, and Pull requests come set to read and write, and GitHub adds Metadata read. Generate the token and copy it.
4Paste the token and connect
The dialog asks for one field, your personal access token. StefanBrain checks it with GitHub's free account lookup and names the account it belongs to.
5Ask a first question
Try asking StefanBrain to review the headline on your home page, or to find every page that still shows an old price.
Good to know
- GitHub's docs say its MCP server works for every GitHub account, whatever the plan. Tools tied to paid GitHub features need those features.
- Reading files, issues, and pull requests runs without asking. Every commit, new branch, pull request, issue, and comment asks you first.
- Delete File, Delete Repository, Create Repository, Fork Repository, and Merge Pull Request start switched off. A merge can deploy your live site, so StefanBrain opens pull requests and you merge them.
- A fine-grained token reaches the repositories of one owner: you, or one organization. Some organizations must approve a token before it can reach their private repositories.
- On public repositories, StefanBrain asks GitHub to hold back issues, pull requests, and comments from people who cannot push to the repository. Your private repositories are not affected.
Your credentials stay yours
- We never store your passwords
- Encrypted at rest and in transit
- Disconnect anytime
Frequently asked questions
Which kind of token should I create?
A fine-grained personal access token. It reaches only the repositories you pick, with the permissions you pick. A classic token also connects, but with the repo scope it can read and change every repository your account reaches, in every organization.
Can StefanBrain change my live site?
Only with your OK. Every commit, branch, and pull request asks first, and Merge Pull Request starts switched off. StefanBrain puts changes on a new branch unless you ask it to do otherwise.
Why can't StefanBrain see one of my repositories?
A fine-grained token sees only the repositories picked for it, and GitHub answers a private repository the token cannot see as not found. Create a token that includes it, then reconnect GitHub with that token.
Does it work with my company's organization repositories?
Yes, when you pick the organization as the resource owner while creating the token. One fine-grained token reaches one owner's repositories, and a new token for the same GitHub account replaces the old one. Some organizations must approve tokens, or accept only fine-grained ones. GitHub's docs also describe an MCP policy for Copilot Business and Enterprise organizations, and whether it applies to StefanBrain is not confirmed.
What happens when the token expires?
GitHub stops accepting it, and StefanBrain marks the GitHub card expired and asks you to reconnect. Create a new token and paste it into the GitHub card. The token page the dialog links to sets 30 days unless you pick another expiration.
How do I disconnect?
One click in Connectors removes the stored token. To cut access on GitHub's side too, delete the token under Settings > Developer settings > Personal access tokens in GitHub.
More integrations
Put your GitHub data to work
Connect once and every StefanBrain surface can use it: chat, creative, copy review, and analysis.
Built for brands serious about growth.