Point an agent at a Kywi site
Reaching a Kywi site from an agent means adding the site MCP server’s command, base URL and API key to the client’s own config — by hand.
An agent reaches a Kywi site the way it reaches any MCP server: something in its own config runs a command, and that command needs credentials. Kywi's half of that is one small binary, kywi-mcp-site, scoped to exactly one site by a base URL and an API key — no project path, no site slug, nothing else to configure.
What the client config needs
Point the command at the installed package and set the two environment variables it reads: KYWI_API_URL, the site's REST base ending in /api/v1, and KYWI_MCP_API_KEY, a key scoped to that site.
{
"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"
}
}
}
}A tool call, once it is wired
Every tool the site server exposes takes plain arguments over stdio — there is no separate authentication step once the client has started the process. list_content is the one you'll reach for first, and it doubles as the cheap way to check whether something already exists before creating it: pass slug and read total rather than paging through results.
{
"type": "page",
"slug": "pricing",
"limit": 1
}This is one of two servers
The binary above is the site server — it only ever talks to one site's content over its REST API. Kywi ships a second binary, kywi-mcp-dev, for editing kywi.config.ts and scaffolding; it reads a different set of environment variables and does a genuinely different job. Wire it as a second entry in the same config when you need both — see Two servers, two jobs.