🌐 MCP Connection Setup

Choose your preferred method to connect MCP clients to this TYPO3 instance.

No workspace configured

All changes made through MCP are staged in a TYPO3 Workspace before publishing. One will be created automatically, but you should create one manually to control permissions and review workflow.

Local/private network detected

{baseUrl} resolves to a private network address. Most remote MCP clients (Claude Desktop, n8n cloud, manus) cannot reach this server from the internet.

What works locally: The MCP Inspector (runs on your machine) and the Local Setup (TYPO3 CLI) tab. The Local Setup (mcp-remote) may also work since mcp-remote runs on your machine.

Connect MCP clients to this TYPO3 instance over the internet using OAuth authentication. This is the recommended method for most use cases.

MCP endpoint status:
{baseUrl}/.well-known/oauth-authorization-server
{baseUrl}/.well-known/oauth-protected-resource
🚀 Claude Desktop Integration

To connect Claude Desktop to this TYPO3 instance:

  1. In Claude Desktop, go to Settings → Integrations
  2. Click "Add Integration"
  3. Enter Integration Name: {siteName}
  4. Paste the Server URL: {baseUrl}/mcp
  5. Claude Desktop will automatically handle OAuth authentication
🔄 n8n Integration

To configure your n8n MCP Client node:

  1. In n8n, add an MCP Client node to your workflow
  2. Set Endpoint to: {baseUrl}/mcp
  3. Set Server Transport to: HTTP Streamable
  4. Set Authentication to: Bearer Auth
  5. Create a token in the Active OAuth Tokens section (e.g. name it "n8n"), create a new credential and paste the token
  6. Select which tools to include or choose "All"
🤖 manus Integration

To configure your manus MCP connection:

  1. In manus, go to Connectors settings and add a connector
  2. Set Server Name to: {siteName}
  3. Set Transport to: HTTP
  4. Set Server URL to: {baseUrl}/mcp
  5. Create a token in the Active OAuth Tokens section (e.g. name it "manus")
  6. Add a custom header Authorization with the value Bearer YOUR_TOKEN (use the token shown at creation)
  7. Save your MCP configuration
🔍 MCP Inspector

Debug and test tools using the official MCP Inspector CLI:

What happens next:

  1. The Inspector UI opens in your browser
  2. All parameters are pre-configured. It's enough to click Connect.
  3. After authorization, you can test all available tools

Note: Requires Node.js to be installed on your system.

🔧 Generic MCP Client Setup

For MCP clients that support OAuth and remote connections:

  1. Configure your client with server URL: {baseUrl}/mcp
  2. Optionally set integration name: {siteName}
  3. Your client should automatically discover OAuth endpoints
  4. During authentication, you'll be redirected to this TYPO3 backend
  5. After authorization, your client will receive secure access tokens

Note: Your MCP client must support OAuth 2.0 and automatic endpoint discovery.

For MCP clients that don't support remote connections natively. The mcp-remote package acts as a local bridge, connecting to this TYPO3 instance on behalf of your MCP client.

Example mcp-remote configuration:

Create a token in the Active OAuth Tokens section (e.g. name it "mcp-remote") and replace YOUR_TOKEN with the plain token shown at creation.

⚠️ Security Note:

The token URL includes your authentication token in the URL. Only use this method when your MCP client doesn't support Authorization headers or when using mcp-remote configurations that require tokens in the URL.

For local development where your MCP client has direct shell access to this TYPO3 installation.

How CLI access works:
  • Direct access: No OAuth needed
  • Local only: Only works when your client has shell access to TYPO3
Important considerations:
  • Long-running process: The CLI server runs continuously and may accumulate memory usage over time. Restart periodically if you notice performance issues.
  • Code changes: Changes to PHP code won't be reflected immediately. You'll need to restart the CLI server to pick up code modifications.

🔑 Active OAuth Tokens

Manage your active OAuth tokens. Each token represents an authorized MCP client connection.

Client Name Created Last Used Expires Actions
{token.client_name} {token.created} {token.last_used} {token.expires}
🔑

No active tokens found.

Click Create Token above to create your first token.

{tool.name}

{tool.description -> f:format.nl2br()}