mcp-server-mariadb-vector

Created By
DavidRamosSala year ago
MCP server for MariaDB
Overview

What is mcp-server-mariadb-vector?

The mcp-server-mariadb-vector is a server that allows LLM agents to interact with a MariaDB database that supports vector operations, providing a natural language interface for data storage and interaction.

How to use mcp-server-mariadb-vector?

To use the server, clone the repository from GitHub, set up a MariaDB instance with vector support, and run the server either as a Python package or a Docker container.

Key features of mcp-server-mariadb-vector?

  • Vector Store Management: Create, delete, and list vector stores in a MariaDB database.
  • Document Management: Add documents with metadata and perform semantic searches.
  • Embedding Provider: Utilize OpenAI's embedding models for document embedding.

Use cases of mcp-server-mariadb-vector?

  1. Providing context from a knowledge base to LLM agent conversations.
  2. Storing and querying conversations with LLM agents.
  3. Managing vector data for AI applications.

FAQ from mcp-server-mariadb-vector?

  • Can I use this server with any LLM client?

Yes, it is compatible with any MCP client, including Claude Desktop and Cursor.

  • Is there a specific version of MariaDB required?

Yes, a MariaDB instance with version 11.7 or higher is required for vector support.

  • How do I run the server?

You can run it using the command line with uv or as a Docker container.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
DavidRamosSal
Star
0
Language
Python
License
LGPL-2.1 license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

9 hours ago
Alloy

2 days ago