Skip to main content

Build with Replit

Replit can keep the agent, application server, and deployment in one workspace. Connect Inttegro MCP for planning, then let server code perform the live API calls with a credential stored in Replit Secrets.

Open Replit · Read the Replit documentation

Connect Inttegro MCP

  1. Open Integrations in your Replit workspace and add a custom MCP server.
  2. Enter https://mcp.inttegro.com as the server URL.
  3. Complete OAuth if Replit offers it for the connection. Otherwise, add a dedicated Inttegro API key through Replit's protected connection settings as an Authorization header with the value Bearer YOUR_KEY.
  4. Connect the server and confirm that Inttegro tools appear.

Do not paste the key into Replit Agent chat, source code, .replit, or a committed configuration file. Follow Replit's official custom MCP setup for the current connection controls.

Paste this into Replit Agent

Turn on Plan mode before you paste the brief. It tells Agent to inspect the workspace and propose the integration before changing files. After you approve the plan, Agent can build against the same context. Replit's Agent workflow keeps the plan, implementation, review, and test loop in the project.

Prompt

Business outcome

Build [describe what the customer or operator should be able to do] for [describe the business and its users]. Preserve the app's current visual language and existing architecture.

Plan in Replit before editing

  1. Inspect this workspace, its runtime, routes, data model, authentication, and replit.md.
  2. Use the connected Inttegro MCP. Call design_integration with the business outcome above, then inspect only the operation references its plan returns.
  3. Ask me one concise round of questions for decisions that cannot be learned from the project or MCP. Do not ask me for an API key in chat.
  4. Show me the smallest end-to-end plan: the customer journey, Replit server routes, Inttegro operations, data we own locally, failure states, and a definition of done. Wait for my approval before changing files.

Build after approval

  • Keep INTTEGRO_API_KEY in Replit Secrets. Read it only in server code; never expose it through client environment variables, browser bundles, source, logs, or error messages.
  • If this workspace runs Node.js 24 or later, use the official Inttegro TypeScript SDK and its native request objects. Otherwise call the documented Inttegro operation from the Replit server by HTTPS. Do not downgrade the runtime or invent an API shape.
  • Reuse the app's backend. Add Replit Database only if the app genuinely needs local state such as user-to-Inttegro ID mapping; do not duplicate Inttegro resources as a second source of truth.
  • Validate every browser request, use stable idempotency keys for mutations, and look up the authoritative result after a redirect or uncertain write.
  • Record the approved Inttegro boundary and commands in replit.md so later Agent sessions preserve it.

Finish in Replit

Run the project's checks and check_integration_readiness. With App Testing enabled, exercise the complete happy path and one safe failure path in Preview. Fix regressions, then report the routes changed, the single secret I must add, the test evidence, and any remaining step before Publish.

What Replit should create

  • a server route or server action that owns each Inttegro request;
  • a browser interface that sends only the fields needed by that route;
  • one reusable Inttegro client with bounded timeouts and safe error handling;
  • stable idempotency keys for mutations; and
  • a lookup step after redirects or ambiguous network results.

For TypeScript, use Node.js 24 or later and install the Inttegro TypeScript SDK:

npm install @inttegro/inttegro-sdk

If the workspace cannot run a supported SDK runtime, call the Inttegro API by HTTPS from the Replit server and follow the linked operation reference exactly.

Start from existing code

If your application already lives on GitHub, use Replit's provider import, then connect Inttegro MCP in the imported workspace. Importing code does not import secrets; create INTTEGRO_API_KEY again in Replit Secrets.

Before publishing

Replit's Secrets tool stores the key as an encrypted environment variable. Turn on App Testing for a supported web runtime, inspect every route that reads the secret, and exercise the happy path and a failed payment or invalid request with disposable Inttegro data.