Download the PHP package upassist/neos-mcp without Composer

On this page you can find all versions of the php package upassist/neos-mcp. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.

FAQ

After the download, you have to make one include require_once('vendor/autoload.php');. After that you have to import the classes with use statements.

Example:
If you use only one package a project is not needed. But if you use more then one package, without a project it is not possible to import the classes with use statements.

In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
Some PHP packages are not free to download and because of that hosted in private repositories. In this case some credentials are needed to access such packages. Please use the auth.json textarea to insert credentials, if a package is coming from a private repository. You can look here for more information.

  • Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
  • To use Composer is sometimes complicated. Especially for beginners.
  • Composer needs much resources. Sometimes they are not available on a simple webspace.
  • If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
  • Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Please rate this library. Is it a good library?

Informations about the package neos-mcp

UpAssist.Neos.Mcp

Let AI assistants manage your Neos CMS content — safely, with human review before anything goes live.

This package adds an HTTP bridge to your Neos CMS installation that AI tools like Claude Code and Cursor can connect to via the Model Context Protocol (MCP). The AI can read pages, create and edit content, manage assets, and generate preview links. All changes are staged in a separate workspace so an editor can review before publishing.

How it works

There are two components to install:

  1. This package (upassist/neos-mcp) — a Neos Flow package that exposes content operations as a REST API
  2. The MCP server (@upassist/neos-mcp) — a lightweight Node.js process that translates between MCP protocol and the REST API

Quick start

1. Install the Neos package

2. Generate a shared token

The bridge uses a Bearer token to authenticate requests. Generate a secure token and add it to your Neos .env file:

3. Install the MCP server

The MCP server is a small Node.js application that runs locally on the developer's machine. See the neos-mcp-client README for detailed installation and configuration instructions per editor.

Quick version for Claude Code:

Add a .mcp.json to your Neos project root:

Important: Add .mcp.json to .gitignore — it contains your token.

4. Try it out

Start your Neos instance, open Claude Code (or Cursor), and ask:

"Show me the pages on my Neos site"

The AI will call neos_get_site_context and show you the site structure. From there you can ask it to edit content, create pages, upload images, and more — all staged for your review.

Requirements

Version Neos CMS PHP Branch
v2.x 9.0+ 8.2+ main (this branch)
v1.x 8.3 8.1+ neos-8

Node.js 18+ is required for the MCP server in both versions.

Configuration

The default settings work out of the box. The only required configuration is the API token in your .env file (see step 2 above).

Workspace

All content changes are written to a dedicated mcp workspace (branched from live). This workspace is created automatically on first use. Changes remain there until explicitly published — the AI never auto-publishes to live.

Authentication

Every request to the bridge must include a Bearer token:

By default, authenticated requests get Neos.Neos:Administrator privileges. To restrict this to Editor privileges, add to your site's Settings.yaml:

Full settings reference

What the AI can do

Once connected, the AI assistant has access to these capabilities:

Read content

Tool Description
neos_get_site_context Get site structure, all node types with properties, and page tree
neos_list_pages List all pages in a workspace
neos_get_page_content Get all content nodes on a specific page
neos_get_document_properties Get page-level properties (title, SEO fields, etc.)
neos_list_node_types List available node types and their properties

Create and edit content

Tool Description
neos_update_node_property Update a property on an existing node (text, images, metadata)
neos_create_content_node Create a new content element inside a page
neos_create_document_node Create a new page
neos_move_node Move a node to a new position
neos_delete_node Remove a node

Manage assets

Tool Description
neos_list_assets Browse the Media Manager (filter by type, tag)
neos_list_asset_tags List available asset tags

Review and publish

Tool Description
neos_get_preview_url Generate a 24-hour preview link (no Neos login needed)
neos_list_pending_changes See what has been changed
neos_publish_changes Publish all changes from workspace to live

Typical AI workflow

Entity CRUD (advanced)

Beyond Neos content nodes, the bridge can also expose custom Doctrine entities for CRUD operations. This is useful for managing data stored in custom database tables (e.g. notifications, form submissions, product data).

Packages declare their entities in YAML — no code changes in the bridge itself:

Once configured, the AI gets access to generic entity tools: neos_entity_discover, neos_entity_list, neos_entity_show, neos_entity_create, neos_entity_update, neos_entity_delete, and neos_entity_action.

Supported field types

Type Description
string, text, markdown Text fields
integer, float Numeric fields
boolean Boolean (also accepts string "true"/"false")
datetime ISO 8601 date/time
reference UUID reference to another entity
asset Reference to a Neos asset (by UUID)
enum Validated against a list of allowed values
json JSON data

Service delegation

When a service and serviceMethods are configured, CRUD operations are routed through a service class instead of direct repository calls. This preserves business logic like validation, markdown rendering, and side effects. Use parameterMapping when service method parameters differ from field names.

Full entity configuration reference

Review Status (opt-in)

The package includes an optional review workflow that shows editors which pages were modified by AI and what changed.

Enabling

Add the mixin to your Document node types:

What it does

The Review tab in the inspector shows:

API reference

Full REST API documentation All endpoints are available under `/neos/mcp/` and accept/return JSON. Every request requires a `Authorization: Bearer ` header. ### GET /neos/mcp/getSiteContext Returns site info, all node types with properties, and the page tree. Typically the first call an MCP client makes. ### POST /neos/mcp/setupWorkspace Creates the MCP workspace if it doesn't exist. ### POST /neos/mcp/listPages List all document nodes. Optional parameter: `workspace` (default: `mcp`). ### POST /neos/mcp/getPageContent Get all content nodes for a page. Parameters: `nodePath` (required), `workspace` (default: `mcp`). ### POST /neos/mcp/getDocumentProperties Get document-level properties. Parameters: `nodePath` (required), `workspace` (default: `mcp`). ### POST /neos/mcp/listNodeTypes List available node types. Parameter: `filter` — `content`, `document`, or `all` (default: `content`). ### POST /neos/mcp/updateNodeProperty Update a single property on a node. Parameters: `contextPath` (required), `property` (required), `value` (required), `workspace` (default: `mcp`). For image/asset properties, pass the asset UUID — it will be resolved automatically. ### POST /neos/mcp/createContentNode Create a content node. Parameters: `parentPath` (required), `nodeType` (required), `properties` (optional), `workspace` (default: `mcp`). ### POST /neos/mcp/createDocumentNode Create a page. Parameters: `parentPath` (required), `nodeType` (required), `properties` (optional), `workspace` (default: `mcp`), `nodeName` (optional), `insertBefore`/`insertAfter` (optional). ### POST /neos/mcp/moveNode Move a node. Parameters: `contextPath` (required), plus exactly one of: `insertBefore`, `insertAfter`, or `newParentPath`. Optional: `workspace` (default: `mcp`). ### POST /neos/mcp/deleteNode Remove a node. Parameters: `contextPath` (required), `workspace` (default: `mcp`). ### POST /neos/mcp/listPendingChanges List unpublished changes. Parameter: `workspace` (default: `mcp`). ### POST /neos/mcp/getPreviewUrl Generate a 24-hour preview URL. Parameters: `nodePath` (required), `workspace` (default: `mcp`). ### GET /neos/mcp/listAssets List assets from Media Manager. Parameters: `mediaType` (default: `image`), `tag`, `limit` (default: `50`), `offset` (default: `0`). ### GET /neos/mcp/listAssetTags List all asset tags. ### POST /neos/mcp/publishChanges Publish all pending changes to live. Parameter: `workspace` (default: `mcp`). ### Entity endpoints All at `/neos/mcp/entity/`, using Bearer token auth: | Endpoint | Method | Description | |----------|--------|-------------| | `listentities` | GET | Discover all exposed entities with schemas | | `list` | POST | List/filter entities | | `show` | POST | Get single entity by UUID | | `create` | POST | Create new entity | | `update` | POST | Update entity properties | | `delete` | POST | Delete entity | | `execute` | POST | Run a named action |

Architecture

Internal components | Component | Purpose | |-----------|---------| | `McpBridgeController` | REST API endpoints for all content operations | | `ApiTokenProvider` | Flow security authentication provider (Bearer token to Neos roles) | | `PreviewTokenMiddleware` | HTTP middleware that activates workspace preview from `?_mcpPreview=` tokens | | `PreviewTokenService` | Singleton holding the active preview workspace for the current request | | `WorkspacePreviewAspect` | AOP aspect that switches ContentRepository context to the preview workspace | | `ReviewStatusService` | Tracks MCP changes, creates changelog entries, clears on approval | | `ReviewStatusNodeInfoAspect` | Injects review status into Neos UI tree node data | ### Preview mechanism 1. `PreviewTokenMiddleware` reads the `_mcpPreview` query parameter 2. Validates the token against cache (24h TTL) 3. Activates the preview workspace via `PreviewTokenService` 4. `WorkspacePreviewAspect` intercepts `ContextFactory->create()` and switches to the preview workspace 5. The page renders normally — hidden content is **not** shown in previews

License

MIT

All versions of neos-mcp with dependencies

PHP Build Version
Package Version
Requires neos/neos Version ^9.0
neos/flow Version ^9.0
Composer command for our command line client (download client) This client runs in each environment. You don't need a specific PHP version etc. The first 20 API calls are free. Standard composer command

The package upassist/neos-mcp contains the following files

Loading the files please wait ...