Skip to main content
GitHub is a developer platform for code hosting, collaboration, and CI/CD. By connecting Github as an MCP, your agent can read repositories, manage issues and pull requests, trigger GitHub Actions, and interact with GitHub Copilot directly.

​
Adding Github as an MCP

Before you start, make sure the MCP Server is set up. See MCPs for how MCPs work.
  1. Go to Activate → MCPs, click New MCP and choose Github.
  2. Name your MCP and describe what it is used for. The agent reads the description to choose between MCPs of the same provider.
  3. Setup access. To connect using an API key:
    1. Go to your GitHub account settings and generate a personal access token.
    2. For company-wide access, create a fine-grained personal access token with the organization as the resource owner and grant it access to the necessary repositories.
    • GitHub token: A GitHub personal access token authenticating every request to GitHub’s hosted MCP server. For company-wide access, create a fine-grained token with the organization as the resource owner and grant it access to all repositories. If the organization requires approval, the token stays pending — with read access to public resources only — until an organization owner approves it. The token’s permissions control read vs. write: a read-only token makes this a read-only connection, enforced by GitHub. (Required)
  4. Select tools. Pick the tools your agents can use. See Available tools below.
  5. Click Save. On Growth and Custom plans, choose who can use it; see Access levels.

​
Example prompts

  • “Check the latest pull requests in our main repository and summarize the pending reviews.”
  • “List the failed GitHub Actions workflows from yesterday and fetch the job logs for the failures.”
  • “Create a new issue describing the login bug, then assign GitHub Copilot to investigate it.”
  • “Search our codebase for usages of the deprecated logging function and list the files that need updating.”

​
Available tools

Choose which of these tools your agents can use in Select tools.

​
Read tools

​
Write tools

​
Troubleshooting

  • Expired or revoked access: If your personal access token expires or is revoked, the MCP will show that it needs to reconnect. Go to the MCP’s page in Nekt and update the token to restore access.
  • Missing permissions: If the agent fails to perform certain actions (especially write operations like creating branches or modifying issues), ensure your token has the correct repository permissions granted. A read-only token will restrict the agent to read-only tools.
  • Pending organization approval: If you created a fine-grained token for an organization that requires approval, the token will only have read access to public resources until an administrator approves it in GitHub.

​
Need help?

Contact our support team if you have trouble connecting Github.