Connecting Claude or ChatGPT to Your Site Through MCP

Piskes Website Builder now speaks the Model Context Protocol (MCP), so Claude, ChatGPT, or any MCP-compatible assistant can connect directly to your sites — no scraping, no copy-pasting URLs into a chat window.

The address

Point your assistant's custom connector or MCP server field at https://mcp.piskes.com/mcp. You'll be asked to sign in to Piskes and shown exactly what's being requested before anything is granted — nothing connects silently.

What it can read

Ten tools are granted by default, covering the reference questions an assistant gets asked constantly: list_sites and get_site for an overview, list_pages and search/fetch for individual pages, audit_site for accessibility and SEO issues, list_deploys for publish history, list_redirects and list_branches for configuration, and get_publish_info for whether a site is actually live. None of it touches form submissions or visitor data.

What it can change

Four write tools sit behind a separate consent screen: publish_site, create_redirect, delete_redirect, and create_branch. None of them edits the text or design of a page directly — publishing ships what's already there, and the others manage routing and branching, not content.

Taking it back

Settings → Connected apps lists every assistant you've connected, what it can do, and when it last used that access. Disconnecting takes effect on the assistant's next request.

One more detail worth knowing: content an assistant reads through these tools — page names, redirect paths, audit findings — is text other people typed, including strangers filling out your forms. The server marks all of it as untrusted before an assistant sees it, so a hidden instruction inside a page name gets reported back to you rather than followed.

Full tool list and setup details are at web.piskes.com/docs/mcp.