couchdb-mcp-server

Created By
MCP-Mirrora year ago
Mirror of
Overview

what is couchdb-mcp-server?

The couchdb-mcp-server is a Model Context Protocol server designed for interacting with CouchDB databases, enabling AI assistants to manage and manipulate CouchDB documents through a simplified interface.

how to use couchdb-mcp-server?

To use the couchdb-mcp-server, install it via Smithery or set it up in your development environment by configuring the CouchDB connection URL and version. You can then utilize various tools provided by the server to manage your CouchDB databases.

key features of couchdb-mcp-server?

  • Create, list, and delete CouchDB databases.
  • Create and update documents in a database.
  • Query documents using Mango query syntax (for CouchDB 3.x+).
  • Automatic detection of CouchDB version for feature support.

use cases of couchdb-mcp-server?

  1. Managing multiple CouchDB databases efficiently.
  2. Automating document creation and updates in CouchDB.
  3. Performing complex queries on CouchDB documents using Mango.

FAQ from couchdb-mcp-server?

  • What is the required environment for couchdb-mcp-server?

You need Node.js 14 or higher and a running CouchDB instance with proper credentials.

  • How do I install couchdb-mcp-server?

You can install it via Smithery or by cloning the repository and running the installation commands.

  • What happens if I encounter an error?

The server includes robust error handling and will return formatted error messages through the MCP protocol.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
MCP-Mirror
Star
0
Language
JavaScript
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.

16 hours ago
Voyei

6 hours ago