GitHub MCP Server

GitHub's MCP server enables AI agents to interact directly with GitHub's REST and GraphQL APIs to manage software development lifecycles. It allows agents to search repositories, inspect commit histories, read and submit pull requests, create and update issue threads, manage Git branches, and review code diffs across enterprise organizations.

Start for free

GitHub MCP Server

Benefits with Ory + GitHub MCP Server

GitHub's official MCP server exposes tools across repositories, pull requests, issues, Actions, and security alerts through a single connection, and any of your agents holding that connection can call any of them. That's true whether the agent works for a staff engineer or a contractor in their first week. Ory Agent Security checks each GitHub tool call against the user and agent behind it, so a code review agent can read pull requests while changes to your repositories stay with the agents you approve.

View on GitHub

Use Cases

— 01 use case

Agent IAM

Reviewers at Read, coding agents at Write to push and open pull requests, a release agent at Admin to merge, and Block for agents with no GitHub work.

Explore Agent IAM

Core Functionality

— 04 capabilities

Read, write, admin, or no access
Ory Agent Security classifies every tool on the GitHub MCP server as read, write, or admin, so you can give each user, team, or agent type only the level it needs: read for code review agents, write for coding agents that open pull requests for their user, admin for a release agent, and no access for agents with no reason to touch your code, such as a support agent.
Enforced before execution
Ory Agent Security checks each tool call against the user, the agent acting for them, and any sub-agent inside the agent harness, so a denied push or merge stops before it reaches GitHub, with nothing to roll back and no gateway to deploy.
Observe, then enforce
Observe mode shows which agents open, comment on, or merge pull requests and on whose behalf without blocking anything, so you can apply Ory's pre-built policy for the GitHub MCP server and enforce it on your own schedule.
Complete audit trail
Every allow and deny decision on the GitHub MCP server streams to your SIEM through OpenTelemetry with the user, agent, and action attached, so you can show which agent merged a pull request and which user it acted for.