This AI agent analyzes code repositories, detects potential security vulnerabilities, reviews code quality, and suggests fixes based on Sentry error
This AI agent analyzes code repositories, detects potential security vulnerabilities, reviews code quality, and suggests fixes based on Sentry error logs using Sentry and GitHub MCP servers!. That is what the code reviewer fixer agent mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.
21-Day Agent Series: Day 11 AGENT : AI Code Review & Issue Fixer
The server publishes 3 tools. What each one is for:
ReDoc — http://127.0.0.1:8000/redocPrerequisites — The Prerequisites tool exposed by this serverSteps — 3. Create a .env file in the root directory and configure it as follows:Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.
Configuration is passed through the environment: GITHUB_PERSONAL_ACCESS_TOKEN, AZURE_OPENAI_API_KEY, YOUR_GITHUB_TOKEN, SENTRY_AUTH_TOKEN, YOUR_SENTRY_TOKEN. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Code Reviewer Fixer Agent's toolset — ReDoc, Prerequisites, Steps — is a fair guide to whether it matches your workflow. It is maintained by gokborayilmaz; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| ReDoc | [http://127.0.0.1:8000/redoc](http://127.0.0.1:8000/redoc) |
| Prerequisites | The Prerequisites tool exposed by this server. |
| Steps | 3. Create a .env file in the root directory and configure it as follows: |
"mcpServers": {
"github": {
"command": "npx",
"args": ["-y", "@modelcontextprotocol/server-github"],
"env": {
"GITHUB_PERSONAL_ACCESS_TOKEN": "YOUR_GITHUB_TOKEN"
}
},
"sentry": {
"command": "python",
"args": ["-m", "mcp_server_sentry", "--auth-token", "YOUR_SENTRY_TOKEN"]
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| GITHUB_PERSONAL_ACCESS_TOKEN | Credential the server authenticates with. | Yes |
| AZURE_OPENAI_API_KEY | Credential the server authenticates with. | Yes |
| YOUR_GITHUB_TOKEN | Credential the server authenticates with. | Yes |
| SENTRY_AUTH_TOKEN | Credential the server authenticates with. | Yes |
| YOUR_SENTRY_TOKEN | Credential the server authenticates with. | Yes |
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.