# LMStudio SDKs Projects at AI Tinkerers

> Canonical HTML: https://aitinkerers.org/technologies/lmstudio-sdks
> Markdown URL: https://aitinkerers.org/technologies/lmstudio-sdks.md
> Technology record last updated: 2026-03-31T03:15:00Z
> Generated: 2026-09-23T05:50:32Z

Programmatic access to local Large Language Models (LLMs) via dedicated Python and TypeScript SDKs, featuring OpenAI-compatible APIs and agentic tool-calling.

The LM Studio SDKs provide developers with robust libraries—`lmstudio-python` and `lmstudio-js`—to integrate local LLMs directly into their applications. These SDKs simplify local AI development, offering core functionality like chat completions, text generation, and embeddings through an OpenAI-compatible interface. A key differentiator is the `.act()` API, which enables advanced agent-oriented programming: models autonomously utilize tools and execute multi-step workflows. Developers gain precise control over resource management, including the ability to load and unload models (e.g., Qwen3, Gemma3) as needed, ensuring efficient use of local hardware without complex configuration.

- Official technology site: https://lmstudio.ai/docs/developer
- Public AI Tinkerers demos and talks: 1
- Result page: 1 of 1

## Recent Public Talks and Demos

### [Building a Unified AI Interface: Live Demo of Dolphin MCP's Cross-Provider Tool Orchestration](https://quito.aitinkerers.org/talks/rsvp_N6gp-pwJaUo)

This technical deep-dive demonstrates how Dolphin MCP enables seamless interaction with multiple LLM providers (OpenAI, Anthropic, Ollama, LMStudio) through a unified Model Context Protocol (MCP) architecture. The presentation will feature: Live coding session showing how to build a modular AI application that connects to multiple model providers simultaneously Technical walkthrough of the MCP client implementation, exploring function calling, server discovery, and asynchronous tool execution Interactive demonstration of real-time tool orchestration across different LLM backends, with audience members suggesting queries Code dissection of key components including provider-specific implementations, showing how to handle the differences between OpenAI, Anthropic, Ollama, and LMStudio APIs Architecture analysis of the project's approach to separating concerns between providers, tools, and client interfaces I'll show concrete examples of how Dolphin MCP handles function calling across different providers that implement it differently, including explicit handling for: OpenAI's native function calling Anthropic's tool use format Ollama's function calling implementation LMStudio's unique approach The session will include debugging challenging edge cases in multi-provider environments and demonstrating how to build resilient systems that work even when providers return unexpected responses.

- Event context: AI Tinkerers - Quito Primer Meetup (Abril) — 2025-04-24 — Quito
- Public talk page: https://quito.aitinkerers.org/talks/rsvp_N6gp-pwJaUo

## Related Technologies

- [Anthropic API](https://aitinkerers.org/technologies/anthropic-api) ([Markdown](https://aitinkerers.org/technologies/anthropic-api.md)) — 66 public demos
- [MCP](https://aitinkerers.org/technologies/mcp) ([Markdown](https://aitinkerers.org/technologies/mcp.md)) — 129 public demos
- [Ollama](https://aitinkerers.org/technologies/ollama) ([Markdown](https://aitinkerers.org/technologies/ollama.md)) — 77 public demos
- [OpenAI API](https://aitinkerers.org/technologies/openai-api) ([Markdown](https://aitinkerers.org/technologies/openai-api.md)) — 520 public demos