Yetty README | AllMCPs

Yetty MCP Server

Run a real, hosted website from your AI. Yetty turns any static HTML into a fully managed, hosted site with a CMS built around it - byte-true, nothing redesigned - and this MCP server is the control plane: your AI can build, edit, publish and monitor the site end to end.

Remote server: https://mcp.yetty.ai/mcp (Streamable HTTP)
Auth: OAuth 2.0 (PKCE + dynamic client registration) - or a yk_ API key as a Bearer header
Registry: published as ai.yetty/yetty in the official MCP Registry

What your AI can do with it

Area	Tools
Build & convert	create a site from HTML/zip, upload in chunks, start the free conversion, reprocess through the latest engine
Content	edit any text/image field, compose posts, manage collections and items, menus, taxonomies and terms, global content, translations
Publish	publish with a version history, check readiness, roll back anything, staged drafts with one publish door
Grow	SEO (titles, descriptions, robots, AI-crawler policy), site search, redirects, permalinks, sitemaps + llms.txt
Run	real traffic analytics (incl. browsers, devices, referrer types, countries), leads inbox, forms, integrations/webhooks, link checks
Commerce	store status and readiness (Yetty Shops)

Every mutation lands as a rollbackable version - nothing is ever lost.

Connect

Claude (claude.ai / Claude Desktop)

Settings → Connectors → Add custom connector → https://mcp.yetty.ai/mcp → sign in with your Yetty account (OAuth).

Claude Code

Terminal

claude mcp add --transport http yetty https://mcp.yetty.ai/mcp
# or with an API key instead of OAuth:
claude mcp add --transport http yetty https://mcp.yetty.ai/mcp --header "Authorization: Bearer yk_your_key"

Cursor / Windsurf / VS Code (and any client with remote MCP)

config.json

{
  "mcpServers": {
    "yetty": {
      "url": "https://mcp.yetty.ai/mcp",
      "headers": { "Authorization": "Bearer yk_your_key" }
    }
  }
}

ChatGPT / Grok / other MCP-capable apps

Add a remote MCP connector pointing at https://mcp.yetty.ai/mcp. Clients that support OAuth sign in with your Yetty account; the rest use a yk_ API key in the Authorization: Bearer header.

Local stdio bridge (no remote-MCP support)

yetty-mcp.py in this repo is a zero-dependency Python bridge:

config.json

{
  "mcpServers": {
    "yetty": {
      "command": "python",
      "args": ["/path/to/yetty-mcp.py"],
      "env": { "YETTY_API_KEY": "yk_your_key" }
    }
  }
}

Getting a key

Sign up free at yetty.ai
Dashboard → API Keys → Create API key (shown once)
Or skip keys entirely: use OAuth from any connector-capable client.

Full client-by-client setup: yetty.ai → Dashboard → Connect your AI.

Notes for builders

Before sending a site, call the free yetty_authoring_guide tool - it returns the structure rules (repeated items share one class, semantic class names, headings before sections, no JS-rendered content) that decide how clean the generated CMS is. Conversion is free; hosting plans are per site.

License

MIT - see LICENSE.