Something wrong?

Say so in the chat first — most problems are quicker to fix there, because devkoi can see what happened to your site.

“That’s not what I meant” is enough to start with. Every change is kept as a version, so asking for something back is not a rebuild.

Before you ask

Two things account for most of what people write in about, and both are answered already:

How it works — what happens at each step, why a preview link stops working after 24 hours, and what publishing does.
Questions — who owns the site, taking it elsewhere, using your own domain, and who in a group can change things.

Connect devkoi to your assistant

devkoi runs as an MCP server. Add it once and build your site from the assistant you already have open.

Server URL

https://api.devkoi.com/mcp

Any MCP client that can talk to a remote server over HTTP will take this. The cards below are the shortcuts for the common ones.

Claude Code

One command

claude mcp add --transport http devkoi https://api.devkoi.com/mcp

Gemini CLI

One command

gemini mcp add --transport http devkoi https://api.devkoi.com/mcp

VS Code

One command

code --add-mcp '{"name":"devkoi","type":"http","url":"https://api.devkoi.com/mcp"}'

Cursor

Config file

~/.cursor/mcp.json

{
  "mcpServers": {
    "devkoi": {
      "url": "https://api.devkoi.com/mcp"
    }
  }
}

Claude desktop and web

Settings

Settings
Connectors
Add custom connector
Paste the URL above

ChatGPT

Settings

Settings
Connectors
Add custom connector
Paste the URL above

Menus move. If the steps do not match what is in front of you, the server URL is the only part that matters — add it wherever that client keeps its MCP servers.