Getting started
Connect Claude, ChatGPT or Cursor
Run Lumina from the AI tools you already use, through the Lumina MCP server.
If you already work in an AI tool like Claude Code, Codex, Cursor or Grok Bot, you can connect it to your Lumina account. Once connected, it can do almost anything you can do in the dashboard: add clients and deals, build demos, set up embeds, design onboarding forms, ask clients for logins, generate blog posts, read your usage, and more. A few risky actions wait for your approval. You ask in your own words, the same way you would ask Lumina Assistant.
This works through the Lumina MCP server. MCP (Model Context Protocol) is the standard way AI tools plug into other software. You do not need to understand it to use it: copy a URL and a token into your AI tool, and you are done.
Before you start
You need:
- An active Pro plan.
- An AI tool that can connect to a remote MCP server and send a custom header. Claude Code, Codex, the OpenAI API, Cursor, Grok Bot, Dots, and most AI code editors can.
Set it up
Open Developers. The MCP tab has three steps.
1. Server
The Server URL is https://luminasales.io/api/mcp. Copy it.
Under Tools, pick:
- All tools: every action, listed separately. The label shows how many. Best for most tools.
- Compact (5 tools): the agent searches for the action it needs instead of loading all of them. Pick this if your AI tool struggles with long tool lists.
2. Token
- Give the token a Name you will recognise later, like "Claude Code (MCP)".
- Choose Expires after: 30 days, 90 days, 180 days or 1 year.
- Choose Access:
- Full control: the agent can read and change your account, and generate blog posts.
- Read only: the agent can look but not change anything. It can still read client details and portal links.
- Press Create token.
The token starts with lsk_live_. It is shown once. The snippets in step 3 fill it in for you, so copy the snippet you need before you leave the page.
3. Connect your agent
Pick the tab for your tool. The snippets below show YOUR_LUMINA_TOKEN where your real token goes.
Grok Bot. Paste this to Grok Bot as a message:
Add a remote MCP server called lumina_sales at https://luminasales.io/api/mcp with the header "Authorization: Bearer YOUR_LUMINA_TOKEN". Then call lumina_get_context and follow its rules.Dots. Paste the same message. If Dots asks for the details one at a time, use these:
Name: lumina_sales
URL: https://luminasales.io/api/mcp
Transport: Streamable HTTP
Header: Authorization: Bearer YOUR_LUMINA_TOKENClaude. In a terminal, run this once:
claude mcp add --transport http lumina-sales https://luminasales.io/api/mcp --header "Authorization: Bearer YOUR_LUMINA_TOKEN"Or put this in a .mcp.json file in the project you run Claude Code from. Keep that file out of git, because it holds your token.
{
"mcpServers": {
"lumina-sales": {
"type": "http",
"url": "https://luminasales.io/api/mcp",
"headers": {
"Authorization": "Bearer YOUR_LUMINA_TOKEN"
}
}
}
}ChatGPT (Codex). Add this to ~/.codex/config.toml:
[mcp_servers.lumina_sales]
url = "https://luminasales.io/api/mcp"
bearer_token_env_var = "LUMINA_ACCESS_TOKEN"Then set the token in your environment:
export LUMINA_ACCESS_TOKEN="YOUR_LUMINA_TOKEN"General (Cursor and other editors). Most editors read this shape. Keep it out of git.
{
"mcpServers": {
"lumina-sales": {
"url": "https://luminasales.io/api/mcp",
"headers": {
"Authorization": "Bearer YOUR_LUMINA_TOKEN"
}
}
}
}The General tab also has the plain connection details and a test command for developers. The OpenAI Responses API snippet is on the ChatGPT tab. Both are covered in MCP server.
Check that it works
Ask your AI tool:
Call lumina_get_context and tell me which agency you are connected to and what you can do.It should answer with your agency name and whether it can change things or only read them. lumina_get_context also gives the agent Lumina's ground rules, such as asking you before it spends credits, and sending you a link when something needs your approval.
What to ask once it is connected
AI coding tools are especially good at the jobs that span your website and Lumina, like adding an embed to your site or making your site publish your Lumina blog posts. See Publish blog posts to your site.
What needs your approval
Some actions wait for the owner's yes, even with Full control: team changes, the billing portal, where notifications go, account deletion, renaming your subdomain, removing a domain, changing your referral code, cancelling or resuming billing on a build, buying an extra live demo slot, rotating a portal link or embed key, creating or revoking access tokens, the blog schedule, changing a lander's link, opening a client's stored login, and deleting a client, deal, demo, custom niche, lander, form or embed.
When the agent tries one of these:
- It gives you a link. The request also shows under Approvals on Developers.
- Open it, read what it will do and exactly what it sends, and press Approve or Deny.
- Tell the agent. It checks the approval and runs the request once.
An approval runs that exact request once and expires after 24 hours. See MCP server for the full list.
Two things no token can do, even with approval: switch to another agency, and use Lumina Assistant.
Keep your token safe
- Treat the token like a password. Anyone who has it can act on your account with the access you gave it.
- Never paste it into a website, a shared document, or a file that goes into git.
- Use Read only when the agent only needs to look things up.
- A Full control token can change most of your account and spend your AI credits without asking. Deletes wait for your approval, but spending does not: Lumina tells the agent to ask you first, and your AI tool decides whether it does. Keep an eye on what it is doing.
- To cut a token off, go to Issued tokens on Developers, press the trash icon next to it, and confirm. It stops working on the next request.
- Each token stops working when it expires, or when the person who created it leaves the agency.
If something goes wrong
- "Connect with an access token from the Developers page.": the agent is not sending your
lsk_live_token. Check the header is exactlyAuthorization: Bearerfollowed by the token. - The token was rejected as invalid: it may have expired or been revoked. Create a new one.
- The agent says an action needs approval: open the link it gives you, or Approvals on Developers, and press Approve. See Approvals.
- More fixes: API and MCP troubleshooting.
Still stuck? Ask Lumina Assistant in your dashboard (⌘J on any page), or read how to get help.
