Claude Code
One commandclaude mcp add --transport http devkoi https://api.devkoi.com/mcp devkoi runs as an MCP server. Add it once and ask for a site the same way you would in the chat.
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 mcp add --transport http devkoi https://api.devkoi.com/mcp gemini mcp add --transport http devkoi https://api.devkoi.com/mcp code --add-mcp '{"name":"devkoi","type":"http","url":"https://api.devkoi.com/mcp"}' ~/.cursor/mcp.json
{
"mcpServers": {
"devkoi": {
"url": "https://api.devkoi.com/mcp"
}
}
} 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.
The first time your assistant connects, it will open a page asking you to approve it. Sign in with Google there and it comes straight back — the assistant then works on your sites on your behalf, and you can disconnect it at any time from your dashboard.
You do not need an API key. devkoi does not have any.
Once connected, the assistant can:
Some assistants cannot sign in — Meta's agent is one. For those, open Assistants in your dashboard, create a token, and paste that where the API key is asked for. Give it only what that assistant needs: publishing is a separate tick, and a token that can publish is one that can put your site on the internet without asking you first.
The same thing you would say in Telegram. The assistant passes it on and reports back what changed.
Preview links still last 24 hours, free plans still do not publish, and every change is still a version you can go back to. How it works covers all of it.
Free to build. Publishing starts at $19 a month.