> For the complete documentation index, see [llms.txt](https://docs.fastn.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fastn.ai/build/building-from-your-ai-agent/mcp-gateway/bolt.md).

# Bolt

Add fastn to Bolt as a custom MCP connector, sign in, and use your fastn tools from Bolt's chat.

In bolt.new, fastn is a custom MCP connector. Sign in once, turn fastn on for a project, then ask for the integration in Bolt's chat.

## Add fastn

{% stepper %}
{% step %}

#### Open Connectors (MCP)

In bolt.new, click **+** in the chat box, then **Connectors** → **Manage connectors**. On the **Connectors (MCP)** page, click **Custom MCP server**.

<figure><img src="https://1255842839-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F3iSr2Tx8FvvuoLPncziH%2Fuploads%2Fgit-blob-ca34c07107cdce1219cdd2b8ca530182f5af71ce%2Fmcp-bolt-custom-server.webp?alt=media" alt="Bolt&#x27;s Connectors (MCP) settings page with a Custom MCP server card next to pre-configured servers such as Notion, Linear, Miro, Context7, GitHub, Sentry, Granola, Shaders and Jira"><figcaption><p><strong>Custom MCP server</strong> is the first card.</p></figcaption></figure>
{% endstep %}

{% step %}

#### Enter fastn's URL

Enter **Name** `fastn` and **URL** `https://mcp.fastn.dev/fastn-workspace`, leave **Transport Type** on **HTTP**, set **Authentication** to **MCP OAuth** and click **Add MCP server**.

<figure><img src="https://1255842839-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F3iSr2Tx8FvvuoLPncziH%2Fuploads%2Fgit-blob-6d2c5dd8f0f7c7d34ca2648d18e6d403085a198d%2Fmcp-bolt-add-server.webp?alt=media" alt="Bolt&#x27;s New MCP server form with Name fastn, URL https://mcp.fastn.dev/fastn-workspace, Transport Type HTTP, Authentication MCP OAuth, an Automatically enable for new projects toggle, and Cancel and Add MCP server buttons"><figcaption><p>Turn on <strong>Automatically enable for new projects</strong> to skip step 4 in new projects.</p></figcaption></figure>
{% endstep %}

{% step %}

#### Choose Fastn Workspace and authorize

fastn opens in a new tab. Sign in if asked. On **Choose what Bolt can reach**, search for **Fastn Workspace**, tick it and click **Authorize Bolt**.

<figure><img src="https://1255842839-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F3iSr2Tx8FvvuoLPncziH%2Fuploads%2Fgit-blob-b8c81b7839648784c29cf1497038cca0a3599607%2Fmcp-bolt-consent.webp?alt=media" alt="fastn&#x27;s page titled Choose what Bolt can reach, with the search box set to Fastn Workspace, Fastn Workspace ticked with 212 of 212 tools, Gateway Tools ticked, 215 tools selected and an Authorize Bolt button"><figcaption><p>Tick <strong>Fastn Workspace</strong>. If you leave it unticked, Bolt gets no fastn tools.</p></figcaption></figure>

Bolt shows a different screen from other clients here: it doesn't tell fastn which URL it is connecting to, so fastn asks which apps it may reach rather than which workspace to use. Bolt then lists fastn as **Connected** with its tools.

<figure><img src="https://1255842839-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F3iSr2Tx8FvvuoLPncziH%2Fuploads%2Fgit-blob-81029a1e95055ea29743588d140114986055ca2d%2Fmcp-bolt-connected.webp?alt=media" alt="Bolt&#x27;s fastn connector page listing tools such as fastnPlatform__cancelSetupLink, fastnPlatform__cancelWorkflowPromotion and fastnPlatform__claimOnboardingCredits with their descriptions, and a View more button"><figcaption><p>Every tool is on by default. To turn some off, open the <strong>…</strong> menu and choose <strong>Edit</strong>.</p></figcaption></figure>
{% endstep %}

{% step %}

#### Turn fastn on for the project

In the chat box, click **+** → **Connectors** and switch **fastn** on.

<figure><img src="https://1255842839-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F3iSr2Tx8FvvuoLPncziH%2Fuploads%2Fgit-blob-d377e1726703ad0763721a9706066c4d046a898d%2Fmcp-bolt-enable-in-chat.webp?alt=media" alt="Bolt&#x27;s chat box menu open on Connectors, showing fastn with its toggle switched on and a Manage connectors link"><figcaption><p>Bolt turns connectors on per project.</p></figcaption></figure>
{% endstep %}
{% endstepper %}

## Use it

Ask for the outcome in one sentence. To check the connection first, ask *Using the fastn connector, who am I in fastn? Just answer, don't build anything.*

<figure><img src="https://1255842839-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F3iSr2Tx8FvvuoLPncziH%2Fuploads%2Fgit-blob-62e3a2a6fdcd28131404b72f2f98020bf0c12e47%2Fmcp-bolt-answer.webp?alt=media" alt="Bolt&#x27;s chat answering Using the fastn connector, who am I in fastn? with Used Fastn fastnPlatform whoami and a reply naming the signed-in user, role, workspace, plan and environment"><figcaption><p>Bolt shows which fastn tool it used above the answer.</p></figcaption></figure>

From here Bolt works through the same steps as every agent: see [Building from your AI agent](https://docs.fastn.ai/build/building-from-your-ai-agent.md).

## Troubleshooting

* **Bolt lists only connection, skill and feedback.** **Fastn Workspace** wasn't ticked when you authorized. Remove fastn under **Connectors (MCP)**, add it again and tick **Fastn Workspace**.
* **Bolt doesn't use fastn.** Check fastn is switched on under **+** → **Connectors** in this project, then name it in your message, for example *Using the fastn connector, …*.
* **fastn shows Checking or needs sign-in.** Open fastn under **Connectors (MCP)** and connect it again.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.fastn.ai/build/building-from-your-ai-agent/mcp-gateway/bolt.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
