MANAGE YOUR WEBSITES FROM YOUR AI ASSISTANT

The Static.app MCP Server for AI Assistants

Connect Static.app to AI assistants like Claude with the official Model Context Protocol server. Create, update, and manage your websites and forms in plain language, straight from your assistant, with no dashboard needed.

Get your API key Read the MCP docs

CLAUDE CODE

claude mcp add --transport sse static-app \
    https://mcp.static.app/sse \
    --header "Authorization: Bearer sk_xxxx"

ANY OTHER MCP CLIENT

URL:     https://mcp.static.app/sse
Header:  Authorization: Bearer sk_xxxx

Claude Desktop, Cursor, Windsurf and n8n all connect to the same endpoint. Full instructions per client: Setup.

  • Manage websites in plain language

    List, create, update, and delete websites and manage website files by asking your assistant. No dashboard, no clicking through menus.

  • Deploy a ZIP, or edit one file

    Ship a whole site from a ZIP archive, or have your assistant write a single page or stylesheet in place. Archives upload straight from disk, so their size never eats into the conversation.

  • Work with your form entries

    List forms, view form entries, and delete entries through your assistant, so you can triage submissions without opening the dashboard.

Connect Your Assistant in 3 Steps

  • 1

    Create your Static.app account.

  • 2

    Generate your Static.app API key and connect the MCP server with it.

  • 3

    Ask your AI assistant to deploy and manage your websites in plain language.

Why Manage Websites From Your AI Assistant?

The Model Context Protocol lets AI assistants like Claude work directly with your tools. The official Static.app MCP server wraps the Static.app REST API, so your assistant can create websites, update files, and handle form entries on your behalf instead of describing what you should click.

You connect with your own API key, and your assistant does the rest. Deploy and manage your static websites straight from the conversation, with no dashboard needed.

Not Just an MCP Server

  • Built on the Static.app REST API

    The MCP server is the official Static.app server, wrapping the same REST API you can call directly. See the MCP documentation, the API page, and the API documentation.

  • Connects with your own key

    Each user connects the MCP server with their own Static.app API key, so your assistant acts on your account and your websites.

  • Open to every account

    Any Static.app account can create an API key and connect the MCP server. Plan limits apply to what you create rather than to access itself: adding a new website fails once you reach your plan's website allowance.

Frequently Asked Questions

What is the Static.app MCP server?

It is an official Static.app Model Context Protocol server that wraps the Static.app REST API. It lets AI assistants like Claude create, update, and manage your websites and forms in plain language.

Which assistants can I use it with?

The MCP server works with AI assistants like Claude that support the Model Context Protocol. You connect it with your Static.app API key and your assistant can then manage your websites and forms.

What can the MCP server do?

It can list, create, update, and delete websites and manage website files. It can deploy a website from a ZIP archive supplied as a local file, base64 content, or an external URL. It can also list forms, view form entries, and delete entries.

How does it authenticate?

It uses your own Static.app API key. Each user connects the MCP server with their own key, so the assistant acts on your account and your websites.

How does it relate to the Static.app API?

The MCP server wraps the Static.app REST API, and both are open to any Static.app account. Every tool is listed in the MCP documentation; the underlying endpoints live on the API page and in the API documentation.