servers / ai-yetty-yetty
ai.yetty/yetty MCP server
communitystreamable_httpremoteverifiedhealthy
Build, edit and run real hosted websites from your AI - content, SEO, menus, publish with rollback.
01Tools · 9
How to read this: tool names here are observed from a live tools/list handshake. The Risk label is a heuristic inferred from the tool name (write/destructive verbs), not from executing the tool — a conservative guess, not a verified capability. We never escalate risk from a description. Found one that's wrong? Tell us — we fix on report.
| Tool | Risk | Side effects | Approval |
|---|---|---|---|
| yetty_status Connection + authentication status. Call this FIRST. Unauthenticated sessions can still park a website (batch tools) and start email sign-up — the response tells you exactly how. | read | false | unknown |
| yetty_authoring_guide READ THIS BEFORE WRITING OR SENDING ANY HTML (no account needed, free, instant, no arguments). Returns yetty's exact structure rules — repeated items sharing one class, semantic class names for field labels, headings before sections, no JS-rendered content — that decide whether the site converts into a clean editable CMS with named fields and add/remove collections, or a wall of generic "Text" fields. | read | false | unknown |
| yetty_batch_start No account needed: start a PARKED file batch — send the site now, authenticate after. Returns park_ref (use it as batch_ref). Files are stored safely but NOT processed until the owner approves by email. EXAMPLE: yetty_batch_start {} -> {park_ref:"pk_..."} -> yetty_batch_file {batch_ref:"pk_...", path:"index.html", content:"..."} per file -> yetty_batch_end {batch_ref:"pk_..."} -> yetty_signup {email:"owner@x.com", park_ref:"pk_..."} -> owner clicks the email -> yetty_claim_status {park_ref:"pk_..."} gives you an API key + the build status. | read | false | unknown |
| yetty_batch_file Add ONE file to the parked batch. Args: batch_ref (the pk_... park_ref); path (relative, folders allowed); content (text) OR content_base64 (binary). Returns {received_bytes, sha256} — verify against your local copy; mismatch = resend THIS file. Send EXACT bytes, never retype. | read | false | unknown |
| yetty_batch_end Close the parked batch. Nothing is processed yet — next call yetty_signup {email, park_ref} so the owner can approve by email. | unknown | unknown | unknown |
| yetty_signup Link a parked upload to the owner's email: sends them an approval email. The site is processed ONLY after they click it. Args: email (the owner's), park_ref. Then poll yetty_claim_status every ~30s. Ask the owner to check their inbox. | unknown | unknown | unknown |
| yetty_claim_status Check a parked upload. States: parked (send yetty_signup) -> awaiting-approval (owner must click the email) -> approved (returns your api_key ONCE + waiting_url — reconnect with Authorization: Bearer <api_key> for the full toolset). | read | false | unknown |
| yetty_login Sign the OWNER in by email — no dashboard, no key copying. Works for existing accounts AND (when signups are open) new ones. FLOW: yetty_login {email:"owner@x.com"} -> {login_ref} -> the owner clicks the emailed link -> poll yetty_login_status {login_ref} every ~20s -> it returns an api_key ONCE + the exact reconnect command. Use this whenever you are unauthenticated or your token expired. | read | false | unknown |
| yetty_login_status Check an email sign-in: pending (owner has not clicked yet) -> approved (returns api_key ONCE + reconnect instructions). EXAMPLE reconnect for Claude Code: claude mcp remove yetty; claude mcp add --transport http yetty https://mcp.yetty.ai/ --header "Authorization: Bearer <api_key>" -s user | read | false | unknown |
02Install & source
https://mcp.yetty.ai/mcp
remote_url- repohttps://github.com/avniy/yetty-mcp
- homepagehttps://mcp.yetty.ai/mcp
- licenseMIT
- adoption0 stars · 0 forks
05Provenance & freshness
sourcesOfficial MCP Registry [p1]
last_checked2026-08-21 15:40Z
next_check2026-08-22 20:28Z
cadenceevery 29h
verifiedtools_list:passed handshake:passed metadata:passed
index_statusindex — 8 unique facts >= 5
06Badge
Add the “as seen on MCPExplorer” badge to your README. 
[](https://mcpexplorer.com/servers/ai-yetty-yetty)
Next step
This is one server. A loadout combines the right servers, governance, and proven plays for a whole job — assembled deliberately, not tool-dumped.
Explore loadouts →