Product and Business Atlas: MCP Connector Catalog, Professions and Product Ideas

Module: Professional practice | Time: about 40 min of theory + a reference you'll keep coming back to

The gist

This isn't a lesson, it's an atlas. A reference you open when you're wondering "what can I do with Claude Code?" and "how do I turn that into my own business?"

Three parts: a connector catalog (what to plug in), a professions atlas (what's changing), and a products atlas (what to build and sell).

About income numbers. This lesson makes no promises about earnings: results depend on your niche, your market and your work. The product and price examples below are ideas and illustrations, not forecasts. To learn how to set a price and find your break-even point, see the lessons How to set a price and Break-even and a cash cushion.

🎨 Picture this: Claude Code without connectors is like a smartphone without a SIM card. Smart, but cut off. MCP (Model Context Protocol) is the set of SIM cards that connects it to the real world: databases, payment systems, CRMs (customer relationship management systems), the cloud. Every connector opens up new tasks, new products and new possibilities.

Part 1: MCP connector catalog by category

How to find more: pulsemcp.com is a large server catalog | registry.modelcontextprotocol.io is the official registry | smithery.ai is a catalog with hosting

Check before you install. This catalog reflects October 2026, but not every install command has been re-verified. Servers move and get renamed: for example, some of the reference servers from the modelcontextprotocol/servers repository (PostgreSQL, SQLite, Redis, Slack, Puppeteer, Brave Search, GitHub) have been archived and are no longer maintained. Before installing, open the server's page in the registry and check the author and the current command. The "Price" column is the price of the connector itself; the service behind it may be paid.

Installing any MCP:

# stdio (a local process)
claude mcp add <name> -- npx -y @package/name

# remote HTTP
claude mcp add --transport http <name> https://mcp.example.com

# into the project (saved to the .mcp.json file)
claude mcp add --scope project <name> -- npx -y @package/name

🗄 Databases

What to build with it: any SaaS with persistent data, analytics dashboards, CRMs, tracking systems.

☁️ Cloud and infrastructure

💳 Payments and finance

What to build: SaaS with billing, e-commerce, marketplaces, subscription services.

📊 Analytics and monitoring

🤖 AI / ML models

📧 Communication

🎨 Design and media

🔍 Search and data

⚙️ Aggregators (hundreds of apps with one command)

🎨 Picture this: Composio is like a Swiss Army knife with a hundred blades. One install, and you have access to lots of SaaS services.

Part 2: Professions atlas — what Claude Code takes over

The rule: Claude Code doesn't "replace" anyone. It takes on a noticeable share of the routine tasks in each profession. What's left is strategy, real relationships and unique experience. For more on what's changing in specific professions, see the "Professions" page.

💻 Frontend / web developer

What Claude Code does:

• React, Vue and Next.js components from a description
• Landing pages, dashboards and web apps in hours
• Figma → code (Figma MCP)
• CSS, accessibility, dark mode, responsive layouts

Connectors you need: Figma MCP + anthropic-skills:frontend-design + chrome-devtools MCP + GitHub MCP

What stays with the human: architecture that scales, negotiating requirements, accessibility testing with real users

About money: your rate depends on the market and the client. For how to price by result rather than by the hour, see the lesson How to set a price.

🎨 Designer / UI designer

What Claude Code does:

• UI components with a design system (frontend-design skill)
• Posters, social graphics (canvas-design)
• Color accessibility audits (WCAG contrast)
• Design → handoff specs → code

Connectors you need: Figma MCP + anthropic-skills:canvas-design + design:design-critique

What stays with the human: Claude Design can generate a mockup, but it won't explain why that mockup solves the business problem. Brand strategy, user research.

🎬 Motion designer / animator

What Claude Code does:

• CSS animations, WebGL
• Programmatic video with Remotion
• Animated text, subtitles
• Recreating motion graphics from a reference in a few prompts

Connectors you need: Remotion, motion/react, @lottiefiles/dotlottie-react, GSAP

// Remotion + Claude Code: programmatic video
npx create-video@latest
// Claude Code writes TSX components → renders the video
npx remotion render MyComp output.mp4

✍️ Copywriter / content writer

What Claude Code does:

• Landing page copy, email sequences, ads
• SEO articles with keyword integration
• A programmable content engine (YouTube → LinkedIn → Instagram → X)

One person with Claude Code can handle tasks that used to take a small marketing department, but quality and strategy are still on them.

Connectors you need: marketing:draft-content + searchfit-seo:create-content + Postiz MCP (many publishing platforms)

📊 Data analyst / business analyst

What Claude Code does:

• SQL queries in plain language
• Interactive dashboards (Plotly, D3)
• Streamlit apps for data exploration
• Upload a dataset → histograms and correlations automatically

Connectors you need: data:analyze + data:sql-queries + data:build-dashboard + Supabase/Neon MCP + PostHog MCP

What stays with the human: asking the data the right question, interpreting anomalies in business terms, data governance.

🚀 DevOps / SRE

What Claude Code does:

• CI/CD pipelines (GitHub Actions, GitLab CI)
• Docker configurations, docker-compose
• Infrastructure as Code (Terraform, Pulumi)
• Deploy scripts, monitoring setup

Connectors you need: GitHub MCP + AWS MCP + Cloudflare MCP + Docker MCP

# Claude Code generates a GitHub Actions workflow from a description:
# "Deploy to Cloudflare Workers on push to main"

🧪 QA engineer / tester

What Claude Code does:

• Unit tests, integration tests, e2e tests
• Playwright scripts for browser automation
• Test coverage analysis
• Regression testing when things change

Connectors you need: superpowers:test-driven-development + Playwright + chrome-devtools MCP

📱 Mobile developer (iOS/Android)

What Claude Code does:

• React Native apps
• PWAs (Progressive Web Apps) that work like native apps
• Expo setup and configuration
• Key screens and navigation flow

Connectors you need: Context7 MCP (React Native docs) + anthropic-skills:frontend-design + Supabase MCP (backend)

What stays with the human: native optimizations (specific iOS/Android SDKs), publishing to the App Store (the process itself)

🎮 Indie game developer

What Claude Code does:

• Browser games in Phaser, Three.js, vanilla JS
• Simple 2D games: platformers, arcade games, puzzles
• Game logic, collision detection, scoring

Example: simple arcade games (Space Invaders, Asteroids, Pong) in vanilla JS get recreated in just a few hours

Connectors you need: three.js + React Three Fiber + Phaser + WebGL

🛒 SEO specialist

What Claude Code does:

• Technical SEO audits
• Schema markup generation
• On-page optimization
• Internal linking strategy
• A content plan based on keyword analysis

Connectors you need: searchfit-seo:seo-audit + searchfit-seo:on-page-seo + searchfit-seo:schema-markup + searchfit-seo:keyword-clustering

📞 Customer support

What Claude Code does:

• AI chatbots that know your product
• FAQ automation
• Ticket categorization
• Creating and updating a knowledge base

Connectors you need: Telegram Bot API + Slack MCP + Supabase MCP (ticket storage) + anthropic-skills:agents-sdk (an agent is an autonomous AI worker)

Part 3: Products atlas — what to build and sell

💡 How to approach pricing

For how to work out price and cost in detail, see the lessons How to set a price and What a customer costs and what they bring in.

What a SaaS is worth when you sell it depends on revenue, growth, customer churn and the state of the product. Marketplaces like Acquire.com show public valuations, but that's no guarantee of what your product will sell for.

📦 SaaS products — ideas and stack

These are ideas for learning projects, not income forecasts: demand depends on the niche, the competition and your work.

Public examples of solo founders. Marc Lou publicly builds several small products without a team, including a Next.js boilerplate for launching a SaaS (ShipFast); his principle is to ship small products more often rather than grow one for years. Base44 is an app builder that works from a description (vibe coding), built by a single founder; in 2025 it was acquired by Wix. We don't quote numbers from stories like these: they can't be verified, and they depend on luck as much as on work.

🌐 Web apps

📊 Dashboards and analytics

Key components for dashboards:

# Tremor: chart components in TypeScript
npm install @tremor/react

# Recharts: popular, lots of examples
npm install recharts

# shadcn/ui charts: Radix + Tailwind
# already included in the shadcn/ui MCP

🤖 Automations and bots

🛒 E-commerce solutions

🎮 Browser games

🧩 Browser extensions

Getting started: Chrome Extension Manifest V3. To publish in the Chrome Web Store you need a developer registration with a small one-time fee (check the amount on the store's page).

Part 4: Monetization models

The numbers in this part are hypothetical: they show how the math works, not a promised result.

🏆 Model 1: SaaS subscription

The principle: recurring payments are the most predictable kind of revenue, but you have to earn them first: subscribers have to be found and kept.

Hypothetical calculation (an illustration, not a forecast): SEO Tool
- Free: 5 audits/month
- Pro $29/month: 50 audits + keyword research
- Agency $99/month: unlimited + white-label

If there were 100 Pro + 20 Agency customers:
MRR (monthly recurring revenue) = 100 x $29 + 20 x $99 = $4,880

How to launch: Product Hunt and tool directories for your first users. The first users usually take the most effort; after that, word of mouth helps.

🔨 Model 2: Build-to-Sell

The principle: you build a small product, get it to steady revenue and sell it on a marketplace for buying and selling businesses. This is a risky model: buyers look at revenue, growth, churn and code quality, not at how hard you worked.

Marketplaces for selling: Acquire.com, Flippa. Each has its own requirements for business size; check the marketplace's website.

💼 Model 3: Services with Claude Code

The principle: you sell the client a result, and Claude Code speeds up your work. Your price doesn't have to drop along with your time: the client pays for their problem being solved.

Example: Landing page + SEO
- The client pays for the result, not for hours
- The work takes less time with Claude Code than without it
- Set the price based on value, cost and the market (see the lesson "How to set a price")

Where to find clients: freelance marketplaces (niche: AI integrations), LinkedIn, and communities and forums in your niche. Finding clients is covered in the lessons First clients and Cold outreach with Claude.

🎓 Model 4: Info products and learning materials

The principle: you package what you know about specific connectors into materials for others.

🤝 Model 5: Agency / retainer

The principle: you take on clients for ongoing service and automate the routine.

Typical setup:
- The client pays monthly for support and development
- Part of the work is automated, but oversight and responsibility stay with you
- Set the workload per client and the price by contract and by your own costs

Services:
- AI chatbots (setup + maintenance)
- Email automation
- SEO + content generation
- Reporting and analytics

Part 5: Product launch checklist

Phase 1: Idea and validation

□ Niche: who are we selling to? (a specific ICP, ideal customer profile)
□ Problem: what are they paying money for right now?
□ Competitors: 3-5 alternatives, and what they charge
□ What sets us apart: 1 thing we do better / differently
□ Price: chosen based on value and cost (subscription or one-time payment)
□ Demand test: 5 people said "I want this" OR 1 pre-payment

Phase 2: MVP

□ Tech stack chosen (Claude Code + specific MCPs from the catalog)
□ Supabase or Neon for the database
□ Stripe MCP connected before launch (!)
□ Auth: Supabase Auth or Clerk
□ Landing page: a converting headline + bullet points + pricing + CTA
□ MVP ready: 1 core feature, not 10 niche ones
□ Domain registered with a registrar
□ Deploy: Cloudflare Workers or Vercel

Phase 3: First sales

□ Product Hunt launch day (pick a weekday)
□ Tool directories and platforms for early users
□ Reddit: r/entrepreneur, r/SaaS, niche subreddits (read each subreddit's rules)
□ IndieHackers: milestone posts
□ Twitter/X: build in public (regular updates)
□ Cold email: 50 potential customers in your niche (follow anti-spam law, such as CAN-SPAM in the US)
□ Month 1 goal: first paying users and honest feedback

Phase 4: Growth

□ Onboarding email sequence (via Resend + automation)
□ Track feature requests (in Supabase or Notion)
□ Churn analysis: why are people leaving?
□ Referral program (work out the terms from your margin)
□ Affiliates: bloggers and YouTubers in your niche
□ SEO: programmatic landing pages
□ Month 3 goal: a clear, repeatable funnel
□ Month 6 goal: decide whether to grow, maintain or shut down (see the lesson "Break-even and a cash cushion")

Quick start: 3 learning products for a weekend

These are learning projects: they teach you to assemble a product from connectors. Demand for the finished result depends on your niche and your work; income isn't guaranteed.

Product 1: Niche SEO Audit Tool

# Stack
claude mcp add shadcn -- bunx -y @jpisnice/shadcn-ui-mcp-server
claude mcp add --transport http stripe https://mcp.stripe.com
claude mcp add fetch -- npx -y @modelcontextprotocol/server-fetch

# Prompt for Claude Code:
"Build an SEO audit tool for [niche, for example: Shopify stores].
Input: the store's URL. Output: a 15-point report (meta tags, speed, 
structured data, internal links). Stripe for a monthly subscription.
UI in shadcn/ui. Deploy to Cloudflare Workers."

Product 2: AI Client Report Generator

# Stack
claude mcp add --transport http stripe https://mcp.stripe.com
claude mcp add supabase -- npx -y supabase-mcp
claude mcp add posthog -- npx -y @posthog/mcp-server

# Prompt:
"Build a platform for agencies: the client enters data (Google Ads, 
Shopify, PostHog), and the system generates a PDF report with charts.
Subscription via Stripe. Supabase for the data. Tremor for charts."

Product 3: Business Automation Bot (Telegram)

# Stack: covered in detail in the lesson "Telegram bots with the Claude API"
npm install grammy
# + Supabase MCP + Google Workspace MCP

# The idea: a bot that
# - Takes a photo of a receipt → adds it to an expense spreadsheet
# - Generates a weekly expense summary
# - Reminds you to pay bills

Lesson on Telegram bots: Telegram bots with the Claude API.

Tools and resources

MCP catalogs

• pulsemcp.com: a large MCP catalog with ratings
• smithery.ai: a catalog with managed deploy (you can run servers without installing them locally)
• registry.modelcontextprotocol.io: the official registry
• mcp.so: a community directory
• github.com/modelcontextprotocol/servers: the canonical source

Selling a product

• acquire.com: selling SaaS businesses (business size requirements are on the site)
• flippa.com: selling websites and micro-SaaS
• appsumo.com: a software marketplace and a source of early users
• producthunt.com: launch day

Monetization tools

• gumroad.com: digital products, courses
• podia.com: a platform for courses and digital products
• stripe.com: payments for SaaS

Key takeaways

One MCP = one new profession. Stripe MCP turns you into a "payment systems developer." Figma MCP turns you into a "designer → developer." fal.ai MCP turns you into an "AI media studio."

Price is value, cost and the market. Don't multiply your rate by "time saved": the client pays for a solved problem. The lessons How to set a price and Break-even and a cash cushion teach you how to work out a price.

Build-to-Sell is a risky model. Buyers look at revenue, growth and churn, not at hours spent. Numbers from other people's deals don't carry over to your product.

The main launch rule: connect Stripe MCP BEFORE launch, not after. If people can't pay on day one, you won't find out whether there's real demand.

Composio = a Swiss Army knife: hundreds of apps with one install. If you don't know which MCP you need, start with Composio.

Next step

→ Pick ONE product from Part 3. Open Claude Code. Install 2-3 MCPs from the catalog. Give yourself a deadline for the first working version: say, one weekend.

Don't plan forever. Build a small working version and test it on a real person.

The MCP ecosystem changes fast: check pulsemcp.com and the MCP registry for new connectors, and see current prices and versions of services on the What's current page.