The only connection you need is your private MCP URL. Open the MCP page in your dashboard, copy the URL, and paste it into Claude Desktop or Claude Code. Your key is already inside the URL, so there is no header and no API key to set. Once Claude is connected, you build everything by chatting: your casino library, your landers, and even adding and verifying a domain.
CasinoLanders keeps setup deliberately small. There is exactly one thing to connect: your private MCP URL, which links Claude to your account. That single URL is how Claude reads your live casino library and follows the compliant build rules baked into the server. There are no third-party accounts to link and no separate keys to juggle. You paste one URL into Claude once, and from then on every lander is a conversation.
The MCP URL is served over streamable HTTP, and your key is embedded directly in it. That is why there is no separate token field, no Bearer header, and no API key to copy. Copy the URL, paste it into Claude, and you are connected. Because everything the AI needs travels through this one URL, it is the only credential you have to keep safe.
Everything starts on the MCP page in your dashboard.
Open the MCP page in your dashboard. Every account has one private MCP URL, served over streamable HTTP. Your key is already part of that URL, so there is nothing else to fill in, no header to set, and no separate API key to manage. Use the copy button to grab the full URL, or copy the ready-made Claude Desktop config block that already wraps it.
In Claude Desktop, open claude_desktop_config.json and add a CasinoLanders entry under mcpServers with a single url field set to your MCP URL. That is the whole configuration, because the key lives inside the URL. Save the file and restart Claude Desktop so it loads the CasinoLanders server on startup.
If you use Claude Code instead, add the same URL from your terminal with claude mcp add --transport http casinolanders "<url>", pasting your real MCP URL in place of the placeholder. Claude Code registers the CasinoLanders server over HTTP using only that URL, with no token flag to pass separately.
Because your key is inside the MCP URL, treat the whole URL like a password. Every call through it is scoped to your account, so Claude only ever sees your own casino library and affiliate links, never anyone else's. If the URL is ever exposed, open the MCP page and rotate it. Rotating issues a fresh URL and immediately stops the old one from working, so update Claude with the new value afterward.
The MCP URL contains your key, so it is the one value to keep private. There is no other secret to manage, no header to add, and no API key to store separately. If the URL ever leaks, rotate it on the MCP page and paste the new one into Claude.
You can connect from Claude Desktop or Claude Code. Both use the same single MCP URL, and neither needs a separate key.
One url field in claude_desktop_config.json, then restart Claude.
One command adds the server over HTTP.
Replace <url> with your real MCP URL from the dashboard. Because the key is inside the URL, there is no token flag to pass. Claude Code registers the CasinoLanders server over HTTP and it is ready to use.
With the MCP URL in place, Claude works directly against your account by chatting. It can build your casino library, adding each casino with its logo, bonus, rating, pros and cons, and affiliate link. It can design landers, from Top-10 lists to single reviews, comparisons, and bonus pages. It can add a domain and run the verify step that issues your free SSL certificate. And it can assign a domain to a specific lander so the page goes live. All of it flows through the one URL you pasted, and all of it stays scoped to your data.
Keep the MCP URL private and rotate it on the MCP page if you ever think it has leaked. Rotating issues a new URL and immediately disconnects any client still using the old one, so update Claude with the fresh value right after.
It is your private connection between Claude and CasinoLanders, served over streamable HTTP. You find it on the MCP page in your dashboard, where a copy button gives you the full URL and a ready-to-paste Claude Desktop config block.
No. Your key is already inside the MCP URL, so there is nothing else to configure. You do not set a Bearer header or a separate API key. You just paste the one URL into Claude Desktop or Claude Code.
Open claude_desktop_config.json and add a CasinoLanders entry under mcpServers with a single url field set to your MCP URL. Save the file and restart Claude Desktop so it loads the CasinoLanders server.
From your terminal, run claude mcp add --transport http casinolanders "<url>" using your real MCP URL. Claude Code registers the CasinoLanders server over HTTP with just that URL, no extra flags.
Once connected, Claude can build your casino library, design landers such as Top-10 lists, single reviews, comparisons, and bonus pages, add and verify a domain, and assign a domain to a lander, all by chatting through your MCP.
Yes. The URL is unique to your account and every call is scoped to you, so keep it secret. If it leaks, open the MCP page and rotate it, which issues a new URL and immediately disconnects any client still using the old one.
No. You can build your casino library first. Connecting Claude with your MCP URL is what unlocks AI building, so do it before you ask the AI to design and publish a lander.