Db Mcp

Created By
tirthraj07a year ago
Custom made MCP Server for Popular databases (Currently Supporting MYSQL)
Overview

what is Db Mcp?

Db Mcp is a custom-made MCP (Multi-Channel Processing) server designed specifically for popular databases, currently supporting MYSQL, enabling efficient database operations.

how to use Db Mcp?

To use Db Mcp, you need to add the provided configuration to your Claude setup, specifying the command and arguments to run the server.

key features of Db Mcp?

  • Customizable MCP server for MYSQL databases
  • Simplified database operations through a structured command interface
  • Integration with Claude for enhanced processing capabilities

use cases of Db Mcp?

  1. Managing and processing database queries efficiently.
  2. Integrating with applications that require database operations.
  3. Supporting multi-channel processing for various database tasks.

FAQ from Db Mcp?

  • What databases does Db Mcp support?

Currently, Db Mcp supports MYSQL, with potential for future expansions to other databases.

  • How do I configure Db Mcp?

You can configure Db Mcp by adding the specified JSON configuration to your Claude setup.

  • Is Db Mcp open-source?

Yes! Db Mcp is available on GitHub for public use and contributions.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
tirthraj07
Star
0
Language
Python
License
-
Category
databases
Tags

Recommend Servers

View All
Payai X402 Tools

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.

a day ago