"Using llama.cpp and Searxng with local models" matching MCP servers:

A local development MCP server that exposes MySQL databases to VSCode and Copilot CLI with read-only SELECT queries and INSERT/UPDATE operations. It provides secure, schema-specific database access for development environments only.

our ChatGPT and Claude chat history in one local SQLite file, imported from their data exports. Read-only tools to search and read past conversations; no network.

Enables local-first personal finance management through deterministic tools for importing, categorizing, and analyzing bank transactions.

Enables agents to inspect and synchronize local macOS QQ data snapshots, with read-only access to contacts, conversations, messages, search, changes, exports, full tables/datasets, media assets, and favorites via MCP tools.

Enables AI assistants to interact with Databricks workspaces, running SQL queries, managing jobs, and exploring schemas via the Model Context Protocol.

Enables AI agents to keep durable long-term memory on the user's own machine, writing sessions and messages into a local SQLite database and retrieving them via keyword, exact, or optional semantic search with surrounding context. Runs entirely offline over stdio, so no cloud service or API key is required to give an agent recall across sessions.

Exposes your local machine's filesystem, git, shell, network, databases, and system to any MCP-compatible LLM client over HTTP.

Local MCP server that exposes fleet telemetry queries as tools for language models, enabling natural language questions about vehicle positions, trips, and alerts. Runs on the operator's machine and returns aggregated results from a SQLite database.

A read-only MCP server that lets AI search and read both sides of a user's own LINE Desktop chat history on macOS using local database snapshots, without needing a LINE Official Account or altering unread state.

A TypeScript MCP server that provides secure, read-only access to a locally hosted MySQL database for AI-agent workflows, with configurable policies and support for multiple MCP clients.

Enables direct interaction with local WordPress development sites through Local by Flywheel database connections. Provides read-only access to WordPress data including posts, users, options, and custom queries for development and analysis.

MCP server providing WP-CLI, MySQL, and filesystem access for Local by Flywheel WordPress sites, enabling direct management without HTTP endpoints.

TypeScript stdio MCP server for operating Docker-based local-ydb deployments from AI coding agents. Supports local and SSH-backed profiles, bootstrap, diagnostics, auth hardening, schema permissions, storage workflows, dump/restore, upgrades, and plan-first mutating operations.

Local-first Garmin data warehouse with an analysis-grade MCP server. Sync once, analyze forever, even when the API is down.

A read-only MCP server that lets LLMs explore and query local SAS datasets (.sas7bdat / .xpt) without Viya, network, or SAS licensing. It exposes tools for listing, metadata inspection, summarization, frequency tables, value-label decoding, paginated reads, DuckDB SQL joins, and cross-dataset variable search.

A read-only MCP server that enables searching and extracting to-dos from local macOS WeChat chat databases. It decrypts and queries local WeChat data without sending messages or modifying databases.

Gives an LLM a secure local workspace where it can write files, execute Python in a locked-down Docker container with no network access, and run read-only SQLite queries. Lets the model run, debug, and fix its own code without risking the host machine.

Exposes local file I/O, a restricted shell whitelist, and SQLite helpers for safe integration with AI clients like Cursor and Claude Desktop.

Enables an AI agent to run 1C queries, evaluate expressions, execute BSL code, and inspect configuration metadata inside a user's open 1C session, exchanging commands and results through a folder in the user's profile without any intermediate gateway. Results can be gated by user confirmation on the 1C form, and write operations are rolled back unless explicitly permitted.

Enables AI agents to query a local PostgreSQL-backed mock financial database, retrieving a user's recent transaction history and flagging transactions that exceed a given spending threshold.