Venturi

io.useventuriPublished by useventuri.iov0.2.1Updated Nov 1, 2026

Adds conversion components (pricing, checkout, paywalls, upsells) to AI-built Next.js apps.

VerifiedSTDIODesktop onlyDeveloper ToolsMedia & Design

Overview

AI-generated overview

Venturi adds conversion components — pricing, checkout, paywalls, upsells, testimonials — to AI-built Next.js apps, with design rules and themes.

What you can do
  • Browse the conversion components in your plan, grouped by purpose (urgency, social proof, pricing, checkout, recovery, lead capture, monetization, retention, referrals), with their variants.
  • Inspect one component's variants, files, npm packages, props interface and doc comment before wiring it.
  • Get rule-based suggestions for which components to use on a page or goal, in the order they should appear.
  • Read design rules on what reads as AI-generated and what to do instead before laying out a landing or pricing page.
  • Copy components, helpers, UI parts and styles into your project as editable source files, with install and import instructions.
  • List and apply themes from your Venturi portal…
When to use it
Useful when you are building or restyling a Next.js landing, pricing or checkout page with an AI assistant and want ready-made conversion blocks plus guidance on layout and design. It fits projects that already use Venturi components or a Venturi portal account.
Requirements
Runs locally over stdio via npx from the npm package venturi-dev; desktop only. No authentication, environment variables or headers are declared. A Next.js project to write components into, and a Venturi portal account for themes, are implied by the workflow.
Before you install
add_components writes source files into your project and can overwrite your edits when overwrite is true; apply_theme writes CSS overrides and copy JSON, and import_reviews writes content/reviews.json. The server instructs that only real data be used, so review CSVs and copy should be genuine. Review the generated files before committing.

Installation

In SourceWeft

  1. Open Venturi in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Tools

8

list_components

List the Venturi conversion components in the user’s plan, grouped by what they do (urgency, social proof, pricing, checkout, recovery, lead capture, in-app monetization, retention, referrals…), with each one’s variants.

Parametersbenefit

get_component

Details for one component: variants, files, npm packages, its props interface and doc comment, so you can wire it correctly. Call before using a component.

ParametersnamerequiredprojectDir

recommend_components

Suggest which Venturi components to use for a page or goal, in the order they should appear on the page, with one line on why. Rule-based from the Venturi catalog.

Parametersgoalpage

get_design_rules

The design rules to follow when building or restyling a page with Venturi blocks: what reads as AI-generated and what to do instead. Call it before laying out a landing or pricing page.

Takes no parameters.

add_components

Copy Venturi components (and the helpers, UI parts and styles they need) into the user’s project as editable source files. Returns where they went, the npm install command to run, and how to import them. Never overwrites the user’s edits unless overwrite is true.

ParameterspathnamesrequiredoverwriteprojectDir

list_themes

List the themes the user generated in their Venturi portal (colors, fonts and copy for their niche).

Takes no parameters.

apply_theme

Apply one of the user’s portal themes: writes CSS overrides (colors, fonts) next to venturi.css and the suggested copy as JSON.

ParametersidrequiredpathprojectDir

import_reviews

Turn a CSV of the user’s REAL reviews into content/reviews.json for the testimonial components. Columns: quote, name (required); role, rating (1–5), tags (;-separated), avatarUrl, date, url, platform. Never write reviews yourself.

ParametersoutfilerequiredprojectDir

Version history

1
  1. v0.2.1LatestNov 1, 2026

Score

65% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts
  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.