couchbase-mcp-server 0.3.1rc2__tar.gz

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -0,0 +1,201 @@
1
+ Apache License
2
+ Version 2.0, January 2004
3
+ http://www.apache.org/licenses/
4
+
5
+ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
6
+
7
+ 1. Definitions.
8
+
9
+ "License" shall mean the terms and conditions for use, reproduction,
10
+ and distribution as defined by Sections 1 through 9 of this document.
11
+
12
+ "Licensor" shall mean the copyright owner or entity authorized by
13
+ the copyright owner that is granting the License.
14
+
15
+ "Legal Entity" shall mean the union of the acting entity and all
16
+ other entities that control, are controlled by, or are under common
17
+ control with that entity. For the purposes of this definition,
18
+ "control" means (i) the power, direct or indirect, to cause the
19
+ direction or management of such entity, whether by contract or
20
+ otherwise, or (ii) ownership of fifty percent (50%) or more of the
21
+ outstanding shares, or (iii) beneficial ownership of such entity.
22
+
23
+ "You" (or "Your") shall mean an individual or Legal Entity
24
+ exercising permissions granted by this License.
25
+
26
+ "Source" form shall mean the preferred form for making modifications,
27
+ including but not limited to software source code, documentation
28
+ source, and configuration files.
29
+
30
+ "Object" form shall mean any form resulting from mechanical
31
+ transformation or translation of a Source form, including but
32
+ not limited to compiled object code, generated documentation,
33
+ and conversions to other media types.
34
+
35
+ "Work" shall mean the work of authorship, whether in Source or
36
+ Object form, made available under the License, as indicated by a
37
+ copyright notice that is included in or attached to the work
38
+ (an example is provided in the Appendix below).
39
+
40
+ "Derivative Works" shall mean any work, whether in Source or Object
41
+ form, that is based on (or derived from) the Work and for which the
42
+ editorial revisions, annotations, elaborations, or other modifications
43
+ represent, as a whole, an original work of authorship. For the purposes
44
+ of this License, Derivative Works shall not include works that remain
45
+ separable from, or merely link (or bind by name) to the interfaces of,
46
+ the Work and Derivative Works thereof.
47
+
48
+ "Contribution" shall mean any work of authorship, including
49
+ the original version of the Work and any modifications or additions
50
+ to that Work or Derivative Works thereof, that is intentionally
51
+ submitted to Licensor for inclusion in the Work by the copyright owner
52
+ or by an individual or Legal Entity authorized to submit on behalf of
53
+ the copyright owner. For the purposes of this definition, "submitted"
54
+ means any form of electronic, verbal, or written communication sent
55
+ to the Licensor or its representatives, including but not limited to
56
+ communication on electronic mailing lists, source code control systems,
57
+ and issue tracking systems that are managed by, or on behalf of, the
58
+ Licensor for the purpose of discussing and improving the Work, but
59
+ excluding communication that is conspicuously marked or otherwise
60
+ designated in writing by the copyright owner as "Not a Contribution."
61
+
62
+ "Contributor" shall mean Licensor and any individual or Legal Entity
63
+ on behalf of whom a Contribution has been received by Licensor and
64
+ subsequently incorporated within the Work.
65
+
66
+ 2. Grant of Copyright License. Subject to the terms and conditions of
67
+ this License, each Contributor hereby grants to You a perpetual,
68
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
69
+ copyright license to reproduce, prepare Derivative Works of,
70
+ publicly display, publicly perform, sublicense, and distribute the
71
+ Work and such Derivative Works in Source or Object form.
72
+
73
+ 3. Grant of Patent License. Subject to the terms and conditions of
74
+ this License, each Contributor hereby grants to You a perpetual,
75
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
76
+ (except as stated in this section) patent license to make, have made,
77
+ use, offer to sell, sell, import, and otherwise transfer the Work,
78
+ where such license applies only to those patent claims licensable
79
+ by such Contributor that are necessarily infringed by their
80
+ Contribution(s) alone or by combination of their Contribution(s)
81
+ with the Work to which such Contribution(s) was submitted. If You
82
+ institute patent litigation against any entity (including a
83
+ cross-claim or counterclaim in a lawsuit) alleging that the Work
84
+ or a Contribution incorporated within the Work constitutes direct
85
+ or contributory patent infringement, then any patent licenses
86
+ granted to You under this License for that Work shall terminate
87
+ as of the date such litigation is filed.
88
+
89
+ 4. Redistribution. You may reproduce and distribute copies of the
90
+ Work or Derivative Works thereof in any medium, with or without
91
+ modifications, and in Source or Object form, provided that You
92
+ meet the following conditions:
93
+
94
+ (a) You must give any other recipients of the Work or
95
+ Derivative Works a copy of this License; and
96
+
97
+ (b) You must cause any modified files to carry prominent notices
98
+ stating that You changed the files; and
99
+
100
+ (c) You must retain, in the Source form of any Derivative Works
101
+ that You distribute, all copyright, patent, trademark, and
102
+ attribution notices from the Source form of the Work,
103
+ excluding those notices that do not pertain to any part of
104
+ the Derivative Works; and
105
+
106
+ (d) If the Work includes a "NOTICE" text file as part of its
107
+ distribution, then any Derivative Works that You distribute must
108
+ include a readable copy of the attribution notices contained
109
+ within such NOTICE file, excluding those notices that do not
110
+ pertain to any part of the Derivative Works, in at least one
111
+ of the following places: within a NOTICE text file distributed
112
+ as part of the Derivative Works; within the Source form or
113
+ documentation, if provided along with the Derivative Works; or,
114
+ within a display generated by the Derivative Works, if and
115
+ wherever such third-party notices normally appear. The contents
116
+ of the NOTICE file are for informational purposes only and
117
+ do not modify the License. You may add Your own attribution
118
+ notices within Derivative Works that You distribute, alongside
119
+ or as an addendum to the NOTICE text from the Work, provided
120
+ that such additional attribution notices cannot be construed
121
+ as modifying the License.
122
+
123
+ You may add Your own copyright statement to Your modifications and
124
+ may provide additional or different license terms and conditions
125
+ for use, reproduction, or distribution of Your modifications, or
126
+ for any such Derivative Works as a whole, provided Your use,
127
+ reproduction, and distribution of the Work otherwise complies with
128
+ the conditions stated in this License.
129
+
130
+ 5. Submission of Contributions. Unless You explicitly state otherwise,
131
+ any Contribution intentionally submitted for inclusion in the Work
132
+ by You to the Licensor shall be under the terms and conditions of
133
+ this License, without any additional terms or conditions.
134
+ Notwithstanding the above, nothing herein shall supersede or modify
135
+ the terms of any separate license agreement you may have executed
136
+ with Licensor regarding such Contributions.
137
+
138
+ 6. Trademarks. This License does not grant permission to use the trade
139
+ names, trademarks, service marks, or product names of the Licensor,
140
+ except as required for reasonable and customary use in describing the
141
+ origin of the Work and reproducing the content of the NOTICE file.
142
+
143
+ 7. Disclaimer of Warranty. Unless required by applicable law or
144
+ agreed to in writing, Licensor provides the Work (and each
145
+ Contributor provides its Contributions) on an "AS IS" BASIS,
146
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
147
+ implied, including, without limitation, any warranties or conditions
148
+ of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
149
+ PARTICULAR PURPOSE. You are solely responsible for determining the
150
+ appropriateness of using or redistributing the Work and assume any
151
+ risks associated with Your exercise of permissions under this License.
152
+
153
+ 8. Limitation of Liability. In no event and under no legal theory,
154
+ whether in tort (including negligence), contract, or otherwise,
155
+ unless required by applicable law (such as deliberate and grossly
156
+ negligent acts) or agreed to in writing, shall any Contributor be
157
+ liable to You for damages, including any direct, indirect, special,
158
+ incidental, or consequential damages of any character arising as a
159
+ result of this License or out of the use or inability to use the
160
+ Work (including but not limited to damages for loss of goodwill,
161
+ work stoppage, computer failure or malfunction, or any and all
162
+ other commercial damages or losses), even if such Contributor
163
+ has been advised of the possibility of such damages.
164
+
165
+ 9. Accepting Warranty or Additional Liability. While redistributing
166
+ the Work or Derivative Works thereof, You may choose to offer,
167
+ and charge a fee for, acceptance of support, warranty, indemnity,
168
+ or other liability obligations and/or rights consistent with this
169
+ License. However, in accepting such obligations, You may act only
170
+ on Your own behalf and on Your sole responsibility, not on behalf
171
+ of any other Contributor, and only if You agree to indemnify,
172
+ defend, and hold each Contributor harmless for any liability
173
+ incurred by, or claims asserted against, such Contributor by reason
174
+ of your accepting any such warranty or additional liability.
175
+
176
+ END OF TERMS AND CONDITIONS
177
+
178
+ APPENDIX: How to apply the Apache License to your work.
179
+
180
+ To apply the Apache License to your work, attach the following
181
+ boilerplate notice, with the fields enclosed by brackets "[]"
182
+ replaced with your own identifying information. (Don't include
183
+ the brackets!) The text should be enclosed in the appropriate
184
+ comment syntax for the file format. We also recommend that a
185
+ file or class name and description of purpose be included on the
186
+ same "printed page" as the copyright notice for easier
187
+ identification within third-party archives.
188
+
189
+ Copyright [yyyy] [name of copyright owner]
190
+
191
+ Licensed under the Apache License, Version 2.0 (the "License");
192
+ you may not use this file except in compliance with the License.
193
+ You may obtain a copy of the License at
194
+
195
+ http://www.apache.org/licenses/LICENSE-2.0
196
+
197
+ Unless required by applicable law or agreed to in writing, software
198
+ distributed under the License is distributed on an "AS IS" BASIS,
199
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
200
+ See the License for the specific language governing permissions and
201
+ limitations under the License.
@@ -0,0 +1,256 @@
1
+ Metadata-Version: 2.4
2
+ Name: couchbase-mcp-server
3
+ Version: 0.3.1rc2
4
+ Summary: Couchbase MCP Server - The Developer Data Platform for Critical Applications in Our AI World
5
+ Author-email: Nithish Raghunandanan <devadvocates@couchbase.com>
6
+ License-Expression: Apache-2.0
7
+ Project-URL: Homepage, https://github.com/Couchbase-Ecosystem/mcp-server-couchbase
8
+ Project-URL: Documentation, https://github.com/Couchbase-Ecosystem/mcp-server-couchbase#readme
9
+ Project-URL: Issues, https://github.com/Couchbase-Ecosystem/mcp-server-couchbase/issues
10
+ Classifier: Development Status :: 4 - Beta
11
+ Classifier: Programming Language :: Python :: 3
12
+ Classifier: Topic :: Database
13
+ Requires-Python: >=3.10
14
+ Description-Content-Type: text/markdown
15
+ License-File: LICENSE
16
+ Requires-Dist: click==8.2.1
17
+ Requires-Dist: couchbase==4.4.0
18
+ Requires-Dist: lark-sqlpp==0.0.1
19
+ Requires-Dist: mcp[cli]==1.6.0
20
+ Provides-Extra: dev
21
+ Requires-Dist: ruff>=0.8.0; extra == "dev"
22
+ Requires-Dist: pre-commit>=3.0.0; extra == "dev"
23
+ Dynamic: license-file
24
+
25
+ # Couchbase MCP Server
26
+
27
+ An [MCP](https://modelcontextprotocol.io/) server implementation of Couchbase that allows LLMs to directly interact with Couchbase clusters.
28
+
29
+ ## Features
30
+
31
+ - Get a list of all the scopes and collections in the specified bucket
32
+ - Get the structure for a collection
33
+ - Get a document by ID from a specified scope and collection
34
+ - Upsert a document by ID to a specified scope and collection
35
+ - Delete a document by ID from a specified scope and collection
36
+ - Run a [SQL++ query](https://www.couchbase.com/sqlplusplus/) on a specified scope
37
+ - There is an option in the MCP server, `READ_ONLY_QUERY_MODE` that is set to true by default to disable running SQL++ queries that change the data or the underlying collection structure. Note that the documents can still be updated by ID.
38
+
39
+ ## Prerequisites
40
+
41
+ - Python 3.10 or higher.
42
+ - A running Couchbase cluster. The easiest way to get started is to use [Capella](https://docs.couchbase.com/cloud/get-started/create-account.html#getting-started) free tier, which is fully managed version of Couchbase server. You can follow [instructions](https://docs.couchbase.com/cloud/clusters/data-service/import-data-documents.html#import-sample-data) to import one of the sample datasets or import your own.
43
+ - [uv](https://docs.astral.sh/uv/) installed to run the server.
44
+ - An [MCP client](https://modelcontextprotocol.io/clients) such as [Claude Desktop](https://claude.ai/download) installed to connect the server to Claude. The instructions are provided for Claude Desktop and Cursor. Other MCP clients could be used as well.
45
+
46
+ ## Configuration
47
+
48
+ Clone the repository to your local machine.
49
+
50
+ ```bash
51
+ git clone https://github.com/Couchbase-Ecosystem/mcp-server-couchbase.git
52
+ ```
53
+
54
+ ### Server Configuration for MCP Clients
55
+
56
+ This is the common configuration for the MCP clients such as Claude Desktop, Cursor, Windsurf Editor.
57
+
58
+ ```json
59
+ {
60
+ "mcpServers": {
61
+ "couchbase": {
62
+ "command": "uv",
63
+ "args": [
64
+ "--directory",
65
+ "path/to/cloned/repo/mcp-server-couchbase/",
66
+ "run",
67
+ "src/mcp_server.py"
68
+ ],
69
+ "env": {
70
+ "CB_CONNECTION_STRING": "couchbases://connection-string",
71
+ "CB_USERNAME": "username",
72
+ "CB_PASSWORD": "password",
73
+ "CB_BUCKET_NAME": "bucket_name"
74
+ }
75
+ }
76
+ }
77
+ }
78
+ ```
79
+
80
+ The server can be configured using environment variables. The following variables are supported:
81
+
82
+ - `CB_CONNECTION_STRING`: The connection string to the Couchbase cluster
83
+ - `CB_USERNAME`: The username with access to the bucket to use to connect
84
+ - `CB_PASSWORD`: The password for the username to connect
85
+ - `CB_BUCKET_NAME`: The name of the bucket that the server will access
86
+ - `READ_ONLY_QUERY_MODE`: Setting to configure whether SQL++ queries that allow data to be modified are allowed. It is set to True by default.
87
+ - `path/to/cloned/repo/mcp-server-couchbase/` should be the path to the cloned repository on your local machine. Don't forget the trailing slash at the end!
88
+
89
+ > Note: If you have other MCP servers in use in the client, you can add it to the existing `mcpServers` object.
90
+
91
+ ### Claude Desktop
92
+
93
+ Follow the steps below to use Couchbase MCP server with Claude Desktop MCP client
94
+
95
+ 1. The MCP server can now be added to Claude Desktop by editing the configuration file. More detailed instructions can be found on the [MCP quickstart guide](https://modelcontextprotocol.io/quickstart/user).
96
+
97
+ - On Mac, the configuration file is located at `~/Library/Application Support/Claude/claude_desktop_config.json`
98
+ - On Windows, the configuration file is located at `%APPDATA%\Claude\claude_desktop_config.json`
99
+
100
+ Open the configuration file and add the [configuration](#server-configuration-for-mcp-clients) to the `mcpServers` section.
101
+
102
+ 2. Restart Claude Desktop to apply the changes.
103
+
104
+ 3. You can now use the server in Claude Desktop to run queries on the Couchbase cluster using natural language and perform CRUD operations on documents.
105
+
106
+ #### Claude Desktop Logs
107
+
108
+ The logs for Claude Desktop can be found in the following locations:
109
+
110
+ - MacOS: ~/Library/Logs/Claude
111
+ - Windows: %APPDATA%\Claude\Logs
112
+
113
+ The logs can be used to diagnose connection issues or other problems with your MCP server configuration. For more details, refer to the [official documentation](https://modelcontextprotocol.io/quickstart/user#getting-logs-from-claude-for-desktop).
114
+
115
+ ### Cursor
116
+
117
+ Follow steps below to use Couchbase MCP server with Cursor:
118
+
119
+ 1. Install [Cursor](https://cursor.sh/) on your machine.
120
+
121
+ 2. In Cursor, go to Cursor > Cursor Settings > MCP > Add a new global MCP server. Also, checkout the docs on [setting up MCP server configuration](https://docs.cursor.com/context/model-context-protocol#configuring-mcp-servers) from Cursor.
122
+
123
+ 3. Specify the same [configuration](#server-configuration-for-mcp-clients). You may need to add the server configuration under a parent key of mcpServers.
124
+
125
+ 4. Save the configuration.
126
+
127
+ 5. You will see couchbase as an added server in MCP servers list. Refresh to see if server is enabled.
128
+
129
+ 6. You can now use the Couchbase MCP server in Cursor to query your Couchbase cluster using natural language and perform CRUD operations on documents.
130
+
131
+ For more details about MCP integration with Cursor, refer to the [official Cursor MCP documentation](https://docs.cursor.sh/ai-features/mcp-model-context-protocol).
132
+
133
+ #### Cursor Logs
134
+
135
+ In the bottom panel of Cursor, click on "Output" and select "Cursor MCP" from the dropdown menu to view server logs. This can help diagnose connection issues or other problems with your MCP server configuration.
136
+
137
+ ### Windsurf Editor
138
+
139
+ Follow the steps below to use the Couchbase MCP server with [Windsurf Editor](https://windsurf.com/).
140
+
141
+ 1. Install [Windsurf Editor](https://windsurf.com/download) on your machine.
142
+
143
+ 2. In Windsurf Editor, navigate to Command Palette > Windsurf MCP Configuration Panel or Windsurf - Settings > Advanced > Cascade > Model Context Protocol (MCP) Servers. For more details on the configuration, please refer to the [official documentation](https://docs.windsurf.com/windsurf/mcp#configuring-mcp).
144
+
145
+ 3. Click on Add Server and then Add custom server. On the configuration that opens in the editor, add the Couchbase MCP Server [configuration](#server-configuration-for-mcp-clients) from above.
146
+
147
+ 4. Save the configuration.
148
+
149
+ 5. You will see couchbase as an added server in MCP Servers list under Advanced Settings. Refresh to see if server is enabled.
150
+
151
+ 6. You can now use the Couchbase MCP server in Windsurf Editor to query your Couchbase cluster using natural language and perform CRUD operations on documents.
152
+
153
+ For more details about MCP integration with Windsurf Editor, refer to the official [Windsurf MCP documentation](https://docs.windsurf.com/windsurf/mcp).
154
+
155
+ ### SSE Server Mode
156
+
157
+ There is an option to run the MCP server in [Server-Sent Events (SSE)](https://modelcontextprotocol.io/docs/concepts/transports#server-sent-events-sse) transport mode.
158
+
159
+ > Note: SSE mode has been [deprecated](https://modelcontextprotocol.io/docs/concepts/transports#server-sent-events-sse-deprecated) by MCP. We are investigating adding support for Streamable HTTP.
160
+
161
+ #### Usage
162
+
163
+ By default, the MCP server will run on port 8080 but this can be configured using the `FASTMCP_PORT` environment variable.
164
+
165
+ > uv run src/mcp_server.py --connection-string='<couchbase_connection_string>' --username='<database_username>' --password='<database_password>' --bucket-name='<couchbase_bucket_to_use>' --read-only-query-mode=true --transport=sse
166
+
167
+ The server will be available on http://localhost:8080/sse. This can be used in MCP clients supporting SSE transport mode.
168
+
169
+ ## Docker Image
170
+
171
+ The MCP server can also be built and run as a Docker container. Prebuilt images can be found on [DockerHub](https://hub.docker.com/r/couchbaseecosystem/mcp-server-couchbase).
172
+
173
+ ```bash
174
+ docker build -t mcp/couchbase .
175
+ ```
176
+
177
+ ### Running
178
+
179
+ The MCP server can be run with the environment variables being used to configure the Couchbase settings. The environment variables are the same as described in the [Configuration section](#server-configuration-for-mcp-clients)
180
+
181
+ ```bash
182
+ docker run -i \
183
+ -e CB_CONNECTION_STRING='<couchbase_connection_string>' \
184
+ -e CB_USERNAME='<database_user>' \
185
+ -e CB_PASSWORD='<database_password>' \
186
+ -e CB_BUCKET_NAME='<bucket_name>' \
187
+ -e MCP_TRANSPORT='stdio/sse' \
188
+ -e READ_ONLY_QUERY_MODE="true/false" \
189
+ mcp/couchbase
190
+ ```
191
+
192
+ ### Risks Associated with LLMs
193
+
194
+ - The use of large language models and similar technology involves risks, including the potential for inaccurate or harmful outputs.
195
+ - Couchbase does not review or evaluate the quality or accuracy of such outputs, and such outputs may not reflect Couchbase's views.
196
+ - You are solely responsible for determining whether to use large language models and related technology, and for complying with any license terms, terms of use, and your organization's policies governing your use of the same.
197
+
198
+ ### Managed MCP Server
199
+
200
+ The Couchbase MCP server can also be used as a managed server in your agentic applications via [Smithery.ai](https://smithery.ai/server/@Couchbase-Ecosystem/mcp-server-couchbase).
201
+
202
+ ## Troubleshooting Tips
203
+
204
+ - Ensure the path to your MCP server repository is correct in the configuration.
205
+ - Verify that your Couchbase connection string, database username, password and bucket name are correct.
206
+ - If using Couchbase Capella, ensure that the cluster is [accessible](https://docs.couchbase.com/cloud/clusters/allow-ip-address.html) from the machine where the MCP server is running.
207
+ - Check that the database user has proper permissions to access the specified bucket.
208
+ - Confirm that the uv package manager is properly installed and accessible. You may need to provide absolute path to uv in the `command` field in the configuration.
209
+ - Check the logs for any errors or warnings that may indicate issues with the MCP server. The server logs are under the name, `mcp-server-couchbase.log`.
210
+
211
+ ---
212
+
213
+ ## 👩‍💻 Contributing
214
+
215
+ We welcome contributions from the community! Whether you want to fix bugs, add features, or improve documentation, your help is appreciated.
216
+
217
+ ### For Developers
218
+
219
+ If you're interested in contributing code or setting up a development environment:
220
+
221
+ 📖 **See [CONTRIBUTING.md](CONTRIBUTING.md)** for comprehensive developer setup instructions, including:
222
+
223
+ - Development environment setup with `uv`
224
+ - Code linting and formatting with Ruff
225
+ - Pre-commit hooks installation
226
+ - Project structure overview
227
+ - Development workflow and practices
228
+
229
+ ### Quick Start for Contributors
230
+
231
+ ```bash
232
+ # Clone and setup
233
+ git clone https://github.com/Couchbase-Ecosystem/mcp-server-couchbase.git
234
+ cd mcp-server-couchbase
235
+
236
+ # Install with development dependencies
237
+ uv sync --extra dev
238
+
239
+ # Install pre-commit hooks
240
+ uv run pre-commit install
241
+
242
+ # Run linting
243
+ ./scripts/lint.sh
244
+ ```
245
+
246
+ ---
247
+
248
+ ## 📢 Support Policy
249
+
250
+ We truly appreciate your interest in this project!
251
+ This project is **community-maintained**, which means it's **not officially supported** by our support team.
252
+
253
+ If you need help, have found a bug, or want to contribute improvements, the best place to do that is right here — by [opening a GitHub issue](https://github.com/Couchbase-Ecosystem/mcp-server-couchbase/issues).
254
+ Our support portal is unable to assist with requests related to this project, so we kindly ask that all inquiries stay within GitHub.
255
+
256
+ Your collaboration helps us all move forward together — thank you!