A lot of you have been asking for this, and it's the natural next step after Git Panel and hosting deploy. Right now Cloudpen deploys static and frontend projects. What's coming next is real backend hosting, starting with PHP and Laravel.

Why PHP/Laravel first: it's the most requested, and it fits how Cloudpen is architected today. Node.js, Express, and Python support will follow once that foundation is solid. Next.js SSR is on the radar too, just further out.

This turns Cloudpen from a frontend cloud IDE into a place where you can build and deploy full fullstack projects end to end. Same workflow you already know: build, git, deploy, just with a real backend running behind it.

More details soon. If backend hosting is something you need, send us an email ([email protected]) to join the waiting list and tell us what you're building. It's helping shape what ships first.

Thanks for building with us so far. More soon.

— Augustine, Founder, Cloudpen

Since launch, we've shipped consistently.

1. A full Git Panel with staging, commits, push, pull, and branches, real git under the hood, not an imitation.
2. One click SFTP Hosting Deploy straight to your own cPanel or DirectAdmin.
3. An API Client built into the editor (think of it like Postman in Cloudpen).
4. An Environment Variables manager. A templates library that grows every week.
5. And most recently, MCP support in both directions. Quill can now query your live Supabase, Postgres, or Neon backend as an MCP client, and Cloudpen itself now runs as an MCP server, so Claude Desktop, Claude Code, Cursor, or any MCP compatible client can read your project's files, git history, and deployment status directly.

That's a lot of real, ongoing engineering, and real ongoing cost on our end in AI tokens, compute, and storage to keep improving it.

Thanks for building with us so far. More soon.

Augustine

Founder, Cloudpen

A few days ago I posted that the next step was Cloudpen acting as an MCP server itself, so external tools could connect to your projects the same way Cloudpen connects out to yours. That's live now.

What this means in practice: point Claude Desktop, Claude Code, Cursor, or any MCP-compatible client at a project, and it can read your files, check deployment status, and see git history, right from your existing workflow, no copy-pasting code into a chat window.

This first release is intentionally scoped:

- Read access is on by default. Writes are a separate opt-in and go through a confirm step from the AI client. nothing gets written to a file without you seeing that request first.

- Every token is scoped to exactly one project. Connect Claude Desktop and Cursor to the same project with two separate tokens, and revoking one never touches the other.

- Write-scoped tokens expire within 90 days no matter what you set — even if you never touch the token again, it dies on its own.

- Creating a write-scoped token requires a fresh email confirmation code, regardless of how you sign in. No password required, no separate flow depending on whether you used Google, GitHub, or email/password to sign up.

You'll find it under the MCP panel in the sidebar of any project, switch to "MCP Server" (it's next to "Data Sources," which is the other direction: Quill querying your own databases).

Available on Pro, Team, and Enterprise plans, plus AppSumo Tier 2 and 3. If you're on Free or Tier 1, you'll see an upgrade prompt when you try to create a token.

As always, if you hit anything weird with this, email [email protected] directly.

Thanks for building with us early. More soon.

- Augustine

A lot of you have asked about MCP (Model Context Protocol), so here it is: Cloudpen can now connect to live MCP servers as a client, directly from the Data Sources panel in the editor.

What this means in practice: connect Cloudpen to a real backend like Supabase (or any Postgres/Neon/PlanetScale/custom MCP endpoint), and Quill can query its live schema, tables, and security posture before writing backend code for you, instead of guessing at your database structure or asking you to paste it in manually.

This first release is intentionally scoped:

- Read-only tool calls only. Quill can look, not write. No migrations, no data changes, nothing destructive gets triggered through this path.

- Supabase, Postgres, Neon, PlanetScale, and GitHub are supported providers, plus any custom MCP endpoint you want to point it at.

- Auto-fetch context is opt-in per connection, so you're always in control of what Quill sees.

You'll find it under Data Sources in the left sidebar of any project.

Next up on the roadmap: the other direction, Cloudpen acting as an MCP server itself, so external tools (your own scripts, other AI agents, whatever you're building) can connect to Cloudpen the same way Cloudpen now connects out. No firm timeline yet, but it's the natural next step and several of you have already asked for it.

As always, if you hit anything weird with this, email [email protected] directly.

Thanks for building with us early. More soon.

- Augustine

We're expanding the templates marketplace, and it's about to get a lot more interesting.

Starting this week, we're publishing new templates every week: sleek, responsive, and genuinely beautiful builds you can drop straight into a project and make your own. No more scrolling through the same handful of starters wondering if there's something fresher.

Every template is built with the same attention to detail you'd expect from a paid theme, across the stacks you actually use, React, Vue, Angular, Tailwind, Bootstrap, or plain HTML/CSS/JS. Landing pages, dashboards, portfolios, e-commerce layouts, all fully responsive and ready to customize in the editor immediately.

The goal is simple: you should never run out of templates, and Cloudpen should be the place you go for design inspiration, not just code. Pick one, fork it, make it yours.

This is just the start. More styles, more categories, and more polish are coming every week.

Thanks for building with us early. More soon.

- Augustine