mcp-server-duckdb

Created By
ktanaka101a year ago
A Model Context Protocol (MCP) server implementation for DuckDB, providing database interaction capabilities
Overview

What is mcp-server-duckdb?

The mcp-server-duckdb is a Model Context Protocol (MCP) server implementation for DuckDB, designed to enable seamless database interaction through MCP tools. It supports various database operations, such as querying, creating tables, and inspecting schemas.

How to use mcp-server-duckdb?

To use the server, set it up by configuring the database path, and request operations using the selected MCP tools. It can run in read-only mode to enhance security.

Key features of mcp-server-duckdb?

  • Support for executing SELECT, INSERT, UPDATE, and DELETE queries.
  • Ability to create new database tables and inspect table schemas.
  • Option to run in read-only mode to prevent data modifications.

Use cases of mcp-server-duckdb?

  1. Efficient data analysis and manipulation via DuckDB.
  2. Safeguarding data integrity in read-only environments.
  3. Integration with other tools and workflows utilizing MCP.

FAQ from mcp-server-duckdb?

  • What is DuckDB used for?

DuckDB is an in-process SQL OLAP database management system that supports high-performance analytics.

  • Is this server suitable for real-time analytics?

Yes, the server facilitates real-time querying capabilities typical of DuckDB.

  • How can I run the server?

You can run the server by configuring the command in the appropriate configuration files of supported platforms.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
ktanaka101
Star
116
Language
Python
License
MIT license
Category
database

Recommend Servers

View All
Payai X402 Tools

8 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