Pulling Business Context into Code with Idea Browser MCP

Greg Isenberg and Amir demonstrate how Idea Browser's new MCP integration with Claude Code pulls full project context—ICP, positioning, offers, growth strategies—directly into the terminal. This tracks a business idea's evolution over time, letting builders reference past documents for better decisions. For their example, an AI sparring partner for B2B sales reps in freight software, they connect via terminal: "connect to idea browser MCP... Pull the right context. Then use the lead magnet skill." This generates a lead magnet like "5 Objections That Kill Freight Software Deals," saving it as a file instantly.

Amir emphasizes the gap it fills: everyone builds landing pages, but few track customer acquisition or growth systematically. "The biggest problem these days... How do you actually know where to get customers? How do you actually grow it?" Idea Browser's skills, like lead magnet legends or landing page architects, build on this context. Greg notes he wishes he'd had it earlier for his own tools like HumbleLytics, praising its interview-style refinement: "It was interviewing me and asking questions... this is so impressive."

This setup creates continuity—activity streaks motivate ongoing iteration, turning isolated ideas into evolving businesses.

Visual Design Without Figma Handoffs Using Paper

Paper bridges the gap between AI code generation and polished design, connecting directly to Claude Code for bidirectional sync. Greg explains the old Figma-to-dev handoff is obsolete; now builders code directly but lose visual iteration. "Paper sits between design and code—you ideate, create variations, and pick directions visually."

They generate a landing page in Paper section-by-section: hero, ROI calculator (swapping pricing), component library. Greg refines by referencing a Claude-generated design system from screenshots of liked sites: "Extrapolate the key design elements... reference design style guide." This ensures consistency without vibe-coded mess.

To elevate polish, Greg installs Tail Arc components via terminal (e.g., content sections), drops screenshots into Paper, and iterates layouts manually if needed—ideal for designers jumping in. "You can use Paper to help build out different variations... make some refinements yourself." Amir notes Paper preserves component decisions for reuse across projects.

Result: Production-ready pages with animations and illustrations that look handcrafted, all Claude-generated but refined visually. Greg contrasts: Figma's new MCP is bidirectional but "Paper's tooling and interface... just works a lot better."

No-Code Deployment and Real-Time A/B Testing with HumbleLytics

Deployment skips manual frontend: Claude Code wires analytics via HumbleLytics API. Greg deploys the page, then runs an A/B test on the hero headline—variant: "Every lost deal started with an objection your rep wasn't ready for." No code pushes; scripts dynamically swap content for traffic subsets, tracking conversions live in a dashboard.

Amir highlights the power: high-converting pages without devs. "Using other tools like HumbleLytics to actually create high converting landing pages and running experiments." They discuss scaling: customers pay $5K–$10K/month for managed services using this exact flow.

The Terminal as Future Interface and Massive Arbitrage

Greg and Amir predict the terminal (via Claude Code) becomes the work interface, evolving from Cursor hype. "The terminal is the interface of work." Agents will outvisit humans on sites—Gartner predicts 20% commerce by agents by 2030—multiplied by users running fleets.

The stack's arbitrage echoes early Facebook ads (5¢ clicks): "99.999% of people have no clue this stack exists. If you have good ideas, can A/B test them, create polished websites... access to billions... the arbitrage is massive." Greg ties to broader shifts: agents get wallets, emails; markdown sites for agent access.

"Do I ever let you down?" Greg quips, committing full transparency—no holding back sauce.

"Raw. We're going to go through everything, all the sauce," Amir promises on takeaways.

"I wish I had Idea Browser sooner... to understand what is the right growth strategy," Greg admits, validating real-world use.

Key Takeaways

  • Connect Idea Browser MCP to Claude Code terminal to pull evolving project context (ICP, growth strategies) and apply skills like lead magnet generation.
  • Use Paper for visual iteration: generate pages from code, refine layouts/components with screenshots and Tail Arc installs, sync back bidirectionally.
  • Deploy via Claude Code, then A/B test headlines/CTAs with HumbleLytics API—no deploys, real-time dashboards.
  • Build design systems in Claude from reference images for consistent, polished (non-vibe) UIs.
  • Reference external blocks (Tail Arc) via terminal/Paper to accelerate pro-level components.
  • Track business progression with activity streaks to bridge idea-to-growth gaps.
  • Exploit arbitrage: polished, testable landing pages give edge over 99.999% unaware of this stack.
  • Terminal + MCPs = future work interface; prep for agent-heavy web (markdown, wallets).
  • For sales tools, niche lead magnets (e.g., "5 Objections...") drive signups.
  • Reuse preserved components across projects for speed.