Independent reviews. IonBin has no partnerships with the tools on this page and was not paid for these listings. Our evaluations are our own, based on public documentation and our research. Product names are trademarks of their owners and are used for identification only. How disclosure works.

LM Studio

Local model host · LM Studio

A desktop host for local models, document chat and developer APIs.

What it is

LM Studio runs downloaded models on your computer. It can serve a local API and host MCP connections. Model compatibility, memory requirements and tool permissions depend on the selected setup.

  • Desktop: Local chat and document attachments source ↗
  • Local server: Developer APIs for applications source ↗

What it's best at

  • Try questions against a small local document collection
  • Compare a downloaded model against reviewed examples

How it works

  1. Download a compatible model and prepare dependencies.
  2. Attach a supported document and check answers against the original.
  3. Enable a local API or MCP connection only when the workflow needs it.

Agent, connector and MCP support

MCP / connectors

Yes

Acts as a host for local and remote MCP servers.

docs ↗
Browser control

To verify

A general browser-control capability is not established here.

Runs code

To verify

Generated code is not proof of a built-in execution sandbox.

Works with files

Yes

PDF, DOCX and TXT document attachments are documented.

docs ↗

Ideal use cases

  • Try questions against a small local document collection
  • Compare a downloaded model against reviewed examples

Limits

  • Downloads and updates require network access.
  • Remote tools can send data elsewhere even when model inference is local.
  • Test retrieval quality; local execution does not prevent incorrect answers.

How it pairs with your tools

This platform is not included in the general tool-page connection matrix. Use the specific pairings and sources above; other combinations need separate verification.

Workflows you can run here

Confirmed means the workflow's connection is documented for LM Studio, including a native recipe explicitly scoped to this platform. Inferred means an API step relies on LM Studio running code, with no document naming the pairing. These labels do not mean IonBin has tested the workflow.

In the wiki

Gemma 4Local model runtimes

Sources