mariadb-mcp-server

Created By
abel9851a year ago
An mcp server that provides read-only access to MariaDB.
Overview

what is mariadb-mcp-server?

mariadb-mcp-server is an MCP server implementation that provides read-only access to MariaDB, allowing users to retrieve data efficiently.

how to use mariadb-mcp-server?

To use mariadb-mcp-server, set up the database connection environment variables and configure the server according to your system's requirements. Then, run the server using the specified command.

key features of mariadb-mcp-server?

  • Exposes schema list in the database.
  • Executes read-only operations against MariaDB.
  • Supports configuration through environment variables.

use cases of mariadb-mcp-server?

  1. Accessing database schemas for documentation purposes.
  2. Running read-only queries for data analysis.
  3. Integrating with applications that require database access without modification capabilities.

FAQ from mariadb-mcp-server?

  • What is the purpose of mariadb-mcp-server?

It provides a way to access MariaDB data in a read-only manner, ensuring data integrity.

  • How do I install the required dependencies?

You can install the MariaDB Connector/C using Homebrew on macOS with the command: brew install mariadb-connector-c.

  • Can I modify the data using this server?

No, mariadb-mcp-server is designed for read-only access only.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
abel9851
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.

11 hours ago
Voyei

an hour ago