kitchen
by lesentiel
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| KITCHEN_TOKEN | No | Your kitchen bearer token (e.g. `kit_…`), used by the Grok plugin so its MCP client can send `Authorization: Bearer kit_…`. Obtain it by calling `create_kitchen` (with the admin secret) or `redeem_invite` (with a single-use invite code). | |
| KITCHEN_MCP_URL | No | The MCP server URL to connect to, if you self-host. Defaults to `https://<your-worker-or-domain>/mcp`; local development uses `http://localhost:5173/mcp`. | |
| KITCHEN_ADMIN_SECRET | No | A secret set by whoever deploys the server. Bots connect without a token and call `create_kitchen` with this secret to get a token. Set it in `.dev.vars` for local use, or via `pnpm exec cf workers secrets update KITCHEN_ADMIN_SECRET --worker kitchen --text "$(openssl rand -base64 32)"` (or pass a secrets file at deploy time with `pnpm exec cf deploy --secrets-file <file>`). Anyone who has it can create kitchens on your server. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
No tools | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
This server cannot be deployed
Maintenance
ActivityMaintained
ResponsivenessNo issues