Configuration

Purpose

This page explains how to configure AI Foundation after installation. You need a minimum working setup before connected extensions can use AI.

Two configuration areas

AI Providers — Path: AI Foundation → AI Providers. API keys, models, defaults, and T3Planet Credits.

Extension Configuration — Path: Admin Tools → Settings → Extension Configuration → ns_t3af. Translation APIs, MCP switches, basic auth, and notifications.

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

  • Title — Friendly label for your team

  • Vendor — OpenAI, Anthropic, Gemini, Azure, Mistral, and others

  • API key — Encrypted after save

  • Model — For example gpt-4o-mini, claude-sonnet-4

  • Default — Exactly one active default provider

  • Enabled — On/off switch per provider

Full guide: AI Providers

Extension Configuration keys

Path: Admin Tools → Settings → Extension Configuration → 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: off)

  • 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 license renewal — verify T3Planet Credits activation