TYPO3 MCP Development Server

Cursor Setup

USE WHEN user says "cursor setup", "configure Cursor", "set up Cursor rules" for this TYPO3 project. Creates .cursor/rules/ and *.mdc files with t3gen conventions and returns the setup instructions. DO NOT use for configuring other editors or for wiring the in-project TYPO3 backend MCP server (use `setup_typo3_mcp_server`).

T3gen Init

USE WHEN starting AI-supported coding on a TYPO3 project, or when the user says "init t3gen", "set up AI coding", "set up .team/AGENTS.md". Initializes or updates the project for t3gen: sets up .team/AGENTS.md, configures available tools, installs t3gen helper packages. On existing projects run `analyze_project` afterwards. DO NOT use to scaffold a brand-new TYPO3 install (use `setup_typo3_project`).

Setup Typo3 Project

USE WHEN user says "set up a new TYPO3 project", "install TYPO3", "create a TYPO3 site from scratch". Returns setup instructions for a new TYPO3 v13.4 project with DDEV, Composer, TYPO3 Console and a sitepackage. DO NOT use on an existing TYPO3 install (use `analyze_project`, then `add_site_sets` / scaffolding tools).

Add Site Sets

USE WHEN user says "add site sets", "register a site set", "set up Configuration/Sets". Returns instructions for adding TYPO3 v13 site sets to an extension. Requires TYPO3 already installed — run `setup_typo3_project` first if not. DO NOT use for TypoScript-only changes that don't introduce a new set.

Setup Frontend Build

USE WHEN user says "set up frontend build", "add webpack/scss build", "set up the asset pipeline". Returns folder structure, scss/js base config and output setup for a bun + webpack + scss build. Requires a frontend_framework arg: "bootstrap", "tailwind" or "vanilla-css". DO NOT use for backend/PHP tooling (use `setup_typo3_code_quality`).

Create Page Template

USE WHEN user says "create a page template", "add a backend layout", "new page layout". Returns instructions for the page TypoScript object, backend-layout tsconfig, and Fluid layouts/templates/partials. DO NOT use for content elements (use `create_content_element`).

Create Content Element

USE WHEN user says "create a content element", "add a CType", "new CE", "scaffold a content element", or describes a new piece of editable content. Returns instructions for TCA registration, TypoScript, Fluid templates, language labels, b13/container containers and shared config for a TYPO3 v13 sitepackage. DO NOT use to edit an existing CType (edit the files directly) or for a page layout (use `create_page_template`).

Add Slider

USE WHEN user says "add a slider", "add a carousel", "add a swiper". Returns a reusable Fluid partial, a single-slide template, a JS init module and npm setup for a Swiper slider. DO NOT use for a generic content element (use `create_content_element`).

Update Typo3

USE BEFORE drafting any TYPO3 version-upgrade plan. Triggers: "upgrade TYPO3", "update to v12/13/14", "migrate from 11", "prepare TYPO3 update", "clean up deprecations", "modernize this TYPO3 project". Returns a structured task list covering the full upgrade workflow per current TYPO3 conventions. Run `analyze_project` first if the current state is unknown. DO NOT use to apply the upgrade (follow the returned steps with composer) or to inspect runtime config (use `ddev typo3 t3gen:configuration`

Setup Typo3 Code Quality

USE WHEN user says "set up code quality", "add PHPStan/Rector/Fractor/PHP-CS-Fixer", "set up linting/testing", "configure CI checks" for a TYPO3 project (v13–v14). Returns instructions configuring PHPStan, PHP-CS-Fixer, Rector, Fractor, PHPUnit, PHPMD, TypoScript/XLIFF/YAML/JSON lint, parallel-lint and composer-normalize, scoped to the project's custom extensions. Supports fresh setup, extending an existing setup with a new extension, and auditing an existing setup. Backend only — DO NOT use for

Setup Typo3 Mcp Server

USE WHEN user says "install the TYPO3 MCP extension", "set up the backend MCP server", "connect Cursor to the TYPO3 backend". Returns MCP server token setup instructions. Requires ddev_domain, username and password. DO NOT confuse with `cursor_setup` (editor rules) — this wires the in-project TYPO3 backend MCP server.

Analyze Remote Page

USE WHEN user says "analyze this page/URL", "what content elements does <URL> use", "document the structure of this live/staging page". Returns instructions for analyzing a remote page and writing its structure into a Markdown document. Pair with `write_page_structure` to rebuild it in TYPO3. DO NOT use to analyze the local project (use `analyze_project`).

Write Page Structure

USE WHEN user says "build the page structure from this document", "create these pages/content in TYPO3", typically after a structure Markdown exists (e.g. from `analyze_remote_page`). Returns instructions for reading a page-structure Markdown doc and writing it into a TYPO3 project. DO NOT use to author the structure doc itself (use `analyze_remote_page`).

Analyze Project

USE FIRST when entering a TYPO3 project for any non-trivial task (upgrade, audit, scaffolding decision, "what's in here"). Triggers: "analyze this project", "what TYPO3 version", "what extensions", "is X installed", "audit this project", "prepare upgrade". Returns analysis instructions plus a project.md template covering TYPO3/PHP version, core+third-party+custom extensions, sitepackage, frontend build, code-quality toolchain and t3gen state. Prefer over reading composer.json + grepping. DO NOT

Spec Init

USE WHEN user says "set up spec-driven development", "set up specs", "add an AGENTS.md spec workflow". Returns spec-driven-development workflow instructions and an AGENTS.md template. DO NOT use to create an individual spec (use `spec_add`) or search them (use `spec_search`).

Spec Add

USE WHEN user says "write/create a spec for X", "save this requirement/spec". Stores a Markdown spec for the project with an automatic 3072-dim vector embedding, scoped to the authenticated user and organized by project. Call `spec_search` first to avoid duplicates. DO NOT use to modify an existing spec (use `spec_update`).

Spec Update

USE WHEN user says "update the spec for X", "change the spec state", "archive this spec". Updates an existing spec's content/state/archive status (content changes regenerate the vector), scoped to the authenticated user. DO NOT use to create a new spec (use `spec_add`).

Spec Search

USE WHEN user mentions a feature/requirement and you need to check if it's already specified, or asks "what specs exist for X", "do we have a spec about Y", "find the requirements for Z". Supports semantic search, exact spec_id lookup, and project/state filters; returns a Markdown table with similarity scores. Call BEFORE `spec_add`/`spec_update` to avoid duplicates. DO NOT use for general code search (use grep/Grep).