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
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago