←back to thread

MCP in LM Studio

(lmstudio.ai)
225 points yags | 2 comments | | HN request time: 0.001s | source
Show context
minimaxir ◴[] No.44380112[source]
LM Studio has quickly become the best way to run local LLMs on an Apple Silicon Mac: no offense to vllm/ollama and other terminal-based approaches, but LLMs have many levers for tweaking output and sometimes you need a UI to manage it. Now that LM Studio supports MLX models, it's one of the most efficient too.

I'm not bullish on MCP, but at the least this approach gives a good way to experiment with it for free.

replies(4): >>44380220 #>>44380533 #>>44380699 #>>44381188 #
chisleu ◴[] No.44380699[source]
> I'm not bullish on MCP

You gotta help me out. What do you see holding it back?

replies(1): >>44381024 #
minimaxir ◴[] No.44381024[source]
tl;dr the current hype around it is a solution looking for a problem and at a high level, it's just a rebrand of the Tools paradigm.
replies(1): >>44381099 #
mhast ◴[] No.44381099[source]
It's "Tools as a service", so it's really trying to make tool calling easier to use.
replies(1): >>44382200 #
ijk ◴[] No.44382200{3}[source]
Near as I can tell it's supposed to make calling other people's tools easier. But I don't want to spin up an entire server to invoke a calculator. So far it seems to make building my own local tools harder, unless there's some guidebook I'm missing.
replies(2): >>44382667 #>>44384088 #
1. cchance ◴[] No.44384088{4}[source]
Your not spinning up a whole server lol, most MCP's can be run locally, and talked to over stdio, like their just apps that the LLM can call, what they talk to or do is up to the MCP writer, its easier to have a MCP that communicates what it can do and handles the back and forth, than writing a non-standard middleware to handle say calls to an API or handle using applescript, or vmware or something else...
replies(1): >>44385222 #
2. ijk ◴[] No.44385222[source]
I wish the documentation was clearer on that point; I went looking through their site and didn't see any examples that weren't oversimplified REST API calls. I imagine they might have updated it since then, or I missed something.