Build and publish websites from Cursor
Cursor's agent is good at code. Kleap is where a website lives. Connect the two and the agent can create a site, push exact files to it, publish it with a live check, and read how it performs, without a deploy pipeline to set up.
Cursor supports OAuth for remote MCP servers.
What you can ask Cursor to do
Kleap is an AI website builder. Your agent gives the instructions, Kleap builds, hosts and publishes.
Build a site from a sentence
Your agent asks Kleap for a site. Kleap's AI builds it, with hosting, SSL and forms included, and returns a task the agent follows until it is done.
Edit what already exists
Find a site by name, address or domain, read its files, change exactly what must change, and keep the rest untouched. Or describe the outcome and let Kleap's AI write it.
Publish with proof it is live
A publish is reported as done only once the new version is actually serving at its URL. Your agent never hands you a dead link.
Improve SEO, once or on a schedule
Read Google Search Console numbers, find the pages that deserve work, rewrite titles and copy, publish, and report. The same prompt can run every day.
Read leads and traffic
Form submissions, visitors, pageviews and top pages come back as plain data your agent can summarise, answer or act on.
Domains, without surprise bills
The agent can search and connect domains. Buying one always goes through a payment link that you pay yourself, so nothing is bought on its own.
Connect Kleap to Cursor
One JSON entry, then a sign-in. Use the project file for one repository or the global file for all of them.
Add Kleap to mcp.json
Put this in .cursor/mcp.json for one project, or ~/.cursor/mcp.json for every project.
.cursor/mcp.json{ "mcpServers": { "kleap": { "url": "https://kleap.co/api/mcp" } } }Sign in with OAuth
Cursor supports OAuth for remote servers that require it. Open Cursor's MCP settings (the Customize page), enable kleap and sign in: a browser tab opens on kleap.co. Kleap's server publishes its OAuth metadata, so no client ID is needed.
Optional: install the Kleap skills
The skills CLI detects Cursor and installs build, edit, publish, data and multilingual skills.
Terminalnpx skills add kleaphq/skillsOr use a key instead of the browser
Create a key at https://kleap.co/settings/api-key with the narrowest preset and send it as a header.
.cursor/mcp.json{ "mcpServers": { "kleap": { "url": "https://kleap.co/api/mcp", "headers": { "Authorization": "Bearer kleap_live_sk_..." } } } }
Prompts to try in Cursor
Copy one, change the details to yours, and send it. Each one names what you want and what done looks like.
Read this repository's README and package.json, then use Kleap to build a marketing site for the project: hero, features, install steps, pricing placeholder and a contact form. Publish it and give me the URL.
Open my Kleap site's pricing page, replace its copy with the text in pricing.md from this repo, keep the layout, publish and confirm it is live.
Write the Astro page src/pages/changelog.astro and a src/data/changelog.json with the entries from CHANGELOG.md to my Kleap site using write_files, then publish it.
Pull my Kleap site's analytics and Search Console data for the last 28 days and tell me which page I should rewrite first and why.
Recurring jobs belong to the CLI
We have not verified a scheduler inside Cursor, so we do not claim one. The Kleap CLI runs anywhere: put it in cron or CI with an API key and read what Google Search says about a site, then bring the result to Cursor's agent for the edits.
Good to know
- If you create the key route above, keep the key out of version control: use the global ~/.cursor/mcp.json rather than a project file you commit.
- Kleap sites are Astro projects. write_files can push pages, data files and components, and publish builds them.
- Domain purchases always go through a payment link that you pay yourself.
Official documentation: Model Context Protocol in Cursor (docs).
Cursor and Kleap: questions
Can Cursor build a website with Kleap?
Yes. With Kleap added as an MCP server, Cursor's agent can create a site, write exact files to it, publish it and check it is live. Kleap hosts the result on a kleap.io address or your own domain.
Where does the code live?
On Kleap, as an Astro project you can read and change through the same tools. Kleap can also back the code up to GitHub; the repository you are working in stays yours.
Does Cursor run it on a schedule?
We have not verified a scheduler in Cursor. For recurring jobs, run the Kleap CLI from cron or CI with an API key, for example npx -y kleap-cli search-console followed by the name of your site.
Does it work with other editors?
Yes. Kleap's server is a standard remote MCP server, so any MCP client works. Windsurf and Cline follow the same pattern as Cursor: a URL and an OAuth sign-in.
Do I need an API key?
No. The connector signs you in with OAuth in your browser, so there is nothing to copy. An API key (kleap_live_sk_…, created at https://kleap.co/settings/api-key) is only for unattended jobs, scripts and clients that cannot open a browser. Pick the narrowest preset: Read-only to inspect sites, Build to change and publish them.
Does it cost anything to connect Kleap?
Connecting is free. Building and AI edits draw on your Kleap usage, and the free plan includes some. If your agent writes the files itself with write_files, Kleap does not run its own AI for that step. Publishing on a Kleap address is free. See the pricing page for each plan.
Using another agent?
Same Kleap account, same sites. See all the agent guides or the MCP, CLI and skills reference.
Put Cursor to work on your website
Connect once, then ask in plain words. Kleap builds, hosts and publishes, and your agent keeps the site improving.
Free to start. See pricing