MagicMirror Forum
    • Recent
    • Tags
    • Unsolved
    • Solved
    • MagicMirror² Repository
    • Documentation
    • 3rd-Party-Modules
    • Donate
    • Discord
    • Register
    • Login
    A New Chapter for MagicMirror: The Community Takes the Lead
    Read the statement by Michael Teeuw here.

    MagicMirror MCP Server Integration For AI Assistants

    Scheduled Pinned Locked Moved Development
    3 Posts 2 Posters 27 Views 2 Watching
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • R Offline
      Rags
      last edited by

      A Model Context Protocol (MCP) server for controlling MagicMirror² via the MMM-Remote-Control API.
      My first milestone in automating MagicMirror using the AI assistants. (With Help from AI Programming Tools.)
      This lets AI assistants like Claude interact with your smart mirror showing/hiding modules, sending alerts, toggling the display, restarting the mirror, and more. The possibilities are endless, just requires ingenuity.
      Check it Out Here :
      https://github.com/Ragziesoft/magicmirror-mcp

      KristjanESPERANTOK 1 Reply Last reply Reply Quote 1
      • KristjanESPERANTOK Offline
        KristjanESPERANTO Module Developer @Rags
        last edited by

        @Rags Nice! 👏 I also thought about something like this.

        Just out of curiosity: Why are you using an very old version of axios instead of build-in fetch?

        R 1 Reply Last reply Reply Quote 0
        • R Offline
          Rags @KristjanESPERANTO
          last edited by

          @KristjanESPERANTO said:

          Why are you using an very old version of axios instead of build-in fetch?

          You have given me food for thought. There’s no good reason. Axios 1.6.0 is not ancient, but it’s still an unnecessary dependency for what this client does. Many TypeScript libraries were originally written for Node 14/16 environments, so Axios became the default. The repo requires node >= 18, and Node 18 ships with the native fetch API built in. Every single method in client.ts is a simple GET or POST with JSON , exactly what fetch handles natively without any extra package. The only real reason to reach for axios in a Node 18+ project today is if you need interceptors for complex auth flows, automatic retry logic, or upload progress events .
          Axios was chosen for convenience and historical compatibility. However, for a modern Node.js TypeScript MCP server, native fetch is cleaner and preferable. For this project switching to native fetch seems logical. Axios adds more value in complex APIs, but here the benefit is minimal. So i guess, i need to strip it . Thanks, I will try and update ASAP.

          1 Reply Last reply Reply Quote 0

          Hello! It looks like you're interested in this conversation, but you don't have an account yet.

          Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

          With your input, this post could be even better 💗

          Register Login
          • 1 / 1
          • First post
            Last post
          Enjoying MagicMirror? Please consider a donation!
          MagicMirror created by Michael Teeuw.
          Forum managed by Sam, technical setup by Karsten.
          This forum is using NodeBB as its core | Contributors
          Contact | Privacy Policy