MCP Servers

 MCP Servers


MCP (Model Context Protocol) was released by Anthropic as an open standard in November 2024. 


Examples released:

  Google Maps: Local search, details of places, etc.

  Slack: Send and receive messages.

  Memory: Remember things across sessions.

  Time: Time and time zone conversions.

  Puppeteer: Interact with a headless browser and send back HTML and images.

  EverArt: An image generator. Note that MCP is not limited to text at all.


Beginning of an open AI ecosystem


Benefits:

  0) The input and output are text.

  1) Open standards extensibility so Claude, Cline, Gemini, etc. can use what I have built.

  2) The power of integration and chaining:

    With MCP, the host gets results from one MCP server, and feeds to another 

MCP server; it can get results from multiple MCP servers and combine them. 

  Example:

a) Listen on Slack for when someone says “Find us a place to go to dinner”

b) Get results from Google Maps and Yelp MCP Servers and mix them to give more comprehensive results

c) Use the Memory MCP server to store and get people’s food preferences (based on said on Slack). 

d) Use the OpenTable MCP server to make a reservation.

e) Post on Slack “Looked at all your food preferences, and nearby restaurants and 

I made a reservation for you at X.”


Tools vs. MCP:

  Tools are targeted at developers who use it in pretty constrained situations. MCP is targeted at users.

  MCP is more dynamic: each user can have their own set of tools that they add and remove.


Questions:

  Should I expose my system as an MCP server?

  Does it give my users a new way to access the capabilities of the AI System?

  Do I even need a user interface any more? Could any MCP host be my new interface?

  Do I want to turn my application into an MCP host to expand its capabilities?


Problems:

  1) Deployment

    Right now adding an MCP server to your host involves editing JSON files, and either running docker or node locally.

  2) Security, auth, etc. 

    It’s still a pain to get auth running correctly.

  3) Dynamic Discovery (so don't need static URL)

     The next step is standardizing a way to discover MCP servers.

Comments

Popular posts from this blog

Upgrading to .NET8 from desktop versions 4.8.X

GHL Chat Bots for Webpage

GHL > Set website so shorter URL address