Source: raw/How_to_Build_a_Fully_Functional_Web_App_with_Claude_AI_No_Code.md (Softr app); raw/Claude_+WordPress-_How_to_Build_Launch_a_Website_With_Claude_AI_Full_Tutorial.md (WordPress site). Auto-caption transcripts; “softer” normalized to Softr, “CPM” to cPanel.
Creator: AI Master (YouTube @iamAImaster) URLs: https://www.youtube.com/watch?v=MZ3hEzqjJTg (Softr app) · https://www.youtube.com/watch?v=s-4Ic72DAQo (WordPress site) Published: not in the transcripts Sponsors: Softr sponsors the app video. The WordPress video is a paid partnership with hosting.com. Both demos run on the sponsor’s product, so confidence is low.
Two AI Master tutorials take a non-coder from a Claude chat to something live. In the first, Claude builds a working agency app through Softr’s MCP connector: a database, a Kanban board, an owner dashboard, logins with per-group visibility, a client portal and an approval workflow. In the second, Claude writes the copy brief and hosting.com’s AI WordPress builder turns it into a site on a real domain. The first is the more useful recipe. It fixes the usual gap in AI-built internal tools, which is no database and no user accounts.
Key Takeaways
- A page written into one file is not an app. The video’s opening Claude-built campaign board looked finished. But cards jumped back on refresh because the data lived in the file, there was no login, and each person got their own copy. The creator says this is how many internal tools get built in marketing and ops before IT rewrites them.
- Connect the builder through MCP and Claude builds inside it. In Claude, go to Customize → Connectors → Add → Add custom connector, paste Softr’s MCP URL, then sign in with OAuth. The tool list includes databases, workflows, pages and user groups, and “vibe-coded blocks.” From then on, a request for a table or page gets built in the app instead of explained.
- Name every table, field and stage in the data prompt. The creator listed the six campaign stages explicitly: “If I skip the stages, Claude invents its own and I spend 10 minutes renaming them.” Claude built clients, then campaigns linked to clients, then tasks, with sample records. The links worked in both directions.
- Claude can query the data it built. Asked which campaigns are over budget, Claude compared spent against budget and listed how far over each one was.
- Custom blocks are small React components that read and write the real tables. The Kanban board is a vibe-coded block. Dragging a card changes the stage in the data tab. Edits from chat (“compact cards, add a budget badge”) change the same block, and every version is saved with a restore option.
- Brief the dashboard like a developer, then add one detail per message. “Build a dashboard” gets “a few generic counters.” Iterating in the same chat works because Claude reads the existing app through the connector. “That’s why I never open a fresh chat when something looks off.” One apparent bug, 40 of 40 tasks overdue, was sample data with past due dates.
- Put the whole access plan in one prompt, group by group. Claude created three groups (admin, team member, client) and a client portal, and set page visibility per group. The creator then checked it by previewing as each group. As a client he also tried to open another client’s campaign by direct link, and it was blocked. Blocks follow the same visibility rules, so no separate permission system was needed.
- Workflows are editable from chat. The workflow is a trigger (stage changes to Approved) and an action (create a “prepare launch” task for the campaign owner). A later chat message added a filter step that stops the run when the budget is under 10,000. Approving a big campaign created the task and approving a small one did not.
- The published app is a second MCP endpoint. After publishing, Claude can connect as a regular user. Logged in as a client, it saw only that client’s campaign and could approve it, but had nothing to show for another client’s campaign. Logged in as a team member, it could answer “which tasks are overdue this week” from the live board.
- WordPress route: Claude for words, the host’s builder for layout. “A chat window is a bad canvas for layout and a good one for words.” Claude produced a business description, a target-audience line and a call to action. These went into the three fields of hosting.com’s AI WordPress Builder, which produced a draft site in about 40 seconds. Images were stock placeholders and the pricing section had invented numbers.
- The WordPress site stays standard. Edit drops into the normal WordPress editor, with “no proprietary builder holding the site hostage.” The creator went from empty cart to live page on a real domain in under half an hour, and would not hand it over as finished.
Try It
- Softr data prompt. Name each table, each field with its type, the links between tables, and the exact option list for any status field. Ask for sample records, then open the data tab and check the links before building pages.
- Ask a real question of the data (over budget, overdue, by stage) before building a dashboard. It shows whether the schema supports the questions the dashboard must answer.
- Write the access plan as a table in your prompt: group, pages visible, records visible, actions allowed. Then preview as every group, and as a client try a direct link to someone else’s record.
- Stage-change workflows: start with trigger plus action, test, then add filters from chat. Test both the pass and the filtered path.
- Before sharing, sign up as a new user in a private window to see what a client sees on day one.
- WordPress: draft the description, audience and call to action in Claude first, then paste them into whatever AI site builder your host offers. Replace the stock images, delete any invented pricing, and point the call to action at a real booking link.
- Day-one hosting checklist from the WordPress video: confirm SSL is active, check the A record and auto-renew on the domain, add a staging subdomain, run one backup restore, and download a monthly backup copy off the server.
Implementation
Tool/Service: Softr (no-code app builder with an MCP server) connected to Claude as a custom connector; hosting.com Pro plan with cPanel, one-click WordPress and an “AI WordPress Builder.”
Setup: Softr: Claude → Customize → Connectors → Add custom connector → paste the Softr MCP URL → OAuth sign-in. Publishing gives a live link with hosting included, and a custom domain is optional. hosting.com: plan → term → data-center region → domain (free for the first year with a 12-month plan, per the video) → Websites → Install WordPress, or the AI WordPress Builder.
Cost: Softr: the video offers 200 AI credits through its referral link; plan prices are not given. hosting.com: the creator chose the Pro plan on a 12-month term with promo code “AI Master.” He says to read the renewal price before paying, because “a 12-month price is a first-year price.” No figures are given in the transcript.
Integration notes: The Softr MCP connection works at two levels. As the builder, it creates tables, pages, groups, workflows and blocks. As a published-app user, it acts under that user’s permissions. hosting.com’s dashboard also has an AI assistant (“Orbi”) that took the creator straight to the DNS records screen.
Open Questions
- Softr pricing and MCP availability by plan. Neither is stated in the transcript.
- How Softr enforces record-level access for MCP user connections. The demo shows a blocked direct link and an empty answer about another client. The underlying rule model is not shown.
- hosting.com list, discount and renewal prices. The video shows them on screen but they are not in the transcript. The referral URL in the captions (“go.toddhosting.com/aimaster”) is garbled.
- Who should skip the WordPress route. The creator says high-traffic stores or apps with a real back end need a bigger tier or their own server. He gives no traffic threshold.
Related
- AI Website Builders Compared — Lovable, Bolt.new, v0 — the prompt-to-app builders this Softr route competes with.
- Claude Connectors — how custom connectors are added.
- Model Context Protocol — the protocol the Softr connector uses.
- Artifacts — Claude’s built-in route when you only need a clickable mockup.
- Claude as an Autonomous WordPress SEO Manager — the next step once a WordPress site exists: running it from Claude over MCP.
- Claude Code for Non-Coders — Desktop Build-to-Deploy Playbook — the code-on-disk alternative, deploying to Vercel.