GitHub integration
Git hosting, issues, and pull requests on GitHub.
All integrations · Settings → Integrations
What is GitHub?
GitHub is a platform for hosting Git repositories, reviewing code, tracking issues, and collaborating on pull requests. Teams use it for source control, CI workflows, releases, and project planning tied to code.
Assistant
The official GitHub MCP server lets the assistant query repositories, issues, pull requests, and file contents you can access with your account. Changes such as comments, merges, or file updates stay behind approval unless you choose otherwise.
In chat, ask about issues, pull requests, or file contents in repositories you can access. The assistant reads first; merges, comments, and file changes need your approval unless you change tool policies.
- Search repositories, issues, pull requests, and code
- Read and write issues, comments, files, and pull requests from workflows
- Assistant and workflow steps share one Connect — no personal access token required
- Create or change GitHub resources only with your approval by default
Workflows
Add GitHub steps from the workflow step picker when this integration is connected. Set owner and repository on each step, then chain search, get, and create/update steps with expressions from upstream outputs.
Search GitHub
Search repositories, issues, pull requests, or code
Get GitHub file
Read a file or directory from a repository
Get GitHub issue
Read issue details from a repository
List GitHub issues
List issues in a repository
List GitHub pull requests
List pull requests in a repository
Get GitHub pull request
Read pull request details from a repository
Create GitHub issue
Open a new issue in a repository
Update GitHub issue
Edit an existing issue in a repository
Add GitHub issue comment
Post a comment on an issue
Create/update GitHub file
Create or update a file on a branch
Create GitHub pull request
Open a new pull request
See also Workflows overview.
How to connect
- Open Settings → Integrations.
- On the GitHub card, choose Connect.
- Sign in with the provider when prompted and allow the access Dailify requests.
- Pick a default policy for new tools (Require approval is recommended).
- After connecting, use Manage on the card to review discovered tools and set permissions per tool.
Permissions and safety
- New MCP tools default to Require approval unless you choose Auto-run when connecting.
- After connecting, open Manage on the integration card to change permissions per discovered tool.
- The assistant only sees data your provider account can access — Dailify does not broaden OAuth scope beyond what you grant.
- OAuth access is limited to: repo, read:user (via GitHub OAuth).
Tips
- Tool policies apply per discovered MCP tool after you connect — open Manage on the integration card to review them.
- Reconnect if workflow steps report a missing tool after GitHub updates their MCP tool list.
- Your organisation may need to approve the OAuth app before Connect succeeds.