DuckPond MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DUCKPOND_THREADS | No | Number of threads for DuckDB. | 4 |
| DUCKPOND_DATA_DIR | No | Local data directory for storage. | ~/.duckpond/data |
| DUCKPOND_STRATEGY | No | Storage strategy: parquet, duckdb, or hybrid. | duckdb |
| DUCKPOND_R2_BUCKET | No | R2 bucket name. | |
| DUCKPOND_S3_BUCKET | No | S3 bucket name. | |
| DUCKPOND_S3_REGION | No | S3 region (e.g., us-east-1). | |
| DUCKPOND_CACHE_TYPE | No | Cache type: disk, memory, or noop. | disk |
| DUCKPOND_JWT_SECRET | No | Secret for signing JWTs (auto-generated if not set). | |
| DUCKPOND_UI_ENABLED | No | Enable DuckDB UI (can also use --ui flag). | false |
| DUCKPOND_OAUTH_EMAIL | No | Email for OAuth user. | |
| DUCKPOND_S3_ENDPOINT | No | Custom S3 endpoint (for MinIO, etc.). | |
| DUCKPOND_DEFAULT_USER | No | Default user ID for DuckDB UI auto-start. | |
| DUCKPOND_MEMORY_LIMIT | No | Memory limit for DuckDB. | 4GB |
| DUCKPOND_OAUTH_ENABLED | No | Enable OAuth 2.0 authentication for HTTP transport. | false |
| DUCKPOND_OAUTH_USER_ID | No | Default user ID for OAuth. | |
| DUCKPOND_R2_ACCOUNT_ID | No | R2 account ID for cloud storage. | |
| DUCKPOND_JWT_EXPIRES_IN | No | JWT token expiration in seconds (default 1 year). | 31536000 |
| DUCKPOND_OAUTH_PASSWORD | No | Password for OAuth authentication. | |
| DUCKPOND_OAUTH_USERNAME | No | Username for OAuth authentication. | |
| DUCKPOND_BASIC_AUTH_EMAIL | No | Email for Basic Auth user. | |
| DUCKPOND_EVICTION_TIMEOUT | No | Idle timeout in milliseconds before eviction. | 300000 |
| DUCKPOND_MAX_ACTIVE_USERS | No | LRU cache size for multi-tenant users. | 10 |
| DUCKPOND_R2_ACCESS_KEY_ID | No | R2 access key ID. | |
| DUCKPOND_S3_ACCESS_KEY_ID | No | S3 access key ID. | |
| DUCKPOND_BASIC_AUTH_USER_ID | No | Default user ID for Basic Auth. | |
| DUCKPOND_BASIC_AUTH_PASSWORD | No | Password for Basic Authentication. | |
| DUCKPOND_BASIC_AUTH_USERNAME | No | Username for Basic Authentication. | |
| DUCKPOND_R2_SECRET_ACCESS_KEY | No | R2 secret access key. | |
| DUCKPOND_S3_SECRET_ACCESS_KEY | No | S3 secret access key. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
| logging | {} |
| completions | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| queryB | Execute a SQL query for a specific user and return results |
| executeB | Execute SQL statement (DDL/DML) for a specific user without returning results |
| getUserStatsB | Get statistics about a user's database (memory usage, query count, etc.) |
| isAttachedB | Check if a user's database is currently cached in memory |
| detachUserA | Manually detach a user's database from the cache to free resources |
| listUsersA | List all currently cached users and cache statistics |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
query and execute both run SQL but are clearly differentiated by whether results are returned, while the remaining tools have distinct management purposes. isAttached, getUserStats, and listUsers target different aspects of user database state. Only query/execute could potentially be confused, but the descriptions resolve the boundary.
Tool names mix lowercase single-word verbs like query and execute with camelCase compound names like getUserStats and detachUser. isAttached also follows a different predicate-style pattern rather than verb_noun. The naming style is inconsistent across the set.
Six tools is a well-scoped size for this server's purpose. Each tool covers a distinct need: SQL execution, user statistics, cache status, cache eviction, and user listing. No tool feels redundant or extraneous.
The tool surface covers the core workflow of querying and executing SQL, inspecting user state, and managing cached database attachment. A manual attach tool is missing, but automatic attachment on first use likely makes it unnecessary. Overall the domain is well covered with only minor optional gaps.