CouchDB MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| createDatabaseC | Create a new CouchDB database |
| listDatabasesB | List all CouchDB databases |
| deleteDatabaseC | Delete a CouchDB database |
| createDocumentC | Create a new document or update an existing document in a database |
| getDocumentC | Get a document from a database |
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 5 tools
Each tool has a distinct purpose targeting specific resources and actions: createDatabase, deleteDatabase, and listDatabases handle database-level operations, while createDocument and getDocument handle document-level operations. There is no overlap or ambiguity between tools.
All tool names follow a consistent verb_noun pattern (e.g., createDatabase, getDocument) using camelCase throughout. The naming is predictable and uniform across all five tools.
With 5 tools, this server is well-scoped for basic CouchDB operations, covering database and document management without being overly sparse or bloated. Each tool serves a clear and necessary function.
The toolset covers core CRUD operations for databases (create, delete, list) and documents (create, get), but lacks document deletion and update tools, which are common in database workflows. This minor gap might require workarounds but does not severely hinder functionality.