Alchm.kitchen MCP server
A Model Context Protocol server exposing thirteen alchemical tools — live planetary transits, ingredient ESMS analysis, cosmic recipe discovery, dish-context substitutions, multi-recipe grocery consolidation, single-call meal recommendations, and safe culinary profile management — to Meta Muse, Claude Desktop, Cursor, Google Antigravity, the Claude Agent SDK, or any other MCP client.
Anonymous calls work for free tools but the cosmic recipe tool requires a key bound to a paid ESMS balance. Keys are scoped, revocable, and shown exactly once at mint time.
Mint your key →Tools
Connect Gemini, Claude, OpenAI, Meta Muse & Remote Agents
Both https://alchm.kitchen/api/mcp (Culinary & ESMS Nutrition) and https://agents.alchm.kitchen/api/mcp (72 Historical Mentors, Natal-Sky Bi-Wheel & PVR 25–99 OVR) support standard Streamable HTTP and an OpenAPI 3.1.0 REST Bridge:
- Free Tier (0 ESMS, no API key required): All 8
readOnlyHint: truetools (get_live_sky_transits,alchemize_ingredients,substitute_ingredient,build_consolidated_grocery_list,get_user_allowance,compute_synastry_overlay,get_transit_natal_overlay,compute_triplicate_synastry), plus all static resources, RFC 6570 resource templates, and prompts. - Authenticated / Metered ESMS Tier (
Authorization: Bearer sk_alchm_...): Required for full recipe search & composite recommendations (what_to_cook_now— 10 ESMS,generate_cosmic_recipe— 10 ESMS,create_evidence_snapshot— 10 ESMS,submit_recipe_reflection— 0.4 ESMS) and persistent account memory (update_culinary_profile).
1. Google Gemini CLI / Antigravity & Google ADK (google-genai)
Add to ~/.gemini/settings.json (Gemini CLI / Antigravity) or invoke via Python google-genai:
{
"mcpServers": {
"alchm-kitchen": {
"httpUrl": "https://alchm.kitchen/api/mcp",
"headers": {
"Authorization": "Bearer sk_alchm_live_…"
}
},
"planetary-agents": {
"httpUrl": "https://agents.alchm.kitchen/api/mcp",
"headers": {
"Authorization": "Bearer sk_alchm_live_…"
}
}
}
}from google import genai
from mcp import ClientSession
from mcp.client.streamable_http import streamablehttp_client
# 8 read-only tools work with zero API key; pass Authorization for paid tools
headers = {"Authorization": "Bearer sk_alchm_live_..."}
async with streamablehttp_client("https://alchm.kitchen/api/mcp", headers=headers) as (r, w, _):
async with ClientSession(r, w) as session:
await session.initialize()
client = genai.Client()
res = await client.aio.models.generate_content(
model="gemini-2.5-flash",
contents="Check live sky transits and suggest an alchemical substitute for heavy cream.",
config=genai.types.GenerateContentConfig(tools=[session]),
)
print(res.text)2. Anthropic Messages API (Remote MCP Connector)
curl https://api.anthropic.com/v1/messages \
-H "x-api-key: $ANTHROPIC_API_KEY" \
-H "anthropic-version: 2023-06-01" \
-H "anthropic-beta: mcp-client-2025-04-04" \
-H "content-type: application/json" \
-d '{
"model": "claude-sonnet-4-20250514",
"max_tokens": 1024,
"mcp_servers": [
{
"type": "url",
"url": "https://alchm.kitchen/api/mcp",
"name": "alchm-kitchen",
"authorization_token": "sk_alchm_live_..."
},
{
"type": "url",
"url": "https://agents.alchm.kitchen/api/mcp",
"name": "planetary-agents",
"authorization_token": "sk_alchm_live_..."
}
],
"messages": [{"role": "user", "content": "Alchemize garlic, lemon, and olive oil under current transits."}]
}'3. OpenAI Responses API & Custom GPT Actions (OpenAPI 3.1.0 Bridge)
import OpenAI from "openai";
const client = new OpenAI();
const response = await client.responses.create({
model: "gpt-4.1",
tools: [
{
type: "mcp",
server_label: "alchm_kitchen",
server_url: "https://alchm.kitchen/api/mcp",
headers: { Authorization: "Bearer sk_alchm_live_..." },
require_approval: "never",
},
{
type: "mcp",
server_label: "planetary_agents",
server_url: "https://agents.alchm.kitchen/api/mcp",
require_approval: "never",
},
],
input: "Match my dinner to today's planetary transits and a historical mentor.",
});For OpenAI Custom GPT Actions or Google Vertex AI Extensions, import our OpenAPI 3.1.0 schema URLs (https://alchm.kitchen/api/mcp/openapi.json and https://agents.alchm.kitchen/api/mcp/openapi.json), which execute via POST /api/mcp/rest/[toolName].
4. Meta Muse (~/.config/muse/settings.json)
{
"mcp_servers": {
"alchm-kitchen": {
"url": "https://alchm.kitchen/api/mcp",
"headers": {
"Authorization": "Bearer sk_alchm_live_…"
}
},
"planetary-agents": {
"url": "https://agents.alchm.kitchen/api/mcp",
"headers": {
"Authorization": "Bearer sk_alchm_live_…"
}
}
}
}Raw HTTP Callers & Content Negotiation
Per the official MCP 2026-07-28 Streamable HTTP specification, POST requests MUST specify both MIME types in the Accept header:
Content-Type: application/jsonAccept: application/json, text/event-stream
Omitting text/event-stream from the Accept header will cause strict MCP SDK transports to reject the call with 406 Not Acceptable. Example raw curl invocation:
curl -X POST https://alchm.kitchen/api/mcp \
-H "Content-Type: application/json" \
-H "Accept: application/json, text/event-stream" \
-H "Authorization: Bearer sk_alchm_live_…" \
-d '{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "get_user_allowance",
"arguments": {}
}
}'Modern agents can also auto-discover our capabilities and security metadata at standard endpoints:
- OpenAPI 3.1.0 REST Spec (Custom GPTs & Vertex AI):
/api/mcp/openapi.json - OAuth 2.0 Protected Resource Metadata (RFC 9728):
/.well-known/oauth-protected-resource - OAuth 2.0 Authorization Server (RFC 8414):
/.well-known/oauth-authorization-server - Meta Muse Connector Descriptor:
/.well-known/muse/connector.json
Prompts, Resources & Parameterized Templates
In addition to tools, our MCP server exposes structured Prompts (actionable blueprints for meal planning and alchemical analysis), static Resources, persistent account memory, and zero-token RFC 6570 Resource Templates:
Prompt Blueprints (prompts/list & prompts/get)
cosmic_meal_planning: End-to-end prompt guiding agents from celestial weather to recipe discovery and grocery lists.fast_pantry_dinner: Rapid single-call workflow pairing pantry ingredients and time limits withwhat_to_cook_now.pantry_alchemical_balance: Prompt guiding agents through ESMS analysis, substitutions, and flavor balancing.historical_culinary_council: Prompt to consult canonical personas like Leonardo da Vinci or Hildegard von Bingen.
Resources & RFC 6570 URI Templates (resources/list & resources/read)
alchm://ingredients/{slug}: Deep nutritional metrics, elemental properties, seasonality, and pairings for 1,002 ingredients.alchm://recipes/{id}: Full structured JSON-LD recipe payloads with metric/US volume scaling, timers, and beverage pairings.alchm://techniques/{slug}: Culinary technique guide cards (sear, braise, ferment, confit, reduce, clarify).alchm://account/culinary-profile: Authenticated caller hard allergens, dietary frameworks, spice tolerance, and kitchen equipment.alchm://account/allowance: Live ESMS balance, rate limits, and tool cost schedule for the calling account.alchm://catalog/cuisines&alchm://catalog/diets: Reference lists of supported tags.alchm://ontology/esms: Spirit, Essence, Matter, Substance philosophical and thermodynamic framework.
Connecting Claude Desktop (Local stdio)
Edit ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or the equivalent on your platform, and add:
{
"mcpServers": {
"alchm-kitchen": {
"command": "npx",
"args": ["-y", "@alchm/mcp-server"],
"env": {
"MCP_USER_API_KEY": "sk_alchm_live_…"
}
}
}
}Replace sk_alchm_live_… with the key you minted above. Restart Claude Desktop after editing.
Connecting Cursor (Local stdio)
Add to ~/.cursor/mcp.json or the project-local .cursor/mcp.json:
{
"mcpServers": {
"alchm-kitchen": {
"command": "npx",
"args": ["-y", "@alchm/mcp-server"],
"env": {
"MCP_USER_API_KEY": "sk_alchm_live_…"
}
}
}
}Per-call auth
Every tool accepts an optional _meta field on its arguments:
{
"name": "generate_cosmic_recipe",
"arguments": {
"prompt": "spicy",
"cuisine": "thai",
"_meta": {
"apiKey": "sk_alchm_live_…",
"caller": "claude-desktop"
}
}
}_meta.apiKey resolves to a row in your account, which is debited for any tool with an ESMS cost. _meta.caller is a free-form identifier (e.g. "claude-desktop", "cursor") that appears on the invocation row for observability.
If MCP_USER_API_KEY is set in the server's environment, it is used as the default for every call — convenient for single-user installs.
Quotas, telemetry, revocation
- Every successful or failed tool call writes a row to
mcp_invocations. - Insufficient ESMS balance returns a structured
QUOTAerror. Refill at /account/billing/mcp — one-shot bundles in $5 / $20 / $50 tiers. - Keys can be revoked at any time from /profile/api-keys — the next call from a revoked key returns 401.