# Statpio MCP server: build, publish and update websites from Claude, ChatGPT, Cursor and Claude Code

> Statpio is an MCP server. Connect it to the AI app you already use, sign in with your Statpio account, and the assistant builds websites, publishes them to your account, changes them when you ask, adds your photos, and reads your messages and visitor numbers. On every plan, free included.

- Server address: https://statpio.com/api/mcp (Streamable HTTP, OAuth 2.1 sign-in)
- This page: https://statpio.com/mcp · Markdown: https://statpio.com/mcp.md · Updated 2026-10-27
- Start free: https://statpio.com/signup · Help: https://statpio.com/help/build-with-ai · Everything about Statpio: https://statpio.com/llms.txt

## What you can ask for

### Build and publish a website

A complete site from your description, or from a starter design with your texts, contact details and colours, published to your account with a free address. A finished build can also be published from a ZIP at a public address.

Tools: create_website, create_site_from_template, deploy_website, deploy_website_zip_url

Example: "Build and publish a website for my bakery in Lisbon: the menu, opening hours and a contact form."

### Change what is live

Read the files of a site, change some of them and publish a new version. Every publish is a version, so an earlier one can be put back in one step.

Tools: get_website_files, update_website_files, list_deployments, rollback_website

Example: "Add our Christmas opening hours to the home page and publish."

### Your own photos

A private link, open for 24 hours, where you add up to 40 photos from your phone; the assistant then places them on the site.

Tools: create_photo_upload_link, list_uploaded_photos

Example: "Give me a link to upload photos of the shop, then put the best three on the home page."

### Check and improve

A check of the live site: broken links and missing files, pages without a title, description or phone viewport, images without alt text, forms Statpio cannot capture, heavy images. The assistant fixes what it finds.

Tools: check_website

Example: "Check my website and fix everything it reports."

### Messages and visitors

The messages a site received through its forms, and its visitor numbers for a period: visitors, page views, top pages, where they came from.

Tools: get_leads, get_visitor_stats

Example: "How many visitors did the site have this month, and which messages came in this week?"

### Blog and settings

A new post on the hosted blog (Solo Pro and up, with the blog turned on), or a password on a site while a client reviews it.

Tools: add_blog_post, set_site_password

Example: "Write a post about our autumn menu and publish it on the blog."

### An overview

Your websites, their addresses, their domains and whether they are live.

Tools: list_websites

Example: "Which websites do I have on Statpio, and which one is the bakery?"

### Ready-made prompts

- build_website (Build a website): Build and publish a complete website for a business.
- improve_website (Improve a website): Read a live website and improve it: texts, layout, phone view, search basics.
- website_report (Website report): A plain-language report on how a website is doing: visitors, messages and problems.

## Set up your app (checked October 2026)

### Claude

Chat. Claude on the web, Claude Desktop and Cowork. Every plan, Free included; a Free account can have one custom connector.

1. Open Statpio in the Claude connector directory and choose Connect.
2. Or add it yourself: Settings → Connectors → Add custom connector, name it Statpio, paste the address below, then Connect.
3. Sign in with your Statpio account and approve the permissions. Then ask in any chat: "Build and publish a website for …".

Connect in Claude: https://claude.ai/directory/connectors/statpio

### Claude Code

Terminal. Any plan that includes Claude Code.

1. Run the command in your project folder.
2. Type /mcp in Claude Code and sign in with Statpio in the browser it opens.
3. Then: "Publish the dist folder to Statpio and give me the address."

```sh
claude mcp add --transport http statpio https://statpio.com/api/mcp
```

### Cursor

Editor. Every Cursor plan.

1. Press Add to Cursor (Cursor must be installed), or put the JSON below in .cursor/mcp.json, in your project or globally.
2. Cursor shows Needs login next to Statpio: choose it and sign in.
3. Ask the agent to publish the folder it just built.

Add to Cursor: cursor://anysphere.cursor-deeplink/mcp/install?name=Statpio&config=eyJ1cmwiOiJodHRwczovL3N0YXRwaW8uY29tL2FwaS9tY3AifQ==

.cursor/mcp.json:

```json
{
  "mcpServers": {
    "statpio": {
      "url": "https://statpio.com/api/mcp"
    }
  }
}
```

### ChatGPT

Chat. ChatGPT on the web; custom MCP servers are a feature of the paid plans (Plus and Pro).

1. Open Plugins, choose + and then Add custom MCP server.
2. Paste the address below, choose OAuth, and choose Create as a plugin; sign in with Statpio when it asks.
3. In a chat, type @ and pick Statpio, then say what to build.

Open ChatGPT plugins: https://chatgpt.com/plugins

### Codex CLI

Terminal. OpenAI's Codex in the terminal.

1. Run the command; Codex opens the browser to sign in with Statpio.
2. Start codex and ask it to publish your build folder.

```sh
codex mcp add statpio --url https://statpio.com/api/mcp
```

### VS Code

Editor. VS Code with GitHub Copilot, in agent mode.

1. Press Install in VS Code, or use the Command Palette: MCP: Add Server → HTTP, paste the address, name it Statpio.
2. MCP: List Servers → Statpio → Start Server, allow the sign-in and finish it in the browser.
3. In agent mode, ask Copilot to publish.

Install in VS Code: vscode:mcp/install?%7B%22name%22%3A%22Statpio%22%2C%22url%22%3A%22https%3A%2F%2Fstatpio.com%2Fapi%2Fmcp%22%7D

### Windsurf

Editor. Windsurf (Cascade), every plan.

1. Add the JSON below to mcp_config.json (Windsurf settings → MCP → View raw config).
2. Refresh the servers and sign in with Statpio when asked.

mcp_config.json:

```json
{
  "mcpServers": {
    "statpio": {
      "serverUrl": "https://statpio.com/api/mcp"
    }
  }
}
```

### Gemini CLI

Terminal. Google's Gemini CLI.

1. Add the JSON below to ~/.gemini/settings.json.
2. Run /mcp list in Gemini CLI and sign in when asked.

~/.gemini/settings.json:

```json
{
  "mcpServers": {
    "statpio": {
      "httpUrl": "https://statpio.com/api/mcp"
    }
  }
}
```

### Any other MCP app

Chat. Anything that speaks MCP over Streamable HTTP with OAuth sign-in.

1. Add the address below as a remote (HTTP) server and sign in with Statpio when the app asks.
2. Coding agents: one command sets Statpio up in every agent it finds on your machine (add-mcp, a third-party tool).

```sh
npx add-mcp https://statpio.com/api/mcp
```

Address for every app: https://statpio.com/api/mcp

## What it does, and what it leaves to you

### It does

- Builds and publishes websites to your account, on the free address each site gets.
- Changes live sites file by file and publishes new versions; puts an earlier version back.
- Reads a site's messages and visitor numbers, checks a live site, writes blog posts, sets a password.
- Publishes to a site that already has your own domain: the domain stays, the files change.

### It does not

- Connect or change custom domains (the dashboard does, on Solo Pro and up).
- Touch billing, plans or your account settings.
- Delete a website, or invite clients to your portal.
- Read anything of other Statpio accounts: it works inside the account that signed in.

### Limits

- Your plan's limits apply: websites, storage, and the size of one publish (25 MB on Free Forever, 50 MB on Solo Pro, 100 MB on Agency Pro); up to 5,000 files per publish.
- Files fetched by address: up to 20 per call, 8 MB each, 16 MB together. Reading files: up to 20 files and 512 KB per call.
- Rollbacks reach back as far as your plan keeps versions: 5, 20 or 50.
- The heavier tools have their own per-account rate limits, and every publish passes the same content checks as an upload in the dashboard.

## Sign-in and permissions

1. The app sends you to statpio.com, where you sign in as usual. The app never sees your password.
2. Statpio shows the permissions the app asks for; you approve them. Each app gets its own connection.
3. The app receives a token for your account with those permissions, and uses it for every tool call.
4. Disconnect any app in your account page, under Connected AI apps, or remove the server in the app.

Permissions an app can ask for:

- projects:read: Read your websites and their settings
- projects:write: Create new websites
- deploy: Publish websites and files on your behalf
- leads:read: Read the messages (form submissions) your websites receive
- analytics:read: Read your websites' visitor statistics
- sites:manage: Write blog posts and change website settings such as password protection

An assistant follows the text it reads, including web pages and files you give it. Connect apps you trust, read what they publish, and remember that every publish is a version you can put back.

Statpio receives the tool calls, not your conversation. Photos you add through an upload link are stored in your account like any file.

## For developers

- CLI: `npx statpio deploy ./dist`. The CLI publishes a built folder with a website API key (Integrations → API keys), from a terminal or a CI job.
- The deploy API takes the same key: JSON files, an uploaded ZIP, or a ZIP by address. Every publish keeps the earlier versions.
- GitHub push-to-deploy on Solo Pro and up: connect the repository and every push goes live.
- Transport: Streamable HTTP at the address above; MCP protocol versions 2025-11-25, 2025-06-18 and 2025-03-26.
- Sign-in: OAuth 2.1 with PKCE and dynamic client registration, so any app registers itself; metadata at /.well-known/oauth-authorization-server and /.well-known/oauth-protected-resource.
- The server offers the 16 tools, 3 prompts and a resource (statpio://guide/building-websites) that tells the model how a site must be built: static files, a viewport, titles, forms without a backend.
- A website API key can use the deploy and file tools only, never messages, statistics or settings.

## Questions

### Does the connector cost anything?

No. It is part of every plan, Free Forever included. What it publishes counts against your plan like anything else: websites, storage and the size of a publish.

### Do I need a paid Claude, ChatGPT or Cursor plan?

Claude: no, a Free account can add one custom connector. ChatGPT: custom MCP servers are a feature of Plus and Pro. Cursor, Windsurf, VS Code and the terminal tools work on their free tiers; Claude Code needs a plan that includes it. Checked October 2026.

### Can the assistant see my Statpio password?

No. You sign in on statpio.com and approve what the app may do; the app gets a token with those permissions and nothing else. You can disconnect it any time in your account page.

### What if it publishes something wrong?

Every publish is a version. Put the earlier one back in the dashboard in one click, or ask the assistant to roll back. It cannot delete a website.

### Can it put the site on my own domain?

It publishes to the site, and the site keeps whatever address it has. Domains are connected in the dashboard on Solo Pro and up; after that, every publish from the assistant goes live on your domain.

### Can my clients use it?

It works with the account that owns the websites and its team. Clients who use your portal cannot connect it; they ask for changes through the portal, and you or your assistant make them.

### Which apps work?

Claude (web, Desktop, Cowork), Claude Code, Cursor, ChatGPT, Codex CLI, VS Code with Copilot, Windsurf, Gemini CLI, and any other app that supports remote MCP servers with OAuth. Statpio is listed in the Claude connector directory.

### Does Statpio see my conversations?

No. Statpio receives the tool calls the app makes (for example "publish these files") and answers them. The conversation stays with the AI provider, under its own privacy policy.