Yetty

What yetty MCP server does

The yetty MCP server gives an AI client control over websites hosted on Yetty. It can start a site from static HTML or a ZIP archive, convert that source into Yetty’s managed CMS, and apply changes to the resulting site. The platform preserves the supplied HTML structure during conversion rather than redesigning it.

Website operations span content, publishing, discovery, and day-to-day administration. An agent can update text and images, work with posts and other collection items, manage menus and taxonomy terms, edit global content and translations, and prepare a site for publication. It can also inspect traffic analytics, review leads, check links, and work with forms, integrations, and webhooks.

How it works

The hosted endpoint is https://mcp.yetty.ai/mcp and uses Streamable HTTP. Clients can authenticate through OAuth 2.0 with PKCE and dynamic client registration, or send a Yetty API key as a Bearer token. Every mutation creates a version that can be rolled back, so publishing and later recovery are handled through version history rather than separate manual backups.

The server supports staged drafts with a publishing step, readiness checks, and rollback. SEO-related operations include titles, descriptions, robots settings, AI-crawler policy, redirects, permalinks, sitemaps, and llms.txt. Site search and commerce readiness for Yetty Shops are also exposed where applicable.

Setup and configuration

For a remote-capable client, add the Yetty MCP URL as a remote connector. OAuth-capable clients can sign in with a Yetty account. API-key authentication uses an Authorization: Bearer yk_... header. Keys are created from the Yetty dashboard under API Keys and are shown only when created.

The repository also includes yetty-mcp.py, a zero-dependency Python bridge for clients that cannot connect to remote MCP servers. Configure the bridge as a local stdio server and provide the YETTY_API_KEY environment variable. Claude Code can be configured with an HTTP transport command, while Cursor, Windsurf, and VS Code can use a server URL and authorization header.

Before submitting a site for conversion, call yetty_authoring_guide. It returns the structure conventions that affect the generated CMS, including rules for repeated items, class naming, heading order, and JavaScript-rendered content.

Tools and capabilities

The yetty MCP server covers these operational areas:

• Create sites from HTML or ZIP files, upload content in chunks, start conversion, and reprocess with the latest engine.
• Edit text and image fields, compose posts, manage collections, items, menus, taxonomies, terms, global content, and translations.
• Check publication readiness, publish versions, inspect history, and roll back changes.
• Configure SEO metadata, crawler controls, redirects, permalinks, sitemaps, and llms.txt.
• Review analytics by browser, device, referrer type, and country; inspect leads; and check links.
• Manage forms, integrations, webhooks, search, and Yetty Shops readiness.

Limitations and notes

The remote service requires a Yetty account for OAuth or a Yetty API key for bearer authentication. The local bridge requires Python and a key. Site conversion itself is free, while hosting plans are charged per site. CMS quality depends on following the authoring guidance before conversion. The material does not specify individual tool names beyond yetty_authoring_guide, so clients should discover the available operations through MCP rather than relying on an undocumented static tool list.