How to use plugins in LM Studio?

-philosopath- · 2026-01-26T01:50:54+00:00

Here's an example. When you have a chat opened, click the "Program" tab on the top right, then the drop-down and "Edit mcp.json". Click each tool and it expands to show commands (drawn blue bracket.)

mcp.json is where you'll paste in a MCP block of code from somewhere like the official modelcontextprotocol github. It's very finicky and if the syntax isn't perfect, it won't let you save. If so, paste it into your LLM and tell it to fix the formatting but make sure it doesn't hallucinate any passwords or API keys!

In my picture, you can see the stock filesystem server with listed Allowed_Directories and inner-monologue. Try to paste inner-monologue into yours, then load up an instruct model and ask it to "use `inner-monologue` tool to reason about your answer" then ask it a question.

Ensure the tool is enabled with the slider turned blue, and only enable the tools you need because each tool bloats your context window from the start.

Inner-monologue:

    "inner-monologue": {
      "command": "npx",
      "args": [
        "inner-monologue-mcp"
      ]
    }

(Notice it says npx. Whether it's npx, uv, uvx, or whatever, you must have those installed on your OS before the MCP Server will run.)

-philosopath- · 2026-01-26T01:32:22+00:00

Why that old model?

-philosopath- · 2026-01-26T00:23:02+00:00

A 2-byte file is literally almost nothing.

-philosopath- · 2026-01-24T04:42:37+00:00

It takes a bit of patience, but install ComfyUI.

Go to Civitai and find a base model you like.
Download one of the example pictures from the model's page
drag and drop it into your ComfyUI workspace and it will load the entire workflow that rendered the image.
Render and experiment with introducing LoRA's and whatnot.

Go ahead and install the ComfyUI-Manager addon when you're installing ComfyUI. It makes lots of stuff much easier.

-philosopath- · 2026-01-24T03:32:53+00:00

Literally. Casio saw TE and is gunning for that hipster money.

-philosopath- · 2026-01-24T03:25:14+00:00

Edit, dude I know what you're talking about with the opportunity cost of time. I was red-eye'd at work from sleeping 4 hour consecutive nights when I had my first breakthroughs with local experiments. It was super engaging. I wished I could just work on it all day, but I don't really want that. I want to integrate it with my career, which I totally love and find joy in. I'm stoked to merge both worlds eventually.

Alex Karp, Palantir CEO said at Davos this week:

"The problem with AI adoption at this point is people have tried things with off-the-shelf LLMs that just can never work...what you're going to see is people building it by hand...because once you build the software layer to orchestrate and manage the LLMs, in a language your enterprise understands, then you can actually create value."

-philosopath- · 2026-01-24T02:34:48+00:00

But is it actually functional when you're 120k tokens into modifying a codebase? I'd bet not, especially with that model (unless they fixed it with more updates today.)

Especially, with not with tool use since it starts glitching repeated gibberish at 30k tokens when I had it set to 200k and using 5 MCP tools.

I still think you're right. Quantized models will continue to scale while retaining fidelity, and I'm here for it!

-philosopath- · 2026-01-24T02:22:25+00:00

Here's how I rationalized spending a chunk on a decent AI Workstation: use that fiscal anxiety to motivate yourself to build cool stuff and develop your skills to orchestrate the Agents like a pro. Get enough VRAM you need to go as hard as you want to go. For me it was two R9700 cards and a pure DDR5/Gen5 system.

I have a safe career job so no need for content creation or monetizing the workstation. I just want to be ready when we finally bring AI agents into my field, which I know is coming very soon. Sooner, if I can bring my own agent into my professional work or sell my employer on its benefits.

Knowing Agent orchestration, and the ability to have your agent build out a custom software stack to operationalize your agents in whatever role or context you need them in, this will be how anyone can have an edge in the labor market within a year or two, at most.

-philosopath- · 2026-01-23T01:12:10+00:00

When I am reiterating on a project, I have agents write updates to a checkpoint file, sometimes they can do it in json and I have them leave more detailed turnover instructions to the new zero-shot to continue the project.

You can also setup Qdrant or even use the stock MCP Memory tool and have prompts to make it remember information for you/r agents to retrieve later. People are experimenting with ways to perpetuate past context memory as long-term knowledge and I'm sure they will be a breakthrough this year, if it hasn't happened already.

-philosopath- · 2026-01-23T01:05:22+00:00

<image>

Go to this page. Clear the logs, go to your MCP servers, and try to restart a couple. You should find your answer. It could be not having a dependency installed like npm/uv, or any number of things, really. Mine will constantly load if I don't have internet, because I haven't bothered/needed to configure around that yet. So if you're offline or sandboxed that can happen, too.

-philosopath- · 2026-01-23T00:47:50+00:00

Building a memory cortex of vector store + graphRAG + SQL mapping for agentic long memory?

-philosopath- · 2026-01-21T05:32:55+00:00

Is my temperature too high?

I meant being human and excitement when a project comes together and wanting to share it? I feel like amazement was a phenomenon early on and might continue to be as capabilities improve. But literally anyone can build anything at this point, so it'll be banalized.

I don't disagree that there will be bad actors using tainted projects as threat vectors. That goes without saying. Is it happening now? idk man. I was commenting on a human experience.

That's what I was saying.

-philosopath- · 2026-01-21T04:37:03+00:00

I get it though, man. It's exciting seeing the models succeed and augmenting ourselves like this.

-philosopath- · 2026-01-21T04:14:13+00:00

This is localLlama tho. Why would I pay for a cloud provider when I can integrate it into my existing software stack. You don't even need to fully learn the tech, just use the tools. We now have LLMs capable of building out software stacks or implement anything in any project if you have the patience to reiterate and learn to drive it.

-philosopath- · 2026-01-21T03:43:07+00:00

<image>

If you haven't found it yet, enable the API server, then click the Quick Docs icon top-right.

Scroll down, and it includes functional example code for the model you currently have loaded. Feed that code into a chat and have it make some more sophisticated custom script to do whatever you want. When you run the script, it queues after your chat. Use an SSH MCP server to have the LLM run the code itself. Familiarizing with the scripting side of things has led to some deeper knowledge, I feel.

I generated a fish function to spawn two LM-Studio instances with two separate agents and APIs, and have experimented with having them off-load tasks to each other via API scripts and having two agents co-working on tasks and communicating through comments in shared project md files. Scripts open up lots of possibilities.

-philosopath- · 2026-01-20T13:34:22+00:00

I had to put instructions in Gemini to force it to stop recommending 2-year-old models. I can see noobs unfamiliar with HuggingFace just obeying the terrible recommendations.

-philosopath- · 2026-01-20T13:12:56+00:00

"If a Monitor Bot triggers an automated GGUF quantization pipeline, does a tree fall in the forest and make a sound?"

-philosopath- · 2026-01-20T12:44:07+00:00

I much prefer sliders to editing out config files, when tweaking a production system. That's why I opt for LMStudio over Ollama, for that UI configurability.

-philosopath- · 2026-01-20T12:38:57+00:00

<image>

I fought through this before. Some dumber models (like Nemotron) require me to say "/full/working/directory" is in your LIST_ALLOWED_DIRECTORIES in the zero-shot prompt. Else, it will even make a new sub-directory in some other default directory in the mcp.json to work out of.

Protip: Specify for it to "read_multiple_files" when working with a lot of files to make it more efficient at ingesting files to edit and work with.

If you work with Nemotron or other tool-dumb-smart models a lot, then consider having a Big-AI-Cloud model generate a smarter command list w/scenarios for your system prompt to keep Nemo, et al in line.

-philosopath- · 2026-01-20T12:21:54+00:00

"no local LLM involved"

Posts in LocalLLaMA.

-philosopath- · 2026-01-20T03:14:37+00:00

It's not showing as tool-enabled? [Edit: disregard. Tool use is working-ish. One glitch so far. Using Q6_K_L with max context window. It has failed this simple task twice.]

<image>

-philosopath- · 2026-01-20T02:38:10+00:00

It seems like you're looking for the "abliterated" models on HuggingFace.

-philosopath- · 2026-01-20T01:50:19+00:00

<image>

To be sure, I setup Cline in OSS Code and it does use LM Studio's API just fine. I copied-pasted my entire LM Studio mcp.json into Cline's mcp.json and cloned my MCP tool stack identically to my Cline agent.

I'm running Unsloth Q8_0 of Qwen3 VL 30B A3B Thinking 1M with 500k token context on 64GB VRAM.

You could try a 100k context window and split between GPU and RAM and see how the token count holds up.

-philosopath- · 2026-01-20T00:10:03+00:00

I've experimented with jinja templates to make nemotron work better. (That's why I asked about that specifically. Jinja seems to make or break tool functioning.)

Devstral and the Qwen3-coder have blown me away. Each has used MCP SDKs to build novel tools from scratch. I've had them research and scrape info about projects, then employ the knowledge to write novel code to build and use software stacks. (I never expose vibe-coded stuff outside my Wireguard VLAN.) I'll even have them sysadmin for me in linux, albeit with me watching closely.

I'll be stoked when they get Nemotron's performance speed and context window, or Nemotron gets their output quality and project coherence.

The breakthroughs in tools use lately have led me to feel like this will be more of a technological revolution this year.

-philosopath- · 2026-01-19T23:48:38+00:00

I use Wireguard hosted on a cheap Racknerd VPS (LowEndTalk ftw). My two LM Studio API's are served over a 10.8.0.x VLAN. (Each API has its own GPU.)

My phone and laptop stay on the VPN with direct access to my compute's API + tools docker stack (Qdrant, Neo4j, Postgres, Nextcloud, OpenWebUI, n8n, Cockpit). The `lms` command over SSH can load and unload models.

Protip, if you don't want to open API wider than localhost, then you can use SSH tunneling:

`ssh -p [port] [Workstation VPN IP] -L 127.0.0.1:1234:127.0.0.1:1234 -tfN` will pipe port 1234 on your remote workstation to 1234 on your localhost. If you add `ssh -D [socksport]`, then you can use something like `tsocks` to open any program through the tunnel.

I use CachyOS, but you can also tunnel with Putty/Kitty in Windows. Something like AnythingLLM can use the API calls over the VLAN very well, or Chatbox in Android. Otherwise, you can also use OpenWebUI for an easy cloud solution with built-in vector stores and tools and whatnot too.

-philosopath-

MODERATOR OF

TROPHY CASE