[HN Gopher] Reflections on building with Model Context Protocol
       ___________________________________________________________________
        
       Reflections on building with Model Context Protocol
        
       Author : outlore
       Score  : 26 points
       Date   : 2024-12-14 08:58 UTC (1 days ago)
        
 (HTM) web link (outlore.dev)
 (TXT) w3m dump (outlore.dev)
        
       | outlore wrote:
       | After recently learning about MCP from HN, I started working on
       | some demos. I jotted down my thoughts about my developer
       | experience and potential room for improvement.
        
         | verdverm wrote:
         | > letting servers notify clients that a resource (like a
         | database) was updated
         | 
         | Do you have a link to the spec where they cover this use case?
         | 
         | Why is callback in OpenAPI not sufficient for this?
         | 
         | https://swagger.io/docs/specification/v3_0/callbacks/
        
           | outlore wrote:
           | Sure that would be here https://modelcontextprotocol.io/docs/
           | concepts/resources#cont...
           | 
           | I think OpenAPI callback would certainly work but the client
           | application must support this. For e.g. I don't think ChatGPT
           | supports callbacks (I might be wrong).
           | 
           | Broadly speaking I am agreed with you that OpenAPI can
           | replicate much of the functionality of MCP, but what's
           | missing is the opinionated contract between client and server
           | (similar to LSPs)
        
             | verdverm wrote:
             | > opinionated contract between client and server
             | 
             | That makes it more of a DSL on a protocol (json-rpc) than a
             | protocol itself
             | 
             | If you want to implement notifications without callbacks,
             | you either (1) use an always connected session and pass
             | messages or (2) have the client poll an endpoint
        
       | somnium_sn wrote:
       | Really appreciate the write up. I am one of the authors of MCP
       | and this helps a great deal giving a good overview of where we
       | need to do better.
       | 
       | I was a bit under the water over the last few weeks with talking
       | to people about MCP and just generally a bit overwhelmed about
       | how well it has been received.
       | 
       | I'll take a look at issue88 this week. Thanks so much
        
         | outlore wrote:
         | Thanks so much! Appreciate all that you do. I gave my demo at
         | work and it was really well received. The MCP server was rock
         | solid.
         | 
         | Hope you get some time to rest!
        
       | lmeyerov wrote:
       | How is the community doing authentication & authorization? We're
       | considering how to support in louie.ai, anticipating a large
       | ecosystem of sites supporting it, yet the original spec had
       | essentially TODO for how to do authentication & authorization
       | bindings...
        
       ___________________________________________________________________
       (page generated 2024-12-15 23:01 UTC)