YugabyteDB MCP Server

Created By
YugabyteDBa year ago
An MCP server implementation for YugabyteDB that allows LLMs to directly interact with your database.
Overview

YugabyteDB MCP Server

Overview

What is YugabyteDB MCP Server?

YugabyteDB is a Model Context Protocol server providing read-only access to YugabyteDB databases. It enables schema inspection and execution of read-only queries, making it ideal for integrating with LLMs such as Claude, Cursor, and Windsurf Editor.

How to Use YugabyteDB MCP Server?

To use the YugabyteDB MCP server, configure it within the Claude Desktop app by adding the necessary parameters to the "mcpServers" section of the claude_desktop_config.json file. Replace the YUGABYTEDB_URL in the configuration with your specific URL.

Example:

{
  "mcpServers": {
    "yugabytedb-mcp": {
      "command": "uv",
      "args": [
        "--directory",
        "/path/to/cloned/yugabytedb-mcp-server/",
        "run",
        "src/server.py"
      ],
      "env": {
        "YUGABYTEDB_URL": "dbname=database_name host=hostname port=5433 user=username password=password load_balance=true"
      }
    }
  }
}

Key Features of YugabyteDB MCP Server

  • Executes read-only SQL queries and returns results as structured JSON.
  • Provides schema inspection for all tables, including row counts and column metadata.
  • Automatically discovers tables for any schema using YugabyteDB's metadata.
  • Built for compatibility with Claude, Cursor, Windsurf, and other MCP clients.
  • Lightweight and easy to run locally using uv.

Use Cases of YugabyteDB MCP Server

  • Quickly exploring schema structure before deeper analysis.
  • Generating reports or summaries through conversational interfaces.
  • Prototyping analytics dashboards from natural language prompts.
  • Integrating with LLMs to perform safe, read-only data exploration over distributed SQL databases like YugabyteDB.

FAQ for YugabyteDB MCP Server

Q: Is YugabyteDB MCP Server suitable for writing data?

No. It provides read-only access, meaning data cannot be modified through this server.

Q: Can I use YugabyteDB MCP Server with other apps?

Yes! While designed for Claude Desktop, it can be integrated into any application that can call its MCP endpoints.

Q: How do I get information for a particular schema?

Information for a particular schema can be accessed by asking Claude to describe that particular schema in the database. If no schema name is provided, public schema is used as the default.

Server Config

{
  "mcpServers": {
    "yugabytedb-mcp": {
      "command": "uv",
      "args": [
        "--directory",
        "/path/to/cloned/yugabytedb-mcp-server/",
        "run",
        "src/server.py"
      ],
      "env": {
        "YUGABYTEDB_URL": "dbname=database_name host=hostname port=5433 user=username password=password load_balance=true"
      }
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
YugabyteDB
Star
-
Language
-
License
-
Category

Recommend Servers

View All
Voyei

6 hours ago
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.

16 hours ago