See the product in action. ― Book a free demo →
All guides
Browse all guides
Documentation
Developer tools

Connect an AI assistant with MCP

Connect your Neopress account to a compatible AI assistant, select the right site, and start with a verified read-only task.

Neopress MCP lets an AI assistant read and manage your sites through an authenticated connection. It provides tools for pages, layouts, CMS collections and entries, forms, assets, publishing, and analytics. The assistant creates the instructions and page code; MCP applies supported operations to Neopress.

Before connecting

Use an AI tool that supports remote MCP with OAuth authentication. Your target site needs Launch or Growth access; an active Neopress trial uses Launch access. The connection inherits the permissions of the account you sign in with. Connecting does not grant additional editing or publishing rights.

The remote server address is https://mcp.neopress.ai/mcp. You sign in through the browser. There is no Neopress API key to create or paste into the connection settings.

Connect from site settings

  1. Open the intended site in the Neopress dashboard and go to Settings, then AI tool connections.

  2. Choose Set up remote MCP and copy the setup prompt. It includes the server address and the site's identity.

  3. Paste the prompt into your AI tool. If the tool cannot change its own settings, add the address in its remote MCP connection settings.

  4. Start authentication, sign in to the correct Neopress account, and review the connection request before approving it.

  5. Ask the assistant to list accessible sites, select the intended site, and read its details. Check the returned name and ID before asking for changes.

The exact connection menu depends on your AI tool. For a first check, use a request like this, replacing the example ID with your own:

List my Neopress sites. Select site 123 and confirm its name.
Read the Neopress runtime contract, then list this site's pages.
Make no changes yet.

Give the assistant a clear task

Specify the site, page, intended change, and whether to stop at a draft or publish. For example: “Update the introduction on the About page for site 123, keep the layout and images, compile the page, and show the pending publication changes.” Ask for live publication explicitly when that is the intended outcome.

MCP exposes separate tools for editing and publishing. Site publication covers layout, pages, collection schemas, and forms. CMS entries have their own publish operation. Site publication through this connection currently requires an owner or admin account.

Local MCP and asset uploads

For an assistant running on your computer, local stdio MCP is also available. With Node.js 24 or later, install the CLI and MCP packages, then sign in:

pnpm add -g @neopress/cli@latest @neopress/mcp@latest
neopress login

Configure your AI tool to launch neopress-mcp as a stdio server. It can reuse the local CLI session and read local files for uploads. A remote server cannot read a path on your computer; remote tools instead support importing a public URL or uploading through a temporary storage URL.

After any requested publication, open the real site URL and verify the changed page. A successful connection, saved draft, or compiled page does not by itself confirm that visitors can see the change.

Related guides