FR: Add secret-path option for MCP HTTP endpoint

[vsheg]

Hi, thanks for the add-on; it’s been very useful

Could you please consider adding support for a “secret path” mode for the HTTP, e.g. serving MCP under http://localhost:3141/secret-string/ → https://example.com/secret-string/, so ChatGPT MCP can connect relatively securely without requiring full OAuth?

The goal isn’t strong security, but rather avoiding exposing a fully unauthenticated MCP endpoint

Best regards

P.S. The headless Anki container is quite promising. It would be incredibly useful as a self-hosted sync server with MCP support

[anatoly314]

Good idea — I'll implement this for people who prefer a self-hosted solution. I'd also like to announce that this addon will soon support full OAuth2 authentication as required by the MCP protocol, with DCR as well. I've already finished developing the tunnel server and will deploy it within a week or two. It will have free and paid tiers. Regarding your note about headless Anki — it will also be provided as a service.

[anatoly314]

Fixed in #12.

Added http_path config option — set it to any string to serve the MCP endpoint under a custom path (e.g., http://localhost:3141/my-path/). Leave empty for default root behavior.

A new release will be published within the next 24 hours.

[vsheg]

It seems to work well, thanks. It would be great if the full copyable (e.g. on click) URL is displayed here:

[anatoly314]

Good idea, I did it. Soon will deploy.