Skip to main content

Feature request: MCP server for programmatic/AI access to Moviebase

Features & Bugs

Hi,

I'm a long-time watchlist app user (recently switched to Moviebase) and wanted to suggest a feature that I think would set the app apart: exposing an MCP (Model Context Protocol) server alongside the existing integrations.

Context: MCP is an open protocol (originally from Anthropic, now adopted more broadly) that lets AI assistants call a defined set of tools against an app's API - e.g. list_watchlist, add_to_list, update_rating, sync_lists - instead of requiring users to manually export/import data or scrape web pages. Several productivity and media tools (Notion, Todoist, Spotify) already ship MCP servers for this reason.

For Moviebase specifically, this would solve a real pain point: right now, syncing or reconciling lists across services (e.g. a JustWatch shared list vs. a Moviebase list) requires manual copy-pasting, since there's no clean API/export path an AI assistant can reliably parse. A thin MCP wrapper around your existing backend (even read-only to start: list/search/get-details) would let users manage their watchlists conversationally through any MCP-compatible AI assistant.

Given Trakt's existing API, I imagine most of the groundwork (auth, data model) may already exist - the main lift would be the MCP tool definitions and a hosted endpoint.

Happy to be a test user if this is ever on your roadmap. Thanks for building Moviebase - it's a great piece of software.

Best,

Lech

Posted by Lech Ambrzykowski ·
1 comment

Log in to comment and vote

Comments1

  • Lech Ambrzykowski

    •

    Jul 15

    Hi again,

    Quick follow-up to correct something in my earlier message: I wrote "given Trakt's existing API," which wrongly implies Moviebase depends fully on Trakt for its data layer. I chose not to use Trakt sync at all, and I understand Moviebase can run independently of it. So the groundwork for an MCP server would be your own backend, not Trakt's.

    On that note - if you're already moving toward a fully independent, in-house backend (rather than leaning on Trakt), I think that's a strong direction regardless of the MCP idea. As a European app built on your own data layer, it gives users a genuine alternative to US-based ecosystems, which I suspect matters to a growing share of your user base.

    Thanks again for considering the feature request.

    Best,

    Lech