Configuration

Configure AI Foundation after installation. You need a minimum working setup before connected extensions can use AI.

This section also covers the AI Foundation backend modules used day to day: providers, context, prompts, features, usage, and access control.

Two configuration areas

AI Providers — Path: AI Foundation > AI Providers. API keys, models, and defaults. For managed AI without your own keys, see T3Planet Credits.

Extension settings — Translation APIs, Basic Auth, notifications, and MCP switches (including enableMcpServer). Prefer AI Foundation > MCP Server > Advanced for MCP options. These keys live in AI Foundation settings, not the classic TYPO3 Admin Tools > Settings > Extension Configuration form.

Minimum working setup

  1. One AI provider with a valid key and model

  2. Test connection passes

  3. Provider marked Default

  4. (Optional) DeepL or Google keys for translation APIs

  5. (Optional) MCP enabled if you use AI agents

AI Providers (primary)

Path: AI Foundation > AI Providers

Connect at least one provider, set a model, run Test connection, and mark exactly one row as Default.

Full field reference: Provider fields. Guide: AI Providers

Extension settings

AI Foundation stores translation helpers, Basic Auth, notifications, and MCP switches in extension settings (including enableMcpServer). Prefer AI Foundation > MCP Server > Advanced for MCP options.

Where a classic Extension Configuration form is still used for optional keys, open Admin Tools > Settings > Extension Configuration and select ns_t3af.

Translation (optional)

  • deepl_api_key — DeepL translation

  • google_api_key — Google translation

  • defaultModelForTranslation — Default translation model

OpenAI usage statistics (optional)

  • openai_admin_api_key — Organization usage charts (not the chat API key)

HTTP Basic Auth (optional)

  • basicAuthEnabled — Enable helper

  • basicAuthUsername — Username

  • basicAuthPassword — Password

MCP Server

  • enableMcpServer — Master switch (default: on)

  • mcpBasePath — HTTP endpoint (default: /mcp)

  • requireAuth — Require login (default: on)

  • accessTokenLifetime — OAuth token TTL

Full guide: MCP Server

Per-feature providers

Path: AI Foundation > AI Features

Override the default provider per task: SEO, Pages, Content, Translation.

See AI Features.

Security checklist

  • Limit backend admin access

  • Use HTTPS in production

  • Rotate API keys every 90 days

  • Enable AI Permissions for large teams

  • Never store keys in Git or email

When to reconfigure

  • After key rotation — run Test connection again

  • When adding a new child extension — check AI Features

  • Before enabling MCP in production — read MCP Server security section

  • After OSS license key renewal — confirm the key is still valid