Guide
Claude Code plugin
One command installs the server, the methodology and the topic commands together. It also enforces the reading depth, which no other install path can do.
Install
Run both commands inside Claude Code. The first registers the marketplace, the second installs from it.
/plugin marketplace add https://www.lumin.guru/plugin/marketplace.json
/plugin install lumin@luminYou will be asked for your birth details during install. Enter them once and every reading command uses them, so you never retype a birth date. They are stored in your own ~/.claude/settings.json and are sent to Lumin only when you run a reading.
Then connect the server. Run /mcp, select lumin and sign in with your email address and a six digit code. From a terminal, claude mcp login lumin does the same thing.
Restart
/reload-plugins. New tools from the server can need a full restart before they resolve.What it adds
- The Lumin MCP server, all 221 tools, declared for you rather than pasted into a config file.
- Four commands.
/lumin:readingruns a complete KP reading fanned out by phase./lumin:workflowruns the same reading as a Claude Code workflow with deterministic agent fan-out, the one install path that gets real parallel execution rather than a model orchestrating it turn by turn./lumin:profileshows, checks or changes the birth details on file, for one person or several./lumin:statuschecks the connection with one call. - Five on-demand skills.
kp-readingis the orchestration hub and carries the methodology in full, rather than the roughly 2,000 characters a client delivers of a server's instructions.kp-electionalcovers choosing a date or time rather than reading a chart's promise.kp-horarycovers reading a question from a number rather than a birth chart.kp-pagingcovers how to work through a result that came back split across pages.kp-buildcovers building a product on the server rather than running a reading, from the input classes and metering to paging and the copy rules. - Two agents.
kp-phaseruns one phase of a reading in its own context, so several phases run in parallel and the raw tool output never fills the main conversation.kp-drilldowndoes the same for a single paged tool, reading it to exhaustion and returning only the finding.
The floor is enforced, not requested
A KP reading is an investigation. Depth is the reading, and a verdict from three tools is a guess in the vocabulary of one. Every other install path can only ask a model to go deep. This one can refuse to let it stop.
Two hooks do the work. After each batch of tool calls, one counts the Lumin calls made so far and reports the running total. When the turn tries to end below the floor, the other blocks it and names the tools still uncalled.
- Full reading or any life-area question. Minimum 20 calls, 25 to 40 expected.
- One focused question about a single event or window. Minimum 12 calls.
- A factual lookup such as a nakshatra or today's panchang. Minimum 5 calls.
The floor is not invented by the plugin. It comes from set_birth_profile, which routes your question to a topic and returns the numbered tool list for it. See Reading depth and call floors for how the routing works.
Where the floor applies
Hooks and agents run in Claude Code and in Cowork. They do not run in web or desktop chat. The skill and the commands work everywhere, so on those surfaces you get the methodology without the enforcement.
Cost
The plugin's command and skill descriptions add some fixed context to every session; a skill's full body only loads when it fires.
Metering does not change. Every tool call counts against the same monthly allowance of 300 calls, so a 25 to 40 call reading is roughly 8 to 12 readings a month before a call pack is drawn. Failed calls are free. The run_* composite workflows chain several engine calls into one metered call, so prefer them where they fit. See Rate limits.
Updating
/plugin marketplace update lumin
/plugin update lumin@luminPass --scope local to either command if you installed to this repository rather than to your user account. The update signal is the version string, so a rebuilt plugin at the same version will not prompt.
What you are trusting
A plugin runs code on your machine, and Claude Code does not prompt for permission at install time. Lumin's hooks are one small script that counts tool calls and writes a session file. Read it before you install if you would rather check than take our word for it.
If you are not using Claude Code
Add the server directly instead. See Quickstart for the endpoint and API key vs OAuth for choosing a credential.