Feature specs your agent can read·New: blueprints your AI pulls over MCP

The corner cases your agent won't think of.
The checkout the client can't break.

Blueprints are feature specs with every edge enumerated — the empty cart, the declined card, the expired invite — plus the shadcn components to build them. Your agent pulls only the sections it needs over MCP, so it ships the flow you'd have found in QA, before you quote.

MIT
Your project

This is where your project lives on Monday morning.

See how projects work
acme-marketing
Landing · 68%
Screens
Hero
Features
Pricing
Testimonials
FAQ
Footer
acme-marketing / PricingIn progress

Pricing

Done when
Three tiers, the middle one highlighted
The annual toggle changes every price
The FAQ answers the top objections
Looks right in dark mode
What's in WebShots

Projects come first. Blueprints come with them.

The product

Projects

One per client: its blueprints, progress you tick off, comments, and a link the client can open. Add your people one by one or as a team.

Open projects
The starting point

Blueprints

Feature specs for whole app types — every screen, every corner case enumerated, every component named. Your agent consumes just the sections it needs over MCP.

See blueprints
Featured blueprints

Don't start from a blank page.

All blueprints
What's in one

A blueprint is four things.

Screens, ranked

Every screen the app needs, marked must-have, nice-to-have or later — so you know what ships first and what waits for a paying customer to ask.

The corner cases

The declined card. The expired invite. The empty cart with a coupon already applied. Enumerated in a matrix, not discovered by your client on a Friday.

Pop-ups & empty screens

The invite dialog, the delete confirmation, the screen before anyone has added anything. The small ones everyone forgets, and the ones AI skips.

The decisions

What separates a real product from a pretty demo — why what Stripe says wins, where the sign-in session lives, what to check on the server.

Two ways in

Your agent reads it, or you copy the prompt.

The same blueprint either way. Pick whichever fits how you already work.

01Through your agentMCP

Your AI editor reads it for you

Connect once. Claude, Cursor or any editor that speaks MCP pulls the blueprint itself and asks for only the parts it needs — nothing to copy, nothing to paste.

URLhttps://webshots.design/api/mcpPro

Add it to Claude, ChatGPT, Cursor or any MCP app and sign in with WebShots. Account → MCP servers sets it up in one click.

What it can call
list_blueprintsEvery blueprint, with its corner-case count.
get_blueprintEverything one blueprint covers, in order.
get_sectionsJust the parts your AI asks for, in the right order.
02Pick a prompt on the siteNo setup

Tick what you need, copy the prompt

Nothing to install and no token. Open a blueprint here, choose the parts you want, and the prompt writes itself. Paste it into whatever chat you already use.

01
Open a blueprintAll six are on the site — read the whole map before you commit.
02
Tick what you needScreens, features, pop-ups and tools. The must-haves come pre-ticked.
03
Copy the promptIt rewrites itself as you tick. One button, then paste it anywhere.

Your next client project is already mapped.

Pick a blueprint, tick what the client needs, and hand it to your AI. Ship tonight.

Navigate
Browse blueprintsG B
My projectsG P
Account settingsG S
Actions
Create new project
Toggle theme
Keyboard shortcuts?