# TYPO3 CMS MCP for AI Agents AI Agent Connect > TYPO3 CMS. This Connector lets your agent handle your CMS backend tasks like updating records, pulling navigation trees, and auditing global constants. Instead of jumping between the terminal and the web UI, you can just tell your agent what content needs changing or what page structure you're looking for. It handles the heavy lifting of backend calls so you don't have to. ## Overview - **Category:** content-management - **Price:** Free - **Endpoint:** https://edge.vinkius.com/vk_preview_MvYCENhvJ4l7rLLr6a8FG3KbDflpyTTNIi802Z4o/ai-agent-connect - **Tags:** cms, content-operations, crud-operations, site-architecture, extbase ## Description You spend way too much time switching between your code editor and the backend just to update a single content node or check a configuration value. It’s a friction-filled loop of copy-pasting IDs and digging through menus. This Connector changes that by giving your agent direct access to your environment. You can describe a content change in plain English, and the agent handles the heavy lifting of constructing the right data payload and hitting the backend endpoints. Whether you're trying to map out a complex navigation mesh or bulk-update entries, you can stay in your primary workspace. Vinkius makes it easy to plug this into your existing workflow so you can stop worrying about the boilerplate of content management. You get to focus on the actual architecture while the agent handles the repetitive tasks of data entry and configuration audits. It’s about moving from manual data entry to high-level intent. ## Tools ### create_cms_entity Creates a new Extbase entity or content element. Just provide the data as a JSON object. ### delete_cms_entity Permanently deletes a TYPO3 record from your backend. Use this only when you're sure the content is no longer needed. ### get_initial_boot Retrieves your global configuration and root page schema. It's great for getting a high-level overview of the site. ### get_navigation_tree Retrieves the hierarchical navigation menu starting from a specific page. Use it to map out your site structure. ### get_rendered_page Retrieves a structured representation of a rendered page. This helps you check for syntax breaks on specific paths. ### get_single_record Retrieves all data for a single record by its ID. Use this to inspect the details of a specific content piece. ### update_cms_entity Updates fields of an existing record using a name and ID. It's the primary way to modify content via natural language. ### ping_rest_api Verifies the connection to your TYPO3 REST API is active. Use this to ensure your credentials and URL are correct. ### list_backend_records Lists records for a specific entity or route. Use this to find specific items without searching through the UI. ### list_typoscript_globals Lists global TypoScript settings and constants. This is the fastest way to audit your system configurations. ## Prompt Examples **Prompt:** ``` Can you check the current initial boot configuration of our TYPO3 project? ``` **Response:** ``` I've pulled the initial boot data. The system is running version v12.4 LTS. I found the core routing mappings and the site language configurations for both English and German. ``` **Prompt:** ``` List standard backend records available on the custom entity table 'tx_myext_domain_model_item'. ``` **Response:** ``` I found 8 entries under that entity. Records #23 and #40 were added recently. Would you like me to look at the specific data for one of those? ``` **Prompt:** ``` Permanently delete the CMS entity under ID 644 on 'pages'. ``` **Response:** ``` Done. I've wiped record ID 644 from the 'pages' entity. It's no longer visible in the backend. ``` ## Capabilities ### Pull navigation trees Get the full hierarchical structure of your site's menu in one request. ### Update content records Modify specific fields in existing records using a provided ID and JSON data. ### Create new entities Instantiate new Extbase records or content elements instantly. ### Audit global settings Check your system constants and TypoScript globals without digging through modules. ### Delete old records Permanently remove outdated content entries from your backend. ### Fetch rendered pages See a structured representation of a rendered page to check for layout breaks. ### List backend items Query specific entities to see what's currently live in the system. ## Use Cases ### Mapping a complex site hierarchy A CMS Engineer needs to see how a new sub-folder is nested. They ask the agent to pull the navigation tree to see the full structure. ### Bulk updating page titles An editor needs to change the titles of 20 different pages. They tell the agent to use update_cms_entity for a list of IDs to batch the changes. ### Debugging a broken route A Web Architect is seeing a blank page. They use get_rendered_page to see the JSON output of that path to find a syntax break. ### Auditing global constants A developer needs to check the site language settings. They use list_typoscript_globals to get the exact values the agent needs to see. ## Benefits - Stop manual navigation by using get_navigation_tree to instantly see the entire site hierarchy without clicking through pages. - Speed up content updates with update_cms_entity, allowing you to change multiple fields at once via a simple natural language request. - Reduce human error during data entry by using create_cms_entity to ensure every new record follows your required data structure. - Audit your system faster with list_typoscript_globals to see all your constants in one place instead of hunting through modules. - Verify site integrity quickly using get_rendered_page to check for syntax breaks on priority pages without manual refreshes. - Clean up your backend easily with delete_cms_entity to remove outdated content records that are cluttering your workspace. ## How It Works The bottom line is you stop manual data entry and start giving direct commands to your content. 1. Connect your TYPO3 backend URL and authorization token to the Connector. 2. Give your agent permission to interact with your content and configuration. 3. Ask for specific changes like 'update the header text for ID 45' or 'list all items in the news category'. ## Frequently Asked Questions **Can the TYPO3 CMS MCP help me update content faster?** Yes, it lets your agent modify specific fields in your records using JSON, so you don't have to do it manually in the dashboard. **How does the TYPO3 CMS MCP handle navigation?** It can pull the full hierarchical navigation menu, making it easy to see your entire site structure at once. **Can I use the TYPO3 CMS MCP to audit my site's constants?** Absolutely. It can list all your global TypoScript settings and constants so you can check them instantly. **Does the TYPO3 CMS MCP support Extbase entities?** Yes, it includes tools to create and list records for your custom Extbase entities. **Can the TYPO3 CMS MCP help with debugging rendered pages?** It can fetch a structured representation of a rendered page, which helps you find syntax breaks or layout issues quickly. **Is it safe to delete records with the TYPO3 CMS MCP?** It can permanently delete records, but it's designed so you can first list and inspect them to make sure you're targeting the right ID. **Can it retrieve both the navigation tree and single rendered pages autonomously?** Yes. Command the LLM to 'get_navigation_tree' from ID 1, revealing the layout. Finding a curious page, you can instruct it to 'get_rendered_page' supplying its new ID to dissect content instantly. **How does the assistant handle adding complex backend module data like Extbase records?** Using the 'create_cms_entity' endpoint tool, you just tell the AI the physical target database component and pass your JSON. TYPO3 resolves it server-side identically as if inserted from the admin view. **Is there a fast way to verify if my TYPO3 API authentication block is working?** Run a request with the 'ping_rest_api' capability. It triggers a lightweight, zero-payload call directly returning successful metadata from your host validating you have unbridled authorization natively.