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.

TYPO3 CMS MCP Server for Google ADK 10 tools — connect in under 2 minutes

Name: TYPO3 CMS
Availability: InStock
Author: Vinkius

google.github.io/adk-docs/tools/mcp-tools

Built by Vinkius GDPR 10 Tools SDK

Google Agent Development Kit (ADK) is Google's framework for building production AI agents. Add TYPO3 CMS as an MCP tool provider through Vinkius and your ADK agents can call every tool with full schema introspection.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

python

from google.adk.agents import Agent
from google.adk.tools.mcp_tool import McpToolset
from google.adk.tools.mcp_tool.mcp_session_manager import (
    StreamableHTTPConnectionParams,
)

# Your Vinkius token. get it at cloud.vinkius.com
mcp_tools = McpToolset(
    connection_params=StreamableHTTPConnectionParams(
        url="https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp",
    )
)

agent = Agent(
    model="gemini-2.5-pro",
    name="typo3_cms_agent",
    instruction=(
        "You help users interact with TYPO3 CMS "
        "using 10 available tools."
    ),
    tools=[mcp_tools],
)

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About TYPO3 CMS MCP Server

Connect your TYPO3 CMS backend to any AI agent and take full enterprise control over global content operations mapping, backend Extbase entity tracking, and site hierarchy inspection.

Google ADK natively supports TYPO3 CMS as an MCP tool provider. declare Vinkius Edge URL and the framework handles discovery, validation, and execution automatically. Combine 10 tools with Gemini's long-context reasoning for complex multi-tool workflows, with production-ready session management and evaluation built in.

What you can do

Page Structuring — Query an entire hierarchical navigation mesh grabbing exact IDs to isolate sub-folder content via the API organically
Extbase Data Entry — Perform high-volume CRUD patterns by instantiating new raw custom JSON configurations mapped flawlessly onto defined backend tables
Global Constant Audit — Ping initial states tracking configurations directly looking through the system Constants to bypass heavy configuration modules
Direct Node Removal — Programmatically obliterate or forcefully mutate an outdated content record via native endpoint requests securely

The TYPO3 CMS MCP Server exposes 10 tools through the Vinkius. Connect it to Google ADK in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect TYPO3 CMS to Google ADK via MCP

Follow these steps to integrate the TYPO3 CMS MCP Server with Google ADK.

Install Google ADK

Run pip install google-adk

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token

Create the agent

Save the code above and integrate into your ADK workflow

Explore tools

The agent will discover 10 tools from TYPO3 CMS via MCP

Why Use Google ADK with the TYPO3 CMS MCP Server

Google ADK provides unique advantages when paired with TYPO3 CMS through the Model Context Protocol.

Google ADK natively supports MCP tool servers. declare a tool provider and the framework handles discovery, validation, and execution

Built on Gemini models, ADK provides long-context reasoning ideal for complex multi-tool workflows with TYPO3 CMS

Production-ready features like session management, evaluation, and deployment come built-in. not bolted on

Seamless integration with Google Cloud services means you can combine TYPO3 CMS tools with BigQuery, Vertex AI, and Cloud Functions

TYPO3 CMS + Google ADK Use Cases

Practical scenarios where Google ADK combined with the TYPO3 CMS MCP Server delivers measurable value.

Enterprise data agents: ADK agents query TYPO3 CMS and cross-reference results with internal databases for comprehensive analysis

Multi-modal workflows: combine TYPO3 CMS tool responses with Gemini's vision and language capabilities in a single agent

Automated compliance checks: schedule ADK agents to query TYPO3 CMS regularly and flag policy violations or configuration drift

Internal tool platforms: build self-service agent platforms where teams connect their own MCP servers including TYPO3 CMS

TYPO3 CMS MCP Tools for Google ADK (10)

These 10 tools become available when you connect TYPO3 CMS to Google ADK via MCP:

create_cms_entity

Provide the entity name and data as a JSON object. Creates a new TYPO3 Extbase entity or content element

delete_cms_entity

This action is irreversible. Permanently deletes a TYPO3 record

get_initial_boot

Retrieves global configuration and root page schema from TYPO3

get_navigation_tree

Retrieves the hierarchical navigation menu starting from a page

get_rendered_page

Provide a numeric ID or canonical path. Retrieves a structured representation of a rendered TYPO3 page

get_single_record

Retrieves a single TYPO3 record by ID

list_backend_records

Provide the entity name and optional query parameters. Lists records for a specific TYPO3 entity or route

list_typoscript_globals

Lists global TypoScript settings and constants

ping_rest_api

Verifies connectivity to the TYPO3 REST API

update_cms_entity

Provide entity name, record ID, and JSON updates. Updates fields of an existing TYPO3 record

Example Prompts for TYPO3 CMS in Google ADK

Ready-to-use prompts you can give your Google ADK agent to start working with TYPO3 CMS immediately.

"Can you check the current initial boot configuration of our TYPO3 project?"

"List standard backend records available on the custom entity table 'tx_myext_domain_model_item'."

"Permanently delete the CMS entity under ID 644 on 'pages'."

Troubleshooting TYPO3 CMS MCP Server with Google ADK

Common issues when connecting TYPO3 CMS to Google ADK through the Vinkius, and how to resolve them.

McpToolset not found

Update: pip install --upgrade google-adk

TYPO3 CMS + Google ADK FAQ

Common questions about integrating TYPO3 CMS MCP Server with Google ADK.

How does Google ADK connect to MCP servers?

Import the MCP toolset class and pass the server URL. ADK discovers and registers all tools automatically, making them available to your agent's tool-use loop.

Can ADK agents use multiple MCP servers?

Yes. Declare multiple MCP tool providers in your agent configuration. ADK merges all tool schemas and the agent can call tools from any server in a single turn.

Which Gemini models work best with MCP tools?

Gemini 2.0 Flash and Pro models both support function calling required for MCP tools. Flash is recommended for latency-sensitive use cases, Pro for complex reasoning.