AI agent for GitHub

Connect GitHub to your AI agent through the WorkAist MCP server.

/ agents/marketplace

Marketplace

Pre-built connector templates · install with one click.

Connector
GitHub
Production-grade developer tools MCP server. AGPL-3.0, self-hosted.
v1.3.8developer toolspat
  1. 1Install in one click

    Pick GitHub from the marketplace. WorkAist handles Personal Access Token and stores the credentials encrypted — no JSON keys to paste.

  2. 2Tools auto-generated

    GitHub exposes 6 MCP tools to every agent in your workspace: list_projects, get_config, run_command, list_secrets, and more. Each tool is a typed function, not a brittle script.

  3. 3Data flows to your graph

    Historical developer tools records sync to your private knowledge graph. Agents query relationships across all connected sources, not just GitHub in isolation.

  4. 4Your agents take action

    AI Copywriter picks the right tool, runs it under your access policies, and answers in plain language — with a full audit trail of every GitHub call.

In 60 seconds

GitHub is developer tools software you can connect to WorkAist in minutes. Through the open MCP standard, your AI agents open issues, track deployments and surface errors before they spread — autonomously, under explicit permissions, with no manual hand-offs. GitHub authenticates via a personal access token, and because WorkAist is self-hosted under AGPL-3.0, your data never leaves your own infrastructure.

AI agents that use GitHub

Authentication & setup

The GitHub connector authenticates via Personal Access Token.

Generate a Personal Access Token

Create a token in the service's developer settings with read+write scopes, paste it once at install time. Stored encrypted.

Frequently paired with GitHub

FAQ

Can a WorkAist AI agent really automate GitHub end-to-end?

Yes. The connector exposes read and write tools through Model Context Protocol. AI agents call them through plain-language instructions in a CLAUDE.md file — no glue code.

How does this differ from using the GitHub API directly?

The connector adds permission isolation, audit logging, cost tracking per agent, and reversible PII redaction at the LLM boundary. It also presents GitHub as part of a unified Knowledge Graph alongside your other tools.

What does it cost?

WorkAist is open-source under AGPL-3.0 and self-hosted, so the connector itself is free. You pay only for GitHub's own API costs (if any) and the LLM tokens your agent consumes.

Is my GitHub data sent to a third party?

No. WorkAist runs in your own infrastructure. Data flows from GitHub → your WorkAist instance → the LLM you choose. Sensitive fields can be tokenized before reaching the LLM.

What if GitHub changes its API?

The connector is versioned and published openly. When GitHub ships breaking changes, we bump the connector version and the marketplace UI surfaces the upgrade as a one-click apply.

Licensed under AGPL-3.0 · Self-hosted, your data stays yours.