Give Bolt your company's context: Introducing Connectors

Up to this point, when you were working in Bolt, you had to add context and backstory as-needed throughout the project.

You are familiar with this workflow:

• Start a new chat. 

• Describe your project. 

• List relevant tasks and reqs.

• Paste in docs for reference, SECOND THING, THIRD THING. 

• Add context, repeat. 

Now, with the introduction of Connectors, that work will flow quite differently. 

With Connectors, Bolt can directly integrate with any tool that has a remote MCP server. 

Any. Tool. 

Notion? Linear? GitHub? Yes. 

Miro, Sentry, Context7, Granola, and Jira. Also yes. What are Connectors?

Connectors are direct links between Bolt and the tools you work in. Connect Notion, and Bolt can read and edit your pages while you build. Connect Linear, and your task list becomes live context. Connect GitHub, and Bolt can read your issues and create pull requests without you describing what's in them.

The result: Bolt accesses and uses the context and data directly from the source. You no longer have to play a game of AI telephone.

Connectors are built on MCP (Model Context Protocol), an open standard that lets tools talk directly to AI. Any tool with a remote MCP server can become a Connector in Bolt without a custom integration.

The Connectors ecosystem already comprises a significant segment of key tools, and the list is only growing.

Built-in Connectors

Bolt ships with built-in Connectors for Notion, Linear, GitHub, Miro, Sentry, Context7, Granola, and Jira. Choose a Connector, authenticate (API key or sign-in flow, depending on the tool), and you're ready to go.

From there, Bolt can take specific actions on your behalf. Reading pages, pulling tasks, creating issues. What it can do depends on what the Connector supports.

Custom Connectors

Using a tool that has a remote MCP server? Add it as a custom Connector. You'll need:

• The remote server URL (published in the tool's MCP documentation)

• The transport type (HTTP for most, SSE if the docs specify it)

• Your credentials (API key or OAuth sign-in)

If you're connecting to a public server with no login required, you can skip authentication entirely.

Most tools with MCP support publish setup documentation. Searching "[tool name] MCP server" is a common workaround.

Connector Access Control

Every Connector includes a set of actions Bolt can take that are specific to that solution’s functionality: 

• Read a page. 

• Create an issue. 

• Edit a task. 

• Delete a file.

Once a Connector is established, all actions are enabled by default. Customize how you want each tool to function within Bolt by toggling each action on and off as-needed. 

Connectors live in your personal settings. Set them up once and they're available across your work. Running multiple Connectors at once can slow things down, so we recommend enabling only what you need for a given project.

You can also set a Connector to auto-enable for all new projects if you always want it available.

Get started

Open settings, then click Connectors → Manage connectors.

Start with the tool you're already in every day. If it's in the built-in list, you're a few clicks away.