Webflow MCP Pack
Free
Nothing to run from here
Neos is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
Open Installation—
p95 latency
—
call success
local
runs on your machine
—
calls last 7d
What it does
MCP server for Neos CMS — connects AI assistants to any UpAssist.Neos.Mcp bridge
Quickstart
# 1 — run it from where its publisher ships it
npx -y @upassist/neos-mcp
# 2 — ask your agent something
> MCP server for Neos CMS — connects AI assistants to any UpAssist.Neos.Mcp bridge
Neos is free: there is no plan to choose, no cap to set and nothing that can bill you.
Publishernot claimed
UPAll 1 server
@upassist1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts Neos as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. It is scanned, signed and pinned to the version you choose — read the surface before you approve it.
Claude Codedeclared by this listing
This is a public server: you run it yourself and this marketplace is not in the path. Claude Code registers it in one command.
claude mcp add neos-mcp -- npx -y @upassist/neos-mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free to install, and it runs from its publisher’s own package: no account, no key, no card.
What it writes
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
What you approve
23 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Create a new content element inside a page\
Takes no parameters.
Example callreturns →
Create a new page (document node) as a child of a parent page.
Takes no parameters.
Example callreturns →
Mark a content node as removed in the mcp workspace. The deletion is staged and will only go live after neos_publish_changes is called.
Takes no parameters.
Example callreturns →
Discover all Doctrine entities exposed via MCP. Returns entity schemas with fields, filters, and available actions. Call this first before using other entity tools.
Takes no parameters.
Example callreturns →
List entities from a custom Doctrine table. Use neos_entity_discover first to see available entities and their filters.
Takes no parameters.
Example callreturns →
Get a single entity by its UUID identifier.
Takes no parameters.
Example callreturns →
Create a new entity. Use neos_entity_discover to see required fields and their types. For markdown fields, pass raw markdown text.
Takes no parameters.
Example callreturns →
Update an existing entity. Only pass the fields you want to change.
Takes no parameters.
Example callreturns →
Delete an entity by its UUID.
Takes no parameters.
Example callreturns →
Execute a named action on an entity (e.g. publish, archive, unpublish). Use neos_entity_discover to see available actions.
Takes no parameters.
Example callreturns →
Get all properties of a document node (page) without its content nodes. Use this for SEO fields, meta data, and other document-level properties.
Takes no parameters.
Example callreturns →
Get all content nodes on a specific page with their properties. Call neos_get_site_context first if you have not already done so this session.
Takes no parameters.
Example callreturns →
Get the site context: site name, available content NodeTypes with their properties, current page tree, and editorial workflow instructions. Always call this first at the start of any Neos content editing session.
Takes no parameters.
Example callreturns →
List assets (images, documents, etc.) from the Neos Media Manager. Filter by media type or tag. Returns identifier, title, filename, mediaType, fileSize, tags, and collections.
Takes no parameters.
Example callreturns →
List all available tags in the Neos Media Manager. Use these tags to filter assets with neos_list_assets.
Takes no parameters.
Example callreturns →
List available content node types with their property schemas. Useful to know which types and properties are available before creating or updating nodes.
Takes no parameters.
Example callreturns →
List all document nodes (pages) in the Neos CMS site as a flat tree with paths and titles.
Takes no parameters.
Example callreturns →
List all content changes staged in the MCP workspace that have not yet been published to live. Call this before neos_publish_changes to review what will go live.
Takes no parameters.
Example callreturns →
Reorder or reparent a page or content node.
Takes no parameters.
Example callreturns →
Publish all pending changes from the mcp workspace to live. This is irreversible. Always call neos_list_pending_changes first and confirm with the user before publishing.
Takes no parameters.
Example callreturns →
Restart this Neos MCP server. Use after the MCP bridge code or MCP client has been rebuilt to pick up changes.
Takes no parameters.
Example callreturns →
Idempotently create the shared MCP review workspace. Call this once before making any content changes if the workspace does not exist yet.
Takes no parameters.
Example callreturns →
Update a single property on an existing content node. Call neos_get_site_context first if you have not already done so this session. Always writes to the mcp workspace.
Takes no parameters.
Example callreturns →
Freeyour plan
$0 forever
- Every tool, no call limit
- No card, no account needed
- Source published under a licence you can read
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because nothing bills
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable. Neos costs nothing to install and nothing to call, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: $8.42
$16.58 left
ATrust score 92 / 100
Release 1.0.0 · scanned 26 Aug 2026
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score92
Findings1 threat · 1 capability
Capabilityhigh
Coveragesource
Verificationnone
Surface digestd9ced910518b813efffd00b686c5fab27a49b1d6dbf31f2df234bdce905899a1
Score vectorthreat 100 → client 92
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | high | capability blast radius (high) — client exposure if the model is manipulated | −6 |
| verification-discount | none | publisher verification (unlinked) — no provenance/repo link, but the shipped source was fully read | −2 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tool surfaceread
Implementation sourceread
Package metadataread
Live transportnot available
Tools were statically extracted from the published source (24 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. high is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| neos_create_content_node | no tags | |
| neos_create_document_node | no tags | |
| neos_delete_node | no tags | |
| neos_entity_discover | no tags | |
| neos_entity_list | no tags | |
| neos_entity_show | no tags | |
| neos_entity_create | no tags | |
| neos_entity_update | no tags | |
| neos_entity_delete | no tags | |
| neos_entity_action | no tags | |
| neos_get_document_properties | no tags | |
| neos_get_page_content | untrusted-input | |
| neos_get_preview_url | no tags | |
| neos_get_site_context | no tags | |
| neos_list_asset_tags | no tags | |
| neos_list_assets | no tags | |
| neos_list_node_types | no tags | |
| neos_list_pages | no tags | |
| neos_list_pending_changes | no tags | |
| neos_move_node | no tags | |
| neos_publish_changes | no tags | |
| neos_restart | no tags | |
| neos_setup_workspace | no tags | |
| neos_update_node_property | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digestd9ced910518b813e
Scanned2026-08-26
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Pinned to 1.0.0 — the install command below asks for that release. A pin is part of an install, so it is kept for this visit and written down when you install.
1.0.0
undated
installedNo release note was published with this version.
—
no reviews yet
Reviews are earned
Only accounts with at least 50 real tool calls against this server in the last 90 days can post. Ratings are weighted by how much the reviewer actually uses it, and publishers can reply once per review.
Reviews are earned
Writing one takes an account with at least 50 real tool calls against Neos in the last 90 days. That is the whole gate — there is no other way to post, which is why the counts beside each review are worth reading.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes an account with 50 real tool calls against it.