EXT:ns_t3af).
Installation
Composer conflicts with another MCP package T3AF includes an MCP server and conflicts with other MCP server packages such asmarekskopal/typo3-mcp-server and hn/typo3-mcp-server. Remove those packages before installing nitsan/ns-t3af.
Backend module is missing
- Confirm
ns_t3afis active. - Flush all caches.
- Run:
scheduler and workspaces are available. See Installation.
Providers
Provider request or Test connection fails- Confirm the provider row exists and is enabled in T3AF > AI Providers.
- Run Test connection from the provider drawer.
- Check the API key, model ID, and endpoint URL (for custom/OpenAI-compatible rows).
- Confirm outbound HTTPS to the provider API works from the server.
- Review backend logs for entries from T3AF request logging.
- Confirm the default provider matches the feature you expect.
- Confirm the model ID on the provider row.
- Check feature-level provider overrides in T3AF > AI Features.
- Confirm an OpenAI admin/organization key is set where org usage charts are required.
- Clear caches and open T3AF > AI Usage / T3AF > AI Logs again.
- Confirm the dashboard analytics cache is available after
extension:setup.
Configuration
HTTP 401 / 403 when fetching a protected URL If you use the Basic Auth helper in Extension Configuration (ns_t3af):
- Enable
basicAuthEnabled. - Set
basicAuthUsernameandbasicAuthPassword. - Retry the protected URL fetch.
MCP
MCP client cannot connect- Confirm the MCP server is enabled in Extension Configuration.
- Prefer HTTPS on the site base URL.
- For Cursor and similar clients, follow MCP Testing.
- For stdio setups, keep the working directory and user/workspace flags correct.
Report an issue
Include TYPO3 version, PHP version,ns_t3af version, exact error text, and whether MCP is enabled. Submit via Support.