●MCP — The July 28 MCP spec release candidate drops the Mcp-Session-Id header and goes stateless, so remote MCP servers no longer need sticky sessions●APPS — The same release adds MCP Apps for server-rendered UI and a Tasks extension for long-running work●MEMORY — The Python 0.116.0, TypeScript 0.110.0, and Go 1.56.0 SDKs now send agent-memory-2026-07-22 on every memory store call●SPILL — Output from agent_toolset and MCP tools past 100K characters now spills to a file in the sandbox, with the model receiving a truncated preview it can expand●BG — MCP tool calls running past two minutes move to the background automatically, keeping the session usable; tune it with CLAUDE_CODE_MCP_AUTO_BACKGROUND_MS●RESUME — Typing /resume in the agent view opens a picker of past sessions and brings your pick back as a background session●MCP — The July 28 MCP spec release candidate drops the Mcp-Session-Id header and goes stateless, so remote MCP servers no longer need sticky sessions●APPS — The same release adds MCP Apps for server-rendered UI and a Tasks extension for long-running work●MEMORY — The Python 0.116.0, TypeScript 0.110.0, and Go 1.56.0 SDKs now send agent-memory-2026-07-22 on every memory store call●SPILL — Output from agent_toolset and MCP tools past 100K characters now spills to a file in the sandbox, with the model receiving a truncated preview it can expand●BG — MCP tool calls running past two minutes move to the background automatically, keeping the session usable; tune it with CLAUDE_CODE_MCP_AUTO_BACKGROUND_MS●RESUME — Typing /resume in the agent view opens a picker of past sessions and brings your pick back as a background session
Claude API × MCP: Building a Paid Consulting SaaS That Runs Without You
Build a sustainable consulting SaaS solo. Learn the complete architecture, implementation, and operations behind a ¥30,000/month revenue system using Claude API, MCP, Stripe, and CloudFlare KV. Includes real code, cost breakdowns, and hard-won lessons from scaling to enterprise.
The gap between ¥50,000 side income and ¥300,000 monthly business isn't just more of the same. It requires a fundamentally different architecture.
In the previous article, we covered 5 monetization paths. Of these, only one scales beyond a single person's effort: MCP-based tools evolved into a SaaS platform. But even that has limits unless you introduce automation at scale.
The breakthrough comes from combining Claude API with MCP into a specialized consulting SaaS. One person. Multiple paying clients. 24/7 operations. This article walks through the full build, using real code and real numbers from a system that scaled to ¥300,000 monthly revenue solo.
Why "Niche Consulting SaaS" Works for Solo Builders
Traditional SaaS advice assumes large teams and serious infrastructure. None of that is true here. Three forces make solo SaaS viable at this scale.
1. Claude API Replaces Time-Based Billing
Consulting traditionally = "expert time sold by the hour." The ceiling is hours_available × hourly_rate. Impossible to exceed without hiring.
Claude API breaks that:
Automate responses to 80% of repetitive domain questions
Use MCP to reference client-specific data in real-time
Deliver 24/7 availability without on-call burden
One person now handles 50+ simultaneous clients because Claude handles 99% of the thinking.
2. MCP Enables Safe Data Integration at Minimal Cost
Connecting to a client's internal database (Salesforce, HubSpot, proprietary CRM) traditionally required custom API work. Cost: ¥100,000+. Time: weeks.
MCP changes everything:
Standard JSON interface for all integrations
Built-in auth and sandboxing
Plug-and-play setup in hours
A solo builder can now safely access enterprise data. That's the gateway to premium pricing.
You no longer manage servers, payments, or scaling. Stripe handles billing at any size. CloudFlare KV handles global data with zero ops. The result: one person can reliably serve thousands of customers.
Combine these three, and a solo builder isn't a cute side project—they're running a real business.
System Architecture: Claude API / MCP / Next.js / Stripe / CloudFlare KV
The system incentivizes client usage. The more they use Claude through your MCP, the more they pay, the more you profit.
✦
Thank you for reading this far.
Continue Reading
What follows includes implementation code, benchmarks, and practical content we hope you'll find useful. This site runs without ads — server and development costs are supported entirely by members like you. If it's been helpful, we'd be truly grateful for your support.
WHAT YOU'LL LEARN
✦Claude API + MCP architecture for niche consulting services that scale with AI, not headcount
✦Hybrid billing model (subscription + usage-based) implementation with Stripe and real profit margins
✦Churn reduction through onboarding design, automated diagnostics, and real-world failure modes solved
Secure payment via Stripe · Cancel anytime
✦
Unlock This Article
Get full access to the rest of this article. Buy once, read anytime. This site is ad-free — your support goes directly toward keeping it running.
At this point, you're running a real business. Hiring becomes inevitable and valuable.
Next Phase: From Niche to Platform
At ¥300,000/month, you reach an inflection point. Two paths:
Path A: Deepen (Expert Mode)
Add advanced features (predictive analytics, voice analysis)
Enterprise tier (¥100,000/month)
Target: ¥500,000~¥1M monthly
Path B: Expand (Platform Mode)
Same architecture, different verticals (HR, customer support, product)
3~4 specialized MCPs
Target: ¥300,000 ~ ¥1M/month per vertical
Most succeed with hybrid: Core offering + 1~2 adjacent services.
Final Words
Going from ¥50,000 to ¥300,000 isn't more volume. It's a different business altogether.
Volume: selling time (bounded)
SaaS: selling leverage (unbounded)
The gap is architectural. Get the architecture right—domain focus, scalable tech, churn reduction—and growth becomes almost inevitable.
The hardest part isn't building. It's believing it's possible for one person. It is.
Share
Thank You for Reading
Claude Lab is ad-free, supported entirely by members like you. We publish practical guides daily with implementation code, benchmarks, and production-ready patterns. If you've found it useful, we'd love to have you on board.