Extend Bolt

Connectors and MCP servers.

Reach company systems from Bolt. Connectors are admin only. MCP servers can be personal if your organization allows it. Both are tier 3.

Connectors (admin only).

A connector is a YAML manifest that gives everyone in your organization an = key, such as =jira. It runs in Bolt's service and calls the system as the person who typed it, with their own sign-in, so they see only what they could already see. Add them in Settings → Admin → Utilities.

TabUse it to
CatalogConnectors that are on, with what each still needs.
GalleryThe connectors that ship with Bolt. Add one, then each person signs in on first use.
CustomPaste a manifest, Preview it, Save manifest.
BundlesImport a signed org bundle of connectors and compliance packs, with history and rollback.
Manifest partWhat it does
id, chip, title, emitsIdentity: the key people type and the kind of row it returns.
auth_profile_refWhose sign-in it uses: per-user OAuth (through an MCP server or direct), a personal token, or public for open APIs.
requiresWhich MCP servers must be connected for the key to appear.
scopesSub-commands. Each has a flow: call (an MCP tool or an HTTP request), parallel, merge, transform (jq) and emit.
filters, actions, presentationSearch filters, per-row actions, and how rows look.
bareRecognise text like PROJ-123 without the key and offer the lookup.
provisioning_mode, departments, roles, groupsWho in the organization gets it.

MCP servers.

An MCP server gives agents in Bolt a set of tools. Add one under Settings → Integrations → MCPs with its address and how it signs in (none, an API key, a bearer token, OAuth, and others). Your organization decides whether people can add their own.

On the desktop app Bolt can also import servers you already set up in other AI apps. A server that starts a program on your computer is imported only after you agree to it, and a company device setting can stop such programs from starting at all.

MCP servers cannot go in a personal Boltpack.