duckdb-mcp

Created By
richardwoodinga year ago
MCP Server for DuckDB
Overview

what is duckdb-mcp?

duckdb-mcp is a server designed to work with DuckDB, a high-performance analytical database management system. It provides a framework for managing and executing queries efficiently.

how to use duckdb-mcp?

To use duckdb-mcp, set up the server by following the installation instructions on the GitHub repository, and then connect to it using your preferred client to execute queries against DuckDB.

key features of duckdb-mcp?

  • High-performance query execution for analytical workloads
  • Easy integration with existing DuckDB setups
  • Support for various data formats and sources

use cases of duckdb-mcp?

  1. Running complex analytical queries on large datasets.
  2. Integrating with data pipelines for real-time analytics.
  3. Serving as a backend for data visualization tools.

FAQ from duckdb-mcp?

  • What is DuckDB?

DuckDB is an in-process SQL OLAP database management system designed for analytical workloads.

  • Is duckdb-mcp free to use?

Yes! duckdb-mcp is open-source and available under the MIT license.

  • How can I contribute to duckdb-mcp?

You can contribute by submitting issues or pull requests on the GitHub repository.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
richardwooding
Star
0
Language
Go
License
MIT 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