Two servers, two jobs
The site server reads and writes one site’s content over its API; the developer server edits `kywi.config.ts` or scaffolds through that same API.
Kywi ships two MCP servers, and which one is running decides what an agent can do — not a mode flag on a single server, but two separate binaries with two tool sets that meet in exactly three names.
The site server: one site, its content
Everything the site server registers — content, layout, feeds, components, menus, search, media, users — goes over that one site's REST API. It never opens kywi.config.ts; there's no local file path in its configuration for it to open. Everything it does, it does as whatever role the API key in its config carries.
Its content tools are generic and take the type as an argument: create_content, list_content, update_content. The source also carries a function that would register a create_<type>/list_<type> pair per declared content type — create_blogPost, list_blogPost — but the shipped binary never calls it, so those tools do not exist in the list your agent sees. Don't write a prompt that waits for one.
The developer server: config and scaffolding
The developer server can point at a local kywi.config.ts, work purely through the REST API, or have both configured — which one it lands on for a given connection is its own page (The developer server's mode decides your tool list).
Wiring both at once
Nothing stops both from being configured in the same client — they're separate entries, started as separate processes, and an agent mid-build reaches for whichever one the task needs: content and layout changes go to the site server, a new content type or a module registration goes to the developer server.
{
"mcpServers": {
"kywi-site": {
"command": "node",
"args": ["node_modules/@kywi-software/mcp/dist/site/cli.js"],
"env": {
"KYWI_API_URL": "http://localhost:3000/api/v1",
"KYWI_MCP_API_KEY": "kywi_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"
}
},
"kywi-dev": {
"command": "node",
"args": ["node_modules/@kywi-software/mcp/dist/developer/cli.js"],
"env": {
"KYWI_CONFIG_PATH": "./kywi.config.ts",
"KYWI_API_URL": "http://localhost:3000/api/v1",
"KYWI_MCP_DEV_KEY": "kywi_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx",
"KYWI_MCP_MODE": "auto"
}
}
}
}Reaching a site at all — the site server's own config shape — is covered in Point an agent at a Kywi site; an API key's own limits, which apply to whichever server is using it, are covered in API keys: scopes are a role ceiling.