Claude-LMStudio-Bridge

Created By
infinitimelessa year ago
A bridge MCP server that allows Claude to communicate with locally running LLM models via LM Studio
Overview

what is Claude-LMStudio-Bridge?

Claude-LMStudio-Bridge is a Model Control Protocol (MCP) server that facilitates communication between Claude and locally running LLM models via LM Studio.

how to use Claude-LMStudio-Bridge?

To use the bridge, clone the repository, set up a virtual environment, install the required packages, and run the bridge server while ensuring LM Studio is running locally with your preferred model loaded.

key features of Claude-LMStudio-Bridge?

  • Enables Claude to send prompts to local models and receive responses.
  • Allows comparison of Claude's responses with other models.
  • Facilitates access to specialized local models for specific tasks.
  • Supports running queries locally, keeping sensitive data secure.

use cases of Claude-LMStudio-Bridge?

  1. Comparing responses from Claude and other LLM models.
  2. Utilizing local models for specific tasks without API limitations.
  3. Keeping sensitive queries local to ensure privacy.

FAQ from Claude-LMStudio-Bridge?

  • What are the prerequisites for using the bridge?

You need Python 3.8+, Anthropic Claude with MCP capability, and LM Studio running locally with loaded models.

  • How do I start the bridge server?

Run the command python lmstudio_bridge.py after setting up your environment and ensuring LM Studio is running.

  • Can I customize the connection settings?

Yes, you can modify the LMSTUDIO_API_BASE variable in lmstudio_bridge.py to change the connection port.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
infinitimeless
Star
0
Language
Python
License
MIT license

Recommend Servers

View All
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

2 days ago
Payai X402 Tools

16 hours ago
Payai X402 Tools

16 hours ago
Payai X402 Tools

16 hours ago
Tavily Mcp
@tavily-ai

JavaScript
a year ago