Deploy and host a website from Codex or Cursor

Checked and updated 19 October 2026

Codex and Cursor can deploy a website as soon as Ginta's MCP server is added. In Codex, run codex mcp add ginta --url https://ginta.app/mcp; in Cursor, add the same address to mcp.json or use the one-click link below. Sign in to Ginta once, then ask the agent to publish: it sends hand-written pages straight to Ginta, or uploads your Vite, Astro or Next build as one zip. The site goes live at <name>.ginta.page, and on your own domain on paid plans, without a GitHub repo or a hosting account of its own.

We make Ginta. The Codex and Cursor steps below come from OpenAI's and Cursor's own docs, checked on 19 October 2026 (links at the end).

OpenAI Codex

CLI:

codex mcp add ginta --url https://ginta.app/mcp

This adds Ginta to ~/.codex/config.toml. Codex notices that Ginta uses OAuth and starts the sign-in right away: sign in to Ginta (or create a free account) and press Allow. Later, codex mcp login ginta signs in again, codex mcp list shows your servers, and /mcp in the Codex terminal UI shows the active ones.

Or by hand, in ~/.codex/config.toml:

[mcp_servers.ginta]
url = "https://ginta.app/mcp"

OAuth is the default for HTTP servers, so nothing else is needed. A project-only copy can go in .codex/config.toml (trusted projects only).

IDE extension: open the gear menu → MCP servers → Add server, enter a name, choose Streamable HTTP, paste https://ginta.app/mcp, save, then Restart extension and click Authenticate when it asks.

ChatGPT desktop app: Settings → MCP servers → Add server, choose Streamable HTTP, paste the URL, save, Restart, then Authenticate. The CLI, the IDE extension and the desktop app share the same config.toml, so you set Ginta up once.

Cursor

One click: open this link with Cursor installed and confirm the install:

cursor://anysphere.cursor-deeplink/mcp/install?name=ginta&config=eyJ1cmwiOiJodHRwczovL2dpbnRhLmFwcC9tY3AifQ==

Or by hand, in ~/.cursor/mcp.json (every project) or .cursor/mcp.json (one project):

{ "mcpServers": { "ginta": { "url": "https://ginta.app/mcp" } } }

Cursor registers itself with Ginta automatically, so there's no client ID to set. Click the sign-in button it shows for Ginta, sign in and press Allow. Servers are switched on and off on Cursor's Customize page in the sidebar. By default Cursor asks before it runs each MCP tool; that's normal.

Deploying: what the agent does

Ask, for example:

Build the project and deploy dist/ to Ginta as a new site called my-app.

The agent calls create_site without files (or upload_files without files for an existing site). Ginta answers with an upload link (15 minutes, 3 uploads) and the exact curl command that posts a .zip of the build. The agent runs it, and the JSON answer lists the new version, changed files and anything skipped. The bundle never goes through the model, so a large build costs no tokens. For a few hand-written pages, the agent sends them with create_site instead and edits them later with small find-and-replace changes.

Ginta serves clean URLs (about.html at /about), your own 404.html, and a _redirects file in the Netlify / Cloudflare Pages format, including /* /index.html 200 for single-page apps. API keys go in write-only secrets and are added by Ginta's proxy, never in page code. The full walkthrough with every command is on host a website from Claude Code: the tools are the same in every client. Reference: files and routing, secrets and connections, tools.

Ginta or another deploy plugin?

You have other options, and for some projects they are better. As checked on their own pages on 19 October 2026:

• OpenAI's Codex use case for deploying a web app uses the Build Web Apps and Vercel plugins: a preview deploy, then production when you ask.
• Netlify announced a Codex plugin on 27 March 2026 that creates projects, deploys previews and production, and reads build logs.
• Hostinger shows deploying from Cursor with its own connector plugin and a Hostinger API token, on an active Hostinger hosting service.

Pick Vercel or Netlify when the project needs server code, API routes or server-side rendering: Ginta serves static files only, plus its own parts. Ginta is the better fit for a business website or static app that should go live with no extra accounts or tokens, needs forms, bookings, a menu or a shop without other services, and that a non-technical owner can keep changing later in Ginta's editor, without Codex or Cursor.

What it costs

Deploying from Codex or Cursor uses no Ginta credits. The Free plan includes 20 websites at their Ginta address with a small "Made with Ginta" badge. Your own domain comes with paid plans (from €5 a month); Hosting, €5 a month (50 websites, 3 domains, no badge), is made for people who build with their own AI. File and size limits per plan: limits. All plans: pricing.

Sources

• OpenAI: Codex MCP docs (formerly developers.openai.com/codex/mcp, read 19 October 2026)
• OpenAI: Deploy an app or website (read 19 October 2026)
• Cursor docs: Model Context Protocol and MCP install links (read 19 October 2026)
• Netlify changelog: Deploy from Codex with the Netlify plugin (27 March 2026, read 19 October 2026)
• Hostinger: How to deploy a website from Cursor (dated 7 October 2026, read 19 October 2026)