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
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.

8 hours ago