14 culinary, thermodynamic & astrological tools: cauldron, transits, recipes, synastry & swaps.
Connect Runs on your machine
claude mcp add alchm-kitchen -e MCP_USER_API_KEY=<MCP_USER_API_KEY> -e ALCHM_MCP_USER_API_KEY=<ALCHM_MCP_USER_API_KEY> -e DATABASE_URL=<DATABASE_URL> -e ALCHM_MCP_MODE=<ALCHM_MCP_MODE> -e ALCHM_MCP_REMOTE_URL=<ALCHM_MCP_REMOTE_URL> -e ALCHM_MCP_BACKEND_URL=<ALCHM_MCP_BACKEND_URL> -- npx -y @alchm/[email protected]{
"mcpServers": {
"alchm-kitchen": {
"command": "npx",
"args": [
"-y",
"@alchm/[email protected]"
],
"env": {
"MCP_USER_API_KEY": "<MCP_USER_API_KEY>",
"ALCHM_MCP_USER_API_KEY": "<ALCHM_MCP_USER_API_KEY>",
"DATABASE_URL": "<DATABASE_URL>",
"ALCHM_MCP_MODE": "<ALCHM_MCP_MODE>",
"ALCHM_MCP_REMOTE_URL": "<ALCHM_MCP_REMOTE_URL>",
"ALCHM_MCP_BACKEND_URL": "<ALCHM_MCP_BACKEND_URL>"
}
}
}
}{
"mcpServers": {
"alchm-kitchen": {
"command": "npx",
"args": [
"-y",
"@alchm/[email protected]"
],
"env": {
"MCP_USER_API_KEY": "<MCP_USER_API_KEY>",
"ALCHM_MCP_USER_API_KEY": "<ALCHM_MCP_USER_API_KEY>",
"DATABASE_URL": "<DATABASE_URL>",
"ALCHM_MCP_MODE": "<ALCHM_MCP_MODE>",
"ALCHM_MCP_REMOTE_URL": "<ALCHM_MCP_REMOTE_URL>",
"ALCHM_MCP_BACKEND_URL": "<ALCHM_MCP_BACKEND_URL>"
}
}
}
}{
"servers": {
"alchm-kitchen": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@alchm/[email protected]"
],
"env": {
"MCP_USER_API_KEY": "<MCP_USER_API_KEY>",
"ALCHM_MCP_USER_API_KEY": "<ALCHM_MCP_USER_API_KEY>",
"DATABASE_URL": "<DATABASE_URL>",
"ALCHM_MCP_MODE": "<ALCHM_MCP_MODE>",
"ALCHM_MCP_REMOTE_URL": "<ALCHM_MCP_REMOTE_URL>",
"ALCHM_MCP_BACKEND_URL": "<ALCHM_MCP_BACKEND_URL>"
}
}
}
}Replace the values in angle brackets with your own. Keys stay on your machine; we never see them.
Tools
This server runs locally, so its tools are listed by your MCP client once it starts.
Environment variables
| Name | Description |
|---|---|
MCP_USER_API_KEYOptional, secret | Optional alchm.kitchen API key (mint at https://alchm.kitchen/profile/api-keys). Without DATABASE_URL the server forwards each call to the hosted endpoint, which validates the key and applies billing. Without a key, read tools run locally in demo mode; reflection publication requires a key. |
ALCHM_MCP_USER_API_KEYOptional, secret | Alias for MCP_USER_API_KEY, supported in sanitized Planetary Agents client environments. |
DATABASE_URLOptional, secret | Operator-only PostgreSQL connection string. Setting it runs the tools in-process and validates keys and ESMS billing locally; leave it unset to use the hosted service (with a key) or demo mode (without). |
ALCHM_MCP_MODEOptional | Optional. auto (the default): with an API key and no DATABASE_URL the server forwards to the hosted endpoint, otherwise it runs in-process. remote: always forward to the hosted endpoint, even if an unrelated DATABASE_URL is set in the environment (needs MCP_USER_API_KEY). local: always run in-proce… |
ALCHM_MCP_REMOTE_URLOptional | Optional. The hosted MCP endpoint a key-only install forwards to, and the place your API key is sent: set it only to a host you trust. Defaults to https://alchm.kitchen/api/mcp; must be https (http is accepted only for localhost). |
ALCHM_MCP_BACKEND_URLOptional | Backend origin serving /api/astrologize. Bundled artifacts default to https://alchm.kitchen; source runs default to http://localhost:3000. It is also where the in-process server sends a keyed tool call when it has no database (ALCHM_MCP_MODE=local), so it is where your API key goes then: https, or… |
Details
| Package | @alchm/[email protected] (NPM, stdio) |
| First published | 12 Nov 2026 |
| Last updated | 12 Nov 2026 |
| Registry name | io.github.gregcastro23/alchm-kitchen |
More other servers See all
Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.