Alchm Kitchen
Connect agents to alchm.kitchen for live transits, ESMS ingredients, cosmic recipes, synastry, and transit×natal overlays in lifestyle or culinary experiences.
Overview
Alchm Kitchen is a Build-phase MCP server that connects LLMs to alchm.kitchen live transits, ESMS ingredients, cosmic recipes, synastry, and transit×natal overlays.
What is this MCP server?
- Tools for live transits, ESMS ingredients, cosmic recipes, synastry, and transit×natal overlays
- npm package @alchm/mcp-server v1.1.1 with stdio transport
- Optional MCP_USER_API_KEY from alchm.kitchen/profile/api-keys for per-user quotas and telemetry
- Optional DATABASE_URL enables token gate and invocation logging; anonymous mode keeps all tools working
- MCP bridge to alchm.kitchen—not a generic meal-planner skill or standalone horoscope app
- Server version 1.1.1
- Five capability areas named in description: live transits, ESMS ingredients, cosmic recipes, synastry, transit×natal ove
What problem does it solve?
Builders of astro-culinary agents cannot ship trustworthy synastry or recipe overlays without a dedicated alchm.kitchen tool layer.
Who is it for?
Indie makers of niche lifestyle, food-and-cosmos, or persona-driven apps who already use MCP and alchm.kitchen data models.
Skip if: Teams needing a general nutrition database, FDA compliance tooling, or astrology features with zero external API dependency.
What do I get? / Deliverables
After configuring @alchm/mcp-server, your agent can call alchm.kitchen-backed tools for transits, ingredients, and overlays with optional keyed quotas.
- MCP tool access to transits, ESMS ingredients, recipes, synastry, and transit×natal overlays
- Anonymous or API-key-authenticated alchm.kitchen invocation path
- Optional logged invocations when DATABASE_URL is configured
Recommended MCP Servers
Journey fit
Alchm Kitchen MCP is registered while building product features that call alchm.kitchen APIs through agent tools. Integrations captures optional API-key quotas, anonymous mode, and npm stdio packaging—not launch SEO or production error monitoring.
How it compares
alchm.kitchen API MCP integration, not a markdown-only cooking skill or offline ephemeris library.
Common Questions / FAQ
Who is alchm-kitchen for?
Solo builders integrating alchm.kitchen transits, ESMS ingredients, and cosmic recipes into MCP agents for content or experiential products.
When should I use alchm-kitchen?
Use it in Build integrations when your agent must fetch live alchm.kitchen overlays rather than hard-coding static horoscope or recipe text.
How do I add alchm-kitchen to my agent?
Install @alchm/mcp-server (stdio), optionally set MCP_USER_API_KEY and DATABASE_URL, register the server in Claude Code or Cursor, and restart to load the tools.