# alchm-kitchen [Health: Active]

**Category:** 🔮 Spirituality & Esoterica  
**Repository:** https://github.com/gregcastro23/WhatToEatNext  
**GitHub Stars:** 0  
**Views:** 1  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/alchm-kitchen

## Description
Live transits, ESMS ingredients, cosmic recipes, synastry & transit×natal overlays by alchm.kitchen

## Claude Desktop Quick Installation
No confirmed install details yet, so no config is published. Follow the setup steps in the repository above.

## Documentation

## What alchm-kitchen MCP server does

The alchm-kitchen MCP server connects an MCP-compatible agent to the alchm.kitchen application and its astrology-oriented meal-planning features. Its data model combines natal-chart information, current planetary positions, elemental relationships, ingredients, and recipes. The repository describes the product as an astrological meal-planning system rather than a general-purpose food database.

The available subject areas include live transits, ESMS ingredients, cosmic recipes, synastry, and overlays that compare current transits with a natal chart. The application also includes pages for birth charts, current charts, planetary charts, recipe generation, ingredient details, meal planning, food tracking, and group recommendations.

## How it works

The MCP release adds a Bun-based tool surface to the application. A user creates a per-user API key from the `/profile/api-keys` area and uses that key when connecting an MCP client. The README names Claude Desktop, Cursor, and Cline as supported connection targets.

API keys are subject to tier-aware rate limits, and requests are tracked through telemetry. The application also supports purchasing ESMS top-ups through Stripe. That payment flow is relevant when an account needs additional ESMS capacity, but it is separate from the basic process of connecting an MCP client.

Behind the application, a Python FastAPI service using Swiss Ephemeris handles astrology-related backend work. The broader product uses PostgreSQL, Next.js, React, and Bun, with the frontend hosted on Vercel and backend services hosted on Railway.

## Setup and configuration

Start by creating an account and generating a per-user API key at `/profile/api-keys`, then provide that key to the MCP client configuration required by the client.

The repository’s local development workflow requires Bun 1.3.13 or newer. Developers working from source can clone the repository, run `bun install`, copy `.env.example` to `.env.local`, and start the application with `bun run dev`.

## Tools and capabilities

The documented capability areas include:

- Querying live planetary transits.
- Working with ESMS ingredient data.
- Generating or working with cosmic recipes.
- Comparing charts through synastry.
- Applying current-transit and natal-chart overlays.
- Using per-user API keys with tier-based rate limits and telemetry.

The application also includes meal-planning, grocery-cart, commensal, ingredient, recipe, and food-tracking surfaces.

## Limitations and notes

It also does not identify environment variables required specifically by the MCP server. The `CRON_SECRET` variable belongs to an in-progress daily-yield cron feature and should not be treated as a required MCP setting.

The alchm-kitchen MCP server depends on account-level API-key access and may apply tier-based rate limits. ESMS top-ups use Stripe, so paid capacity and MCP connectivity are separate concerns. Astrology calculations may expose a `degraded` state when the system falls back from live astronomy data, according to the repository’s observability notes.

_Full upstream README: https://allmcps.com/mcp/alchm-kitchen/readme_