Connect the NeoPress remote MCP server

What the remote MCP connection supports

After connecting NeoPress remote MCP, a supported AI client can read sites, pages, collections, entries, forms, assets, and analytics. With the appropriate role, it can also update drafts and run publishing actions.

1. Add the MCP server

The remote MCP URL is https://mcp.neopress.ai/mcp. Add this address as a remote server in the MCP settings of the client you use.

2. Complete OAuth authorization

When the browser authorization page opens, sign in to NeoPress and approve access. You do not need to copy or manage an API key.

3. Verify accessible sites

List the sites available to the connected account first. Use the numeric site ID in later requests to reduce the risk of changing the wrong project.

Example: List the sites available to this account, then inspect the pages for site 420 in read-only mode.

4. Separate reading from editing

Start by reading the site and page list. When editing, request a draft change rather than a production publish. Compile the affected page and inspect the publish preview before going further.

5. Request publishing separately

Connecting MCP does not publish changes automatically. Pages and layouts require a site publish, while CMS entries use a separate entry publish action. Confirm the target site and pending changes before either action.

A remote MCP server cannot read a local file path directly. Import files that already have a public URL, or use a presigned upload for local files.