lmstudio-connectors
Related Servers
Alternatives to lmstudio-connectors
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceEnables tool-calling LLMs to search the internet, capture website images, extract webpage text, and more via a local MCP server.15-
- FlicenseNot gradedqualityBmaintenanceMCP server for web scraping using Playwright headless Chromium. It provides tools to fetch webpage screenshots, search article listings, and generate article briefs via local LM Studio models.-
- AlicenseNot gradedqualityCmaintenanceMCP server for web search and content extraction using DuckDuckGo or SearXNG, with Playwright-based fetching and LLM-powered data extraction.139MIT
- AlicenseNot gradedqualityCmaintenanceA fully local MCP server that provides web search via self-hosted SearXNG and page-to-markdown conversion (static and JS-rendered), all aggregated behind a single endpoint for use with AI assistants.MIT
- AlicenseAqualityAmaintenanceLocal MCP server for web search and page extraction, providing clean markdown from URLs, search results, site mapping, and research endpoints without API keys or accounts.5Apache 2.0
- FlicenseNot gradedqualityDmaintenanceMCP server that provides web search scraping from DuckDuckGo (with Mojeek fallback) and URL content fetching as markdown/text or raw HTML.1-
TDQS
Scored across 15 tools
Each tool targets a distinct operation within its connector group, but playwright_cli_open and playwright_cli_goto both involve navigation and could be confused. The two health checks are also similar in purpose but for different subsystems.
All tools follow a snake_case pattern with a connector-specific prefix (web_, yt_, mflux_, playwright_cli_), but the suffix is a mix of verbs and nouns (e.g., yt_info vs yt_download), introducing minor inconsistency.
With 15 tools across several connectors, the count is within the ideal 3-15 range. Each connector has a minimal but useful set (web: 2, yt: 3, mflux: 2, playwright: 6, health: 2), so no tool feels unnecessary.
The server covers the main workflows for each connector: web search and scrape, YouTube metadata/subtitles/download, MFLUX generation and info, and Playwright browser automation with open/goto/snapshot/action/save/close. Some minor gaps exist, such as no YouTube search or no way to list Playwright sessions, but the core lifecycle is covered.