‹ BackHN Continuity

Thread

MCP was always a bad idea?

335 points · 331 comments · maharshi365

  1. flohofwoe · · focus · HN ↗
    Correct me if I'm wrong, but an MCP server still make a lot of sense for remote-controlling a UI application (like a game engine editor) which otherwise doesn't have any 'access points' for remote-control right?

    An AmigaOS-style "scripting port" would work just as well, but AFAIK that's essentially what an MCP server is (a socket that implements a discoverable command protocol).

    I would actually love if all applications and services could agree on a standard for scripting / remote-control. If the AI hype is what it takes to get there, then so be it ;)

    1. unleaded · · focus · HN ↗
      Every few years we're all doomed to reinvent COM again.
Open on Hacker News to reply ↗

Unofficial Hacker News client; not affiliated with Y Combinator.