Test your TYPO3 MCP server with MCP Inspector

• npx @modelcontextprotocol/inspector@latest --transport http --server-url https://ai-foundation.t3planet.de/mcp
  The command from AI Foundation's setup guide, with our demo's server URL

1. In AI Foundation, MCP Server, Connect, open the setup guide for MCP Inspector and copy the command; it already holds your server URL.
2. Run it in a terminal with Node.js 18 or later and open the Inspector URL it prints.
3. Connect. On our demo the server's OAuth discovery answered 200, but the client registration was refused with 400: the Inspector's redirect URI was not on the allowed list.
4. Under Advanced, Allowed Redirect URIs, add the Inspector's callback, http://localhost:6274/oauth/callback, connect again and authorize in the TYPO3 backend.
5. List the tools and run a read-only one first, such as file_list for a folder, before you connect your assistant.

Shown in Claude; other MCP assistants work too.

The Inspector's request log shows each call with its status code: discovery and registration should both succeed. In the backend, MCP Server, OAuth Tokens lists the token of the Inspector client; revoke it there when you are done.

AI Foundation with its MCP server switched on, Node.js 18 or later, and the Inspector's callback on the allowed redirect list; AI Foundation is free, MCP Inspector is open source.

• We recorded the Inspector's start and the refused registration on our demo. The connected view in the video is an illustration built from a real file_list result on the demo; we did not change the demo's OAuth settings for the video.
• Allowed Redirect URIs takes one URI per line, and a trailing * matches a prefix. An empty list allows any redirect URI, which is wider than most sites want.
• The Inspector's local URL carries a session token. Run it on your own machine and do not share that URL.
• The Inspector talks to your server directly: no assistant vendor sees the data in this test. Once you connect an assistant, what the tools return goes to its vendor.