---
title: "Build with Bolt"
description: "Connect Inttegro MCP to Bolt and keep commerce credentials and API calls in trusted server code."
canonical: "https://studio.inttegro.com/ai-builders/bolt"
format: inttegro-machine-docs/v1
language: "Python"
sdk_version: "v12.0.0"
reader_profile: optional
reader_manifest: "https://studio.inttegro.com/machine/python/readers/index.json"
reader_identification: "Optional: declare your client only if known and your current-session capabilities; use reader_manifest for supplemental recommendations."
preamble_estimated_tokens: 660
model_token_report: "https://studio.inttegro.com/machine/token-report.json"
preamble_questions: 5
preamble_source: "general"
recommended_mcp_tools: ["design_integration","check_integration_readiness","get_integration_guide"]
estimated_tokens: 2162
token_estimate_method: "utf8_bytes_divided_by_4"
---

## Machine preamble

**Summary:** Connect Inttegro MCP to Bolt and keep commerce credentials and API calls in trusted server code. This Python representation uses the selected SDK's native names wherever Studio has a verified mapping.

### Five questions

#### Q1. When should the reader use Build with Bolt?

Use this builder guide when that AI app builder is responsible for generating or extending the application.

#### Q2. What is authoritative on this page?

Use this page for orientation; follow its canonical SDK, guide, API, or MCP links for exact contracts.

#### Q3. What page-specific constraint matters most?

Keep API keys and live commerce calls in the builder’s protected server environment, never generated browser code.

#### Q4. Can Inttegro MCP materially help with this task?

Yes, when the reader has an authenticated MCP connection and the task needs live context, guided planning, or a supported operation. The strongest matches are `design_integration`, `check_integration_readiness`, `get_integration_guide`; their exact roles and boundaries are listed below.

#### Q5. How should the reader verify the answer and continue?

Inspect the generated server boundary, confirm secrets are not client-visible, run the documented end-to-end test, and verify authoritative commerce state. Continue with [API reference](https://studio.inttegro.com/machine/python/api.md) and [Inttegro TypeScript SDK](https://studio.inttegro.com/machine/python/sdks/typescript.md) when those concerns enter scope.

### Recommended MCP assistance

Use these through an authenticated Inttegro MCP connection. This document remains the contract source.

- [`design_integration`](https://studio.inttegro.com/machine/python/inttegro-mcp/tools.md#design_integration) — read-only integration guidance. Elicits the integration goal, AI app builder, server runtime, SDK preference, and checkout approach, then returns a platform-aware build and test plan without accepting credentials.
- [`check_integration_readiness`](https://studio.inttegro.com/machine/python/inttegro-mcp/tools.md#check_integration_readiness) — read-only integration guidance. Audits platform secret storage, server-runtime compatibility, idempotency, errors, state verification, checkout returns, and messaging consent without receiving source code or credentials.
- [`get_integration_guide`](https://studio.inttegro.com/machine/python/inttegro-mcp/tools.md#get_integration_guide) — read-only integration guidance. Returns a focused implementation sequence and canonical Studio links for authentication, checkout, orders, catalog, messaging, idempotency, or testing.

## Document content

# Build with Bolt

[Bolt](https://bolt.new/) can use Inttegro MCP to understand the integration
before it writes code. The application it produces should call Inttegro from
server functions or a separate trusted backend, never directly from the
browser.

[Open Bolt](https://bolt.new/) · [Read the Bolt documentation](https://support.bolt.new/)

## Connect Inttegro MCP

1. From Bolt's chatbox, choose **+ → Connectors → Manage connectors**.
2. Select **Custom MCP server**, name it `Inttegro`, use
   `https://mcp.inttegro.com`, and keep the transport set to HTTP.
3. Choose MCP OAuth and complete the Inttegro sign-in. If OAuth is unavailable,
   use a dedicated Inttegro API key through Bolt's protected connector settings.
4. Review the available Inttegro tools, turn off tools this project does not
   need, then enable the connector for this project.

Use Bolt's current
[custom MCP instructions](https://support.bolt.new/building/using-bolt/connect-mcp)
for the exact settings screen. Never place the credential in a prompt or a file
that Bolt can commit to the repository.

## Paste this into Bolt

Use Bolt's current **Claude Agent**, turn on Plan mode, and enable the Inttegro
connector for this project before pasting the brief. Bolt keeps important
project rules in `claude.md` or Project Knowledge, so the integration boundary
does not depend on a long chat history. See Bolt's
[Agent controls](https://support.bolt.new/building/using-bolt/agents).

### Prompt

> **Copyable prompt:**
>
> **Business outcome**Build \[describe what the customer or operator should be able to do] for
> \[describe the business and its users]. Keep the existing design system,
> routes, authentication, and database unless the plan proves a change is
> necessary.**Plan with Bolt's connected context**
>
> 1. Inspect this Bolt project and its current frontend, database, server
>    functions, authentication, and Project Knowledge or `claude.md`.
> 2. Use the enabled Inttegro MCP connector. Call `design_integration` for the
>    outcome above and read only the Studio operation references it returns.
> 3. Ask me one concise round of unresolved business questions. Never ask me to
>    paste an Inttegro key into chat.
> 4. Present a plan with the user flow, server boundary, Inttegro operations,
>    state ownership, failure states, and acceptance checks. Wait for approval
>    before editing.
>
> **Build after approval**
>
> - Put every live Inttegro call in a Bolt Database Server Function. If this
>   project already has a trusted backend or Supabase Edge Functions, reuse that
>   boundary instead of creating a second backend.
> - Store `INTTEGRO_API_KEY` in the matching Secrets store and read it only in
>   the server function. It must never appear in client environment variables,
>   browser code, source, logs, or returned errors.
> - Use the official Inttegro TypeScript SDK only when the trusted runtime is
>   Node.js 24 or later. Otherwise make the exact documented HTTPS request from
>   the server function. Do not invent fields or call Inttegro from React.
> - Validate browser input, create stable idempotency keys for mutations, and
>   perform an authoritative lookup after redirects or uncertain writes.
> - Add the approved architecture and security boundary to `claude.md` or
>   Project Knowledge so future Bolt prompts preserve it.
>
> **Finish in Bolt**Run the project's checks and `check_integration_readiness`. Verify the happy
> path and one safe failure path in Preview, inspect the Server Function logs
> for secret or customer-data leakage, and fix any failure. Then report the
> files and functions changed, the one secret I must create, the evidence you
> checked, and the exact Publish step that remains.

## What Bolt should create

- a thin browser experience for the customer or operator;
- protected server handlers for Inttegro reads and mutations;
- explicit validation between the browser and those handlers;
- stable idempotency keys for operations that create or change resources; and
- an authoritative lookup after a redirect or uncertain write.

If the backend runs Node.js 24 or later, install the
[Inttegro TypeScript SDK](https://studio.inttegro.com/machine/python/sdks/typescript.md):

```bash
npm install @inttegro/inttegro-sdk
```

Otherwise use server-side HTTPS and copy the request shape from the relevant
[API reference](https://studio.inttegro.com/machine/python/api.md). Do not make the browser responsible
for adding an Inttegro bearer token.

## Bring an existing project

Bolt can work from a repository connected through its
[GitHub integration](https://support.bolt.new/integrations/git). After import,
configure the MCP connection and runtime secret again; neither belongs in the
repository.

## Before publishing

Review Bolt's [Server Functions](https://support.bolt.new/cloud/database/server-functions)
and [Secrets](https://support.bolt.new/cloud/database/secrets) screens, then test
the whole flow with disposable Inttegro data. Confirm that errors help the
customer without exposing request bodies, contact details, or the API key.