Guide
Set up with your coding agent
Paste one prompt into your coding agent. It adds the key to your env, connects over MCP, makes the first call and shows you the result. You supply the API key and decide which tools the product uses.
The prompt
This works in Claude Code, Cursor, Codex, or any agent that can edit your project and run it.
Wire the Lumin MCP server into this project. Lumin computes astrology (KP, Parashari, Jaimini and Tajik) and every result carries the rule it applied and where that rule comes from.
Read https://docs.lumin.guru/setup.md first, and follow it over anything you assume about Lumin.
1. Add LUMIN_API_KEY to the project's env example file, then ask me for the key. It starts with mcp_ and I create it at https://app.lumin.guru/api-keys. Never commit it and never print it.
2. Connect with this language's official MCP SDK over Streamable HTTP to https://mcp.lumin.guru/mcp, sending the header Authorization: Bearer <LUMIN_API_KEY>.
3. Call tools/list and tell me how many tools came back.
4. Call set_birth_profile with this test chart and a question, and show me the reading plan it returns:
birth_datetime 1992-08-14T04:32:00, latitude 6.927, longitude 79.861, utc_offset_minutes 330, ayanamsa kp, question "When is marriage likely?"
5. When you show a result to users, keep the rule and source fields it carries. Do not strip them to save space.
Stop and ask me before choosing which tools the product calls. The right set depends on what the product does.What the agent reads
The prompt points the agent at docs.lumin.guru/setup.md, a plain text page written for agents. It holds the endpoint, both ways to sign in, the headers the transport needs, and the reading rules. It is built from the same source as these docs, so it changes when the server does.
For a quick start with no project yet, the one line version works too.
Read https://docs.lumin.guru/setup.md and follow it to set up Lumin for me.What you still do yourself
- Create the API key at app.lumin.guru/api-keys. The agent asks for it and never commits it.
- Choose the tools. The prompt stops before this on purpose, because a matrimonial app and a scheduling app call different sets. The use cases map products to tools.
- Keep the provenance. Every result carries the rule it applied and its source. Show it, or keep it where a practitioner can reach it.
Working in Claude Code?
kp-build skill loads when you build on the server and covers the call shape, metering, paging and provenance.Want a working app to start from? The example apps repository ships an AGENTS.md and an .mcp.json at its root, so an agent can clone it and run an app.