Skip to main content

Build with Bolt

Bolt 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 · Read the Bolt documentation

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 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.

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:

npm install @inttegro/inttegro-sdk

Otherwise use server-side HTTPS and copy the request shape from the relevant API reference. 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. After import, configure the MCP connection and runtime secret again; neither belongs in the repository.

Before publishing

Review Bolt's Server Functions and 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.