Ollama
Local model runtimesRun supported models locally and call them through an API. Local and cloud execution are different modes; check which model actually serves each request. Documentation checked; not hands-on tested.
Independent review. IonBin has no partnership with LM Studio and was not paid for this page. Our evaluation is 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.
A desktop interface for local models, document chat and a local API server. Prepare model downloads first and verify any connected tools separately. Documentation checked; not hands-on tested.
Reference entry: listed because workflows on IonBin use it. IonBin has no affiliate or paid relationship with LM Studio.
Model downloads, discovery and updates need connectivity. Once prepared, local inference, document chat and the local server can operate offline. Connected services need their own review. source ↗
Short documents may fit in context; longer ones use retrieval. Compare answers with the original passage and test questions whose answer is absent. source ↗
How LM Studio connects to each AI platform: native connector or MCP, API through code the agent writes, browser control, or file upload.
| Platform | MCP / connector | API (agent-written code) | Browser | Upload / export |
|---|---|---|---|---|
| Claude (incl. Claude Code) | Not documented An MCP client/host is documented; this does not establish that the product exposes an MCP server. | Not documented Claude (incl. Claude Code): Claude Code edits files and runs commands LM Studio publishes an API, but this pairing still needs network, authentication and execution-scope checks. LM Studio API ↗Claude (incl. Claude Code) docs ↗ | No documented route | Not documented Verify which side exports and which imports, supported formats and permissions. LM Studio's recorded upload/import status is yes; Claude (incl. Claude Code)'s file status is yes. These flags do not establish a file-transfer route. LM Studio file docs ↗Claude (incl. Claude Code) file docs ↗ |
| OpenAI Codex | Not documented An MCP client/host is documented; this does not establish that the product exposes an MCP server. | Not documented OpenAI Codex: Edits files and runs commands locally; cloud tasks run in isolated workspaces LM Studio publishes an API, but this pairing still needs network, authentication and execution-scope checks. LM Studio API ↗OpenAI Codex docs ↗ | No documented route | Not documented Verify which side exports and which imports, supported formats and permissions. LM Studio's recorded upload/import status is yes; OpenAI Codex's file status is yes. These flags do not establish a file-transfer route. LM Studio file docs ↗OpenAI Codex file docs ↗ |
| Google Antigravity | Not documented An MCP client/host is documented; this does not establish that the product exposes an MCP server. | Not documented Google Antigravity: Agents edit code and run tasks LM Studio publishes an API, but this pairing still needs network, authentication and execution-scope checks. LM Studio API ↗Google Antigravity docs ↗ | No documented route | Not documented Verify which side exports and which imports, supported formats and permissions. LM Studio's recorded upload/import status is yes; Google Antigravity's file status is yes. These flags do not establish a file-transfer route. LM Studio file docs ↗Google Antigravity file docs ↗ |
Confirmed is reserved for evidence of the specific connection route. The current named integrations include plugins, skills and CLIs, so a named platform alone does not confirm MCP or a native connector. Inferred means each side documents a relevant capability, but no document describes the pairing. Code execution still needs network and credential access; file handling still needs a compatible format and transfer direction. Not documented means the records do not establish the route. IonBin has not tested these pairings. Recorded Oct 18, 2026.
| Level | Status | Detail / source |
|---|---|---|
| Native connector / MCP | To verify | An MCP client/host is documented; this does not establish that the product exposes an MCP server. |
| API / CLI | Yes | Official docs ↗ |
| Browser / manual | No | Browser access is not recorded for this tool. |
| File upload / import | Yes | Official docs ↗ |
Recorded Oct 18, 2026. Setup and plan limits vary; check the vendor's docs. How levels are assigned.
MCP client support is documented. 122 tools in IonBin list an official server; this is a server inventory, not a compatibility list. Check transport, authentication, supported actions and plan requirements for each pairing:
No long-form review yet. Verdict is based on research, not hands-on testing.
Run supported models locally and call them through an API. Local and cloud execution are different modes; check which model actually serves each request. Documentation checked; not hands-on tested.
ElevenLabs is a trademark of its owner. IonBin is an independent publisher and is not affiliated with, sponsored by, or endorsed by ElevenLabs. Product names are used for identification and review purposes only.
With your permission, Google Analytics uses cookies to measure page visits and help us improve IonBin. It stays off until you choose. We do not enable advertising tracking.
You can change this choice anytime below. Turning analytics off reloads open IonBin tabs where analytics is running. Save unfinished form text first. Privacy details.