Cursor Bugbot: MCP Server Integration for Code Reviews
CursorCursor has added MCP (Model Context Protocol) server support to Bugbot, available to Teams and Enterprise plan users. Configured through the Bugbot dashboard, this integration allows Bugbot to connect to MCP servers and pull additional context — such as internal documentation, logs, or schemas — directly into automated pull request reviews. The feature extends Cursor's existing MCP ecosystem into the PR review workflow for the first time.
Sources & Mentions
5 external resources covering this update
Bugbot Now Supports MCP Servers for Richer Code Reviews
Cursor has extended its Bugbot code review tool with support for MCP (Model Context Protocol) servers, giving Teams and Enterprise customers the ability to bring additional context into automated pull request reviews. The feature is configurable through the Bugbot dashboard and connects to any MCP servers the team has set up.
What This Unlocks
MCP servers act as bridges between Bugbot and external data sources or tools. During a code review, Bugbot can now query configured MCP servers to pull in relevant information — such as internal documentation, service logs, database schemas, or project-specific context — that would otherwise be unavailable to an AI reviewer working solely from the code diff.
This mirrors how Cursor's broader agent and automation features already use MCP, where agents connect to external services like PagerDuty, Slack, or custom internal APIs. The addition of MCP support to Bugbot means the same protocol that powers interactive coding sessions now also powers automated PR review workflows.
Availability
MCP server integration for Bugbot is available to Teams and Enterprise plan subscribers. Configuration is handled through the Bugbot dashboard, keeping the setup separate from the per-developer MCP configuration used in the Cursor editor. This gives teams centralized control over which external context sources Bugbot can access during reviews.