GitHub AI Agent
Run autonomous AI agents on your GitHub repos with Oido. Triage issues, review PRs and automate releases on a schedule or from Telegram.
What you can automate with GitHub + Oido
- Triage new issues every morning, label, assign, and post a summary to your Telegram channel.
- Review open pull requests and leave a first-pass comment before your team wakes up.
- Cut a release: read merged PRs since the last tag, draft release notes, open the release.
- Answer 'what changed in repo X this week?' from a channel message, no dashboard needed.
Oido connects to GitHub through the GitHub MCP server, giving your agent direct, tool-level access to issues, pull requests, commits, and releases. Because Oido runs agents on a schedule and inside channels, GitHub stops being a place you check and becomes something that works on its own.
How it works
The GitHub MCP server exposes GitHub's API as agent tools. Oido installs it as an extension, injects your token, and the agent calls those tools directly, no glue code. Pair it with Oido's built-in cronjob tool to run unattended, or with a Telegram channel to drive it from your phone.
Unlike a coding assistant that only helps you write code, an Oido GitHub agent operates your repo: it reads state, takes actions, and reports back where your team already talks.
Setup
Install the GitHub MCP server as an Oido extension:
oido extensions install @modelcontextprotocol/server-githubOr add it directly to ~/.config/oido/mcp-servers.json:
{
"servers": {
"github": {
"command": "npx",
"args": [
"-y",
"@modelcontextprotocol/server-github"
],
"env": {
"GITHUB_PERSONAL_ACCESS_TOKEN": "${GITHUB_PERSONAL_ACCESS_TOKEN}"
},
"transport": "stdio"
}
}
}GITHUB_PERSONAL_ACCESS_TOKEN, GitHub personal access token with repo scope (Settings → Developer settings → Tokens).
Confirm the exact source and env vars against the GitHub MCP server, package names occasionally change.