Bolt Launches Connectors to Integrate GitHub, Notion, Linear, and More Directly Into Projects.

Bolt has launched Connectors, a new feature built on the Model Context Protocol (MCP) that allows users to integrate external tools directly into their development workflow. The update eliminates the need to manually copy and paste context from services like GitHub, Notion, Linear, Jira, and Miro into Bolt projects.

Connectors let Bolt access live data from connected services, according to the official announcement. Users can now mention a GitHub issue or reference a Linear task, and Bolt will automatically pull in the relevant specifications and context. The platform can read, write, and build with actual data rather than user-provided descriptions of that data.

The feature operates through remote MCP servers that establish secure connections between Bolt and external tools. Users control access at a granular level, toggling individual tool permissions on or off from within Bolt's interface.

For development teams juggling multiple sources of truth, this addresses a longstanding friction point. Instead of switching between tabs to gather requirements from Linear, documentation from Notion, and issue details from GitHub, developers can reference these resources directly in their Bolt prompts. The AI then has full context without manual intervention.

The initial roster of supported tools includes project management platforms (Linear, Jira), documentation systems (Notion), version control (GitHub), monitoring services (Sentry), and collaboration tools (Miro). Bolt previously introduced a specific Miro integration as part of this broader Connectors rollout.

Connectors represent a shift in how AI coding tools handle context. Early AI development platforms required users to manually provide all relevant information in prompts. This created a bottleneck where the quality of output depended heavily on how well users could articulate requirements and paste in supporting details.

By integrating directly with tools that already contain project specifications, bug reports, and documentation, Bolt can now operate with richer context by default. A developer working on a bug fix can simply reference the Sentry error or GitHub issue number, and Bolt will access the full stack trace, reproduction steps, and related code changes.

This approach also reduces context window waste. Rather than copying entire documents into prompts, Bolt can selectively pull only the relevant sections from connected tools.

Bolt emphasizes user control over data access. Each connector operates as an opt-in integration that can be disabled at any time. The permissions model lets users specify exactly which tools Bolt can read from or write to, addressing potential concerns about AI systems having broad access to sensitive project data.

The feature is available now to all Bolt users. Teams can configure connectors from the platform's settings, selecting which integrations to enable based on their existing tool stack.

For teams already using Bolt's collaboration features, Connectors builds on recent updates like team templates and enhanced deployment controls. The combination of shared templates and live data integration positions Bolt as a more comprehensive team development environment rather than just an individual prototyping tool.