Overview
The GitHub connection lets deployed agents work with GitHub: list and manage repositories, branches, commits, and file contents; create and triage issues and comments; open, review, and merge pull requests; publish and edit releases; search repositories, code, issues, users, and commits; and read users, organizations, and gists.- Base URL:
https://api.agntdata.dev/v1/connections/github - GitHub auth: OAuth 2.0 — connect your GitHub account once from the dashboard. agntdata attaches a fresh access token (and the required
Accept/User-Agentheaders) to every call, so you never pass anAuthorizationheader yourself. - MCP tools: agents call
connection_github_*tools, e.g.connection_github_list_repo_issues,connection_github_create_issue,connection_github_create_pull_request,connection_github_merge_pull_request.
Paths take
{owner}/{repo} (owner is the user or org login). Reads paginate with per_page (max 100) and page. search_* tools return { total_count, items }; most list tools return a bare array. File contents are base64-encoded — decode content on reads and base64-encode it on writes, passing the existing blob sha when updating. Issue endpoints also return pull requests (a pull_request field marks them). Delete tools are irreversible.Setup
1
Connect GitHub
In the agntdata dashboard open Integrations, pick GitHub, and click Connect. You’ll be redirected to GitHub to authorize and grant access to the repositories and organizations you want the agent to reach.
2
Pick GitHub tools
In an agent’s Tools panel, add the GitHub tools the agent needs — for example
list_repo_issues, create_issue, create_pull_request, and create_release. Destructive tools (delete_repo, delete_file, delete_release, delete_gist, delete_issue_comment) ship too; leave them off an agent you don’t want deleting things.