Behind the counter
For developers who want to see how the dishes work. Today that's CanAI's MCP toolset. Server access, storage and an AI proxy arrive with Hosting, Kari and ToSAI.
Ready now: CanAI over MCP
CanAI exposes more than 35 operations over MCP's HTTP transport, mirroring the wp-admin screens. Your site's connection link carries a private key, which is the credential.
Claude Code
claude mcp add --transport http canai "https://your-site.com/wp-json/mcp/wpcanai/your-private-key"
Any MCP client
{
"mcpServers": {
"canai": { "url": "https://your-site.com/wp-json/mcp/wpcanai/your-private-key" }
}
}
- Version historySnapshots, an operations log, restore and pin.
- Filters for the parts you'll changeTemplate types, WooCommerce hooks, the options allowlist, page context.
Coming with each dish
Each one opens with its dish. Leave your email on the dish's page to hear the day it does.
-
Root SSH and a web terminal
With HostingFull access to your server from day one, its own IP address, and a dashboard with a typed API.
-
S3-compatible storage
With KariPoint any existing S3 SDK at your bucket. Kari uses the same storage for WordPress uploads.
-
An OpenAI-compatible inference proxy
With ToSAIA stable, metered key to the models behind ToSAI, with an IP allowlist and secrets kept on the server.


