MCP 数据库服务器 (TypeScript)

Created By
cherla year ago
Overview

what is MCP 数据库服务器?

MCP 数据库服务器是一个基于 Model Context Protocol (MCP) 的数据库查询服务器,使用 TypeScript 实现,允许 AI 模型安全地查询关系型数据库,如 MySQL 和 PostgreSQL.

how to use MCP 数据库服务器?

To use the MCP 数据库服务器, clone the repository, install dependencies using cnpm, configure the database connection in the .env file, and then run the server.

key features of MCP 数据库服务器?

  • Supports MySQL and PostgreSQL databases
  • Provides table structure information as resources
  • Supports read-only SQL query execution
  • Ensures query safety using transactions

use cases of MCP 数据库服务器?

  1. Allowing AI models to perform safe database queries.
  2. Providing structured data access for applications.
  3. Facilitating database management and interaction through a secure API.

FAQ from MCP 数据库服务器?

  • What databases are supported?

The server supports both MySQL and PostgreSQL databases.

  • How do I install the server?

You can install it by cloning the repository and running cnpm install.

  • Is it safe to execute queries?

Yes, the server uses transactions to ensure the safety of query execution.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
cherl
Star
0
Language
TypeScript
License
-

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year 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