Connect GitHub to V7 Go

🚧

Preview

This feature is new and evolving. Details on this page may change as we
improve it.

V7 Go connects to GitHub through GitHub's remote MCP server, so the agent
can search repositories, issues, and pull requests from chats, playbooks,
and workflows.

This connector uses a Personal Access Token, not OAuth. It supports
GitHub.com only. GitHub Enterprise Server is not supported.

The short version

1. In Go, open Integrations → MCP Connectors → GitHub — or ask the
   agent in chat to use GitHub. A connect card appears.
2. Create a fine-grained or classic personal access token at
   GitHub token settings. Prefer a
   fine-grained token scoped to the repositories and permissions you
   need (contents, issues, pull requests). Classic tokens need repo and
   read:user if the organization still allows them.
3. Paste the token into the Personal Access Token field on the card.
   Never paste it into chat. If you do, revoke it and issue a new one.
4. Press Connect.

Troubleshooting

• 401 after connecting. The token is missing, expired, revoked, or was
  never saved. Press Re-enter credentials and paste a fresh token.
• Organization SAML SSO. Authorize the token for SSO on GitHub (token
  settings → Enable SSO / Authorize). Reconnecting without that step still
  401s.

For messages Go shows on the connect card, see
MCP connector errors.

FAQ

Is the connection shared? Connections follow the sharing policy on the
connector page.

What can the agent do? Whatever the token can already do on GitHub.com.
Ask "what GitHub tools do you have?" for the live list.