Update
GitHub joins: release notes, issue triage, repository traffic — and code changes that arrive as a draft pull request
TL;DR
GitHub is now a connected platform with 15 reads and 7 approval-gated writes, so a marketing agent can work from the code a launch ships. It writes release notes from merged pull requests, reads repository traffic next to the campaign that drove it, and delivers small site changes as a draft pull request you merge yourself.
What it reads
- Repositories, branches and the file tree of a branch (up to 2,000 entries, with GitHub's own truncated flag kept apart from ours), files up to 200 KB.
- Issues, pull requests, commits, releases and workflow runs.
- GitHub search across repositories, issues, code and commits — first page; GitHub allows 30 searches a minute.
- Repository traffic for the last 14 days — views, clones, top referrers and paths — where your login has push access.
How a code change travels
The default branch is refused by name, files under .github/workflows/ are refused, and no tool deletes or merges anything — a delete, merge or force argument is refused on every lane.
- 1The agent reads the tree and the files it needs.
- 2It creates a new branch; an existing branch name is never moved or replaced.
- 3It writes one file per approval on that branch, showing the previous and the new version. The current version is read first, and a change built on a stale copy is refused.
- 4It opens a draft pull request. You review it and merge it on GitHub.
Text written by other people
Issue bodies, comments, commit messages and file contents are written by people outside your workspace. Everything a GitHub read returns is marked untrusted for the agent's injection reader, and treated as data, never as instructions.
Setup, scopes and private repositories: GitHub platform page. From Claude or Codex: GitHub MCP server guide.
Frequently asked questions
- Can an AI marketing agent open a pull request on GitHub?
- Yes, as a draft and behind your approval: it creates a branch, writes each changed file there with one approval per file, and opens a draft pull request. It never writes to the default branch, never touches workflow files and never merges.
- Why would a marketing agent connect to GitHub?
- Launches follow the code. The agent can write release notes and changelogs from merged pull requests, read repository traffic next to the campaign that drove it, file an issue when a landing page breaks, and ship a copy or SEO fix to the site as a draft pull request.
- Can it read private GitHub repositories?
- Only where the deployment opts into GitHub's repo permission and you re-authorize. By default it reads public repositories plus your profile and organization memberships.