mcp // forged in the north · streamable-http · stateless

typo3-docs

Official, up-to-date TYPO3 documentation for your AI assistant: TYPO3 Explained, TCA, TypoScript, Fluid ViewHelpers, Content Blocks, Core changelog and more. Re-indexed from GitHub every 6h.

$ https://typo3-docs.vps.fullhaus.dev/mcp ● synced 2026-10-23 08:19 UTC

connect

~/setup

Run once in a terminal. --scope user makes it available in all projects.

claude mcp add --transport http --scope user typo3-docs https://typo3-docs.vps.fullhaus.dev/mcp

Check with claude mcp list or /mcp inside a session.

Open Settings → Connectors → Add custom connector, enter the name TYPO3 Docs and this URL. Enable the connector in a chat via the tools menu.

https://typo3-docs.vps.fullhaus.dev/mcp

Run once, or add the block below to ~/.codex/config.toml.

codex mcp add typo3-docs --url https://typo3-docs.vps.fullhaus.dev/mcp

# ~/.codex/config.toml
[mcp_servers.typo3-docs]
url = "https://typo3-docs.vps.fullhaus.dev/mcp"

Check with codex mcp list.

Create .vscode/mcp.json in your project (or run MCP: Add Server… → HTTP from the command palette). Then use Copilot Chat in Agent mode; the tools appear in the tools picker.

{
  "servers": {
    "typo3-docs": {
      "type": "http",
      "url": "https://typo3-docs.vps.fullhaus.dev/mcp"
    }
  }
}

Open Copilot Chat, switch to Agent mode, click the tools icon → Add More Tools…. This opens mcp.json; add the server and save.

{
  "servers": {
    "typo3-docs": {
      "type": "http",
      "url": "https://typo3-docs.vps.fullhaus.dev/mcp"
    }
  }
}

Open Settings → Tools → AI Assistant → Model Context Protocol (MCP), click Add, choose As JSON and paste:

{
  "mcpServers": {
    "typo3-docs": {
      "url": "https://typo3-docs.vps.fullhaus.dev/mcp"
    }
  }
}

Add to ~/.cursor/mcp.json (global) or .cursor/mcp.json (project).

{
  "mcpServers": {
    "typo3-docs": {
      "url": "https://typo3-docs.vps.fullhaus.dev/mcp"
    }
  }
}

Add to ~/.codeium/windsurf/mcp_config.json and refresh the MCP servers in Cascade.

{
  "mcpServers": {
    "typo3-docs": {
      "serverUrl": "https://typo3-docs.vps.fullhaus.dev/mcp"
    }
  }
}

Run once, or add the server to ~/.gemini/settings.json.

gemini mcp add --transport http typo3-docs https://typo3-docs.vps.fullhaus.dev/mcp

// ~/.gemini/settings.json
{
  "mcpServers": {
    "typo3-docs": {
      "httpUrl": "https://typo3-docs.vps.fullhaus.dev/mcp"
    }
  }
}

Any MCP client with Streamable HTTP support works. The server is stateless and needs no authentication.

https://typo3-docs.vps.fullhaus.dev/mcp

use

Just ask. The assistant searches the docs and answers with links to docs.typo3.org. Mention your TYPO3 version; default is 14.3.

Which TCA renderType do I need for a multi-select with two lists in TYPO3 14?
Show me how to register a PSR-14 event listener in TYPO3 13.4.
What breaking changes affect TypoScriptFrontendController in v14?
Explain all arguments of <f:link.page> and give an example with additionalParams.
Build a Content Block for a teaser with headline, image and link.
What does TYPO3 exception 1476107295 mean and how do I fix it?

recipes

Longer prompts for bigger jobs. Copy, adjust the versions and paste into your agent.

Project housekeepingAudit a TYPO3 project against the docs for its version and fix deprecated or outdated code.

Do a housekeeping pass on this TYPO3 project. Use the typo3-docs MCP server for every check and do not rely on memory for TYPO3 APIs.

1. Read composer.json and detect the installed TYPO3 version (typo3/cms-core) and PHP version. Use that version for all typo3-docs searches.
2. Inventory the custom extensions (packages/, local/ or typo3conf/ext/): composer.json, ext_emconf.php, ext_localconf.php, ext_tables.php, Configuration/ (TCA, Services.yaml, Sets, TypoScript, TSconfig), Classes/ and Resources/Private/ (Fluid templates).
3. Check each area against the docs for this version:
   - deprecated or removed APIs, hooks and classes -> search sources ["changelog"] (Deprecation and Breaking entries) and name the replacement
   - TCA: outdated eval/renderType/type usage, missing or obsolete ctrl settings -> sources ["tca"]
   - TypoScript/TSconfig: obsolete properties, conditions, includes; site sets instead of static templates -> sources ["typoscript", "coreapi"]
   - Fluid: unknown or deprecated ViewHelpers and arguments -> sources ["viewhelper", "fluid"]
   - hooks/XCLASS that should be PSR-14 events, ext_localconf/ext_tables registrations that moved to Configuration/ files, Services.yaml/DI best practices -> sources ["coreapi"]
4. Report the findings as a table: file, problem, docs link, suggested fix, effort (S/M/L).
5. Wait for my go, then fix the findings in small, reviewable steps. Run the existing tests and linters after each step.

TYPO3 major upgradePlan and carry out an upgrade, for example from 13.4 LTS to 14.3 LTS, based on the changelog.

Upgrade this TYPO3 project from 13.4 to 14.3. Use the typo3-docs MCP server for every decision and do not rely on memory. Search the changelog with sources ["changelog"] and version "14.3", and look up the new APIs with version "14.3".

1. Analyse the current state: composer.json (TYPO3, PHP and third-party extension constraints), custom extensions, site configuration, TypoScript, TCA and Fluid templates.
2. Check the system requirements of the target version (PHP, database, Composer) in the docs and list any third-party extensions that are not yet compatible.
3. Go through all Breaking and Deprecation changelog entries from 14.0 to 14.3. For each entry that affects this codebase (search the code for the classes, methods, hooks, TCA options or TypoScript properties it names), note the file, the change, the migration from the docs and the docs link.
4. Write an upgrade plan ordered by dependency: composer constraints, PHP code, TCA, TypoScript/TSconfig, Fluid, then database migrations and upgrade wizards. Mark the steps that Rector or Fractor can automate.
5. After my approval, carry out the plan step by step. Run composer update, the tests and linters after each step, and report anything that needs manual testing in the backend or frontend.

always on

Drop this into CLAUDE.md, AGENTS.md or .github/copilot-instructions.md:

## TYPO3 documentation

Use the `typo3-docs` MCP server (https://typo3-docs.vps.fullhaus.dev/mcp) for every TYPO3 question (TCA, TypoScript, Fluid,
Extbase, site sets, events, Content Blocks, ...). Do not rely on memory for TYPO3 APIs.

- Pass the project's TYPO3 version (see `typo3/cms-core` in composer.json), e.g. "14.3" or "13.4".
- Search with `search_typo3_docs`, then read the relevant hit with `read_typo3_doc`.
- Before upgrading or using an API, check `sources: ["changelog"]` for breaking changes and deprecations.

tools

search_typo3_docsFull-text search. Filters: version (14.3, 13.4, main) and sources (e.g. tca, changelog, sysext:form).
read_typo3_docRead a section by id, or a whole page with full_page: true. Code examples, properties and ViewHelper arguments are included.
browse_typo3_docsList the pages of a source, optionally by path prefix.
list_typo3_doc_sourcesShow all sources, versions and when the index was last updated.

sources

contentandmarketingmain
contentblocksmain
contributionmain
changelog14.3, 13.4, main
coreapi14.3, 13.4, main
editors14.3, 13.4, main
exceptionsmain
fluidmain
frontendlocalization14.3, 13.4, main
gettingstarted14.3, 13.4, main
howtodocumentmain
sitepackage14.3, 13.4, main
tca14.3, 13.4, main
typoscript14.3, 13.4, main
viewhelper14.3, 13.4, main

sysext:* adminpanel · core · dashboard · felogin · fluid_styled_content · form · impexp · indexed_search · linkvalidator · lowlevel · reactions · recycler · redirects · reports · rte_ckeditor · scheduler · seo · styleguide · sys_note · theme_camino · webhooks · workspaces