Connect Your AI Assistant

Connect the AI assistant you already use to Landingsite, and run your website from the chat. Ask it to build a site, change your hours, publish, or tell you about this week’s leads and orders.

The fastest way: open landingsite.ai/mcp and pick ChatGPT, Claude or Grok.

Let your agent set it up

If you use a coding agent such as Claude Code, Codex or Cursor, paste this into it:

Set me up with Landingsite. Fetch https://www.landingsite.ai/install.md and follow it.

It adds Landingsite, opens the sign-in page for you, and checks that it’s connected to the right account.

Connect it yourself

Every assistant uses the same server address:

https://mcp.landingsite.ai/mcp

ChatGPT

Go to chatgpt.com/plugins, select +, then Add custom MCP server.
Name it Landingsite and paste the server address.
Choose OAuth for authentication, confirm the warning, and select Create as a plugin.
Open your personal plugins, open Landingsite and select + to install it. Sign in to Landingsite when ChatGPT asks.
On the ChatGPT homepage, switch from Chat to Work, start a new chat, type @ and pick Landingsite.

Your ChatGPT workspace admin may need to allow custom MCP servers first.

Claude (claude.ai and the desktop app)

Open Settings → Connectors and choose Add custom connector.
Name it Landingsite, paste the server address, and choose Add.
Choose Connect and sign in to Landingsite.

On a Team or Enterprise plan, an owner may need to add the connector for the organization first.

Claude Code

claude mcp add --transport http landingsite https://mcp.landingsite.ai/mcp

Then run /mcp in Claude Code, select landingsite and choose Authenticate.

Codex

codex mcp add landingsite --url https://mcp.landingsite.ai/mcp
codex mcp login landingsite

Cursor

Add this to ~/.cursor/mcp.json (or .cursor/mcp.json in your project):

{
  "mcpServers": {
    "landingsite": {
      "url": "https://mcp.landingsite.ai/mcp"
    }
  }
}

VS Code

Run:

code --add-mcp '{"name":"landingsite","type":"http","url":"https://mcp.landingsite.ai/mcp"}'

Grok and other assistants

Open the assistant’s connector or MCP settings (in Grok: grok.com/connectors → New Connector → Custom), add a custom connector and paste the server address. Any assistant that supports remote MCP servers with OAuth works.

Whichever assistant you use, the next steps are the same:

A Landingsite sign-in page opens. Sign in with the account that owns your websites. If you don’t have one yet, create it on the same page.
Landingsite shows what the assistant is asking for. Choose Allow.
Ask your assistant “Which Landingsite account am I connected to?” It should answer with your email address. If it’s the wrong account, disconnect (below) and connect again.

Things to ask

Once you’re connected, ask in your own words. For example:

“Build a website for my bakery, Rise & Crumb, in Portland. We sell sourdough and custom cakes and take pickup orders.”
“Change our Saturday hours to 8am to 2pm and publish it.”
“Show me this week’s new leads from my website and draft a reply to the newest one.”
“List the orders from the last 7 days and tell me which ones still need to ship.”
“Find a domain for my bakery website and connect it.”
“Add a catering page with our menu and a form to request a quote.”

Your assistant works through Landingsite’s own website editor, so every change lands the same way it would if you typed it in the Landingsite app. You’ll see the preview before anything goes live, and it only publishes when you say so.

What connecting allows

When you allow access, your assistant can:

Create, edit and publish your websites and their domains.
See and manage your leads, orders, customers and invoices.

It acts as you, with the same access you have on each website. It can’t do anything your role on a site doesn’t allow, and it never gets staff access.

Some things stay with you in the Landingsite app. Refunds, cancelling a subscription, voiding an invoice and similar money changes are never done by your assistant: it gives you a link, and you confirm them in Landingsite. Nothing is charged inside the chat.

Plans and credits

Connecting works on every plan. Editing uses your site’s editing credits, the same as editing in the app; if a site runs out, your assistant gives you a link to add more. Publishing needs a paid plan, which you buy in the Landingsite app.

Troubleshooting

It connected to the wrong account. Disconnect, sign out of Landingsite in your browser, then connect again and sign in with the right account.
The sign-in page doesn’t open. Check that the address is exactly https://mcp.landingsite.ai/mcp, including /mcp. In Claude Code run /mcp and choose Authenticate; in Codex run codex mcp login landingsite.
My assistant says it can’t edit a site. Editing through an assistant works on React websites. Older sites can still be read, but are edited in the Landingsite app.
ChatGPT doesn’t offer custom MCP servers. Your plan or workspace may not allow them yet; ask your workspace admin.

Disconnect

Remove Landingsite in your assistant’s settings (Claude and ChatGPT: the connectors or plugins page; Claude Code: claude mcp remove landingsite; Codex: codex mcp remove landingsite; Cursor and VS Code: delete it from the MCP servers list). Your sites and data stay as they are.