MCP -Couchbase

This MCP server exposes tools that let an LLM interact with a Couchbase database. Once the server is running (via npx or a manual install), Claude Desktop connections can access a set of capabilities for querying buckets, managing scopes and collections, performing CRUD operations on documents, and handling indexes. The available tools include: query for running N1QL queries, listBuckets to enumerate buckets, createScope and deleteScope to manage scopes, listScopes to inspect scopes, createCollection and dropCollection to manage collections, createDocument, getDocument, updateDocument, deleteDocument, and bulkCreateDocuments for batch inserts, and createIndex, createPrimaryIndex, listIndexes, and dropIndex for index management. Each tool accepts optional collection and scope parameters to target the correct container, and credentials are provided via environment variables to keep secrets out of the prompts.

Prerequisites:

• Node.js 16 or higher
• npm (comes with Node.js)
• A running Couchbase instance (Capella) with a bucket ready for use
• Claude Desktop (for integration)

Option A — Using NPX (Recommended):

1. Install and run the MCP server directly from the npm package registry:

npx -y @couchbasedatabase/couchbase-mcp

Option B — Manual Installation (Clone and run locally):

1. Clone the repository and install dependencies:

# Clone the repository
git clone https://github.com/Aniket310101/MCP-Server-Couchbase.git
cd MCP-Server-Couchbase

# Install dependencies
npm install

# Build if required by the project
npm run build

2. Run the server (typical local run):

node dist/index.js

Claude Desktop integration requires configuring the MCP server in Claude’s config, as shown in the examples below (NPX-based or manual installation).

Tips and considerations:

• Always supply credentials via environment variables rather than embedding them in prompts or code.
• When using NPX, the package will be fetched on demand; ensure network access to npm registry.
• If using the manual installation flow, ensure the build outputs to the path specified in your config (e.g., dist/index.js).
• For production, consider placing the MCP server behind a reverse proxy and enabling authentication.
• If you encounter connectivity issues, verify COUCHBASE_URL, BUCKET, USERNAME, and PASSWORD are correct and that network access to the Capella cluster is allowed.
• The toolset supports optional collection and scope parameters; always specify them when targeting specific data containers to avoid unintended operations.