Couchbase Guru MCP Server
Allows asking questions about Couchbase products, features, SDKs, services, tutorials, and examples, returning natural-language answers with source links from the official Couchbase documentation.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Couchbase Guru MCP ServerHow do I create a primary index with the Python SDK in Couchbase Server 7.6?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Couchbase Guru MCP Server
An MCP server that lets LLMs search the Couchbase documentation from your MCP client. It exposes a single tool, ask_couchbase_docs, which forwards your question to a hosted retrieval-augmented (RAG) documentation agent and returns an answer with source links.
No Couchbase cluster or credentials required. The server talks only to the documentation agent backend, not to your data.
Tool
Tool Name | Description |
| Answer a question about any Couchbase product, feature, SDK, service, tutorial, or example by searching the official documentation. Returns a natural-language answer followed by the documentation source URLs. |
Ask complete, self-contained questions — the backend has no conversation history, so include the product, version, and language where relevant (e.g. "How do I create a primary index with the Python SDK in Couchbase Server 7.6?").
Related MCP server: docrag
Prerequisites
Python 3.10 or higher.
uv installed to run the server.
An MCP client such as Claude Desktop, Cursor, or VS Code.
Configuration
The server can be run from the prebuilt PyPI package or from source with uv. It works with zero configuration — the public documentation agent is used by default.
Running from PyPI
{
"mcpServers": {
"couchbase-guru": {
"command": "uvx",
"args": ["couchbase-guru"]
}
}
}If you already have other MCP servers configured, add this entry to the existing
mcpServersobject.
Running from Source
Clone the repository:
git clone https://github.com/Couchbase-Ecosystem/couchbase-guru.gitThen point your MCP client at it:
{
"mcpServers": {
"couchbase-guru": {
"command": "uv",
"args": [
"--directory",
"path/to/cloned/repo/couchbase-guru/",
"run",
"src/mcp_server.py"
]
}
}
}
path/to/cloned/repo/couchbase-guru/should be the path to the cloned repository on your machine. Don't forget the trailing slash.
Options
All options are optional and can be set via CLI argument or environment variable:
CLI Argument | Environment Variable | Description | Default |
|
| Transport mode: |
|
|
| Host for HTTP transport mode |
|
|
| Port for HTTP transport mode |
|
|
| Base URL of the documentation agent backend. Set this to run against your own self-hosted agent; if unset, the public agent is used. | Public agent |
|
| Secret salt used to pseudonymize client IPs (HTTP transport). Set a shared value for consistent hashing across multiple instances; a local salt is generated when unset. | Auto-generated |
Check the installed version with:
uvx couchbase-guru --versionSelf-hosting the documentation agent
By default the server uses a shared, public documentation agent, so most users need no setup. If you run your own agent backend, point the server at it:
uvx couchbase-guru --agent-base-url https://your-agent.example.comRate limiting & privacy
The public agent applies fair-use rate limits. To support this, the server sends a pseudonymous device identifier to the backend (in the User-Agent header):
stdio: a random id generated once and stored in a per-user file on your machine.
HTTP: a salted, one-way hash of the connecting IP — the raw address is never sent.
No question content or personal data is persisted by the MCP server itself. If you prefer not to share a rate-limit signal, self-host the agent (see above).
Client-specific configuration
Edit the configuration file (see the MCP quickstart guide):
macOS:
~/Library/Application Support/Claude/claude_desktop_config.jsonWindows:
%APPDATA%\Claude\claude_desktop_config.json
Add the configuration to the
mcpServerssection.Restart Claude Desktop.
Logs: ~/Library/Logs/Claude (macOS) or %APPDATA%\Claude\Logs (Windows).
In Cursor, go to Cursor Settings > Tools & Integrations > MCP Tools.
Add the configuration manually, or use the one-click Install in Cursor link.
Save, then refresh to confirm the server is enabled.
Logs: in the bottom panel, click Output and select Cursor MCP from the dropdown.
Open Command Palette > Windsurf MCP Configuration Panel (or Settings > Advanced > Cascade > Model Context Protocol (MCP) Servers).
Click Add Server > Add custom server and add the configuration.
Save, then refresh to confirm the server is enabled.
See the Windsurf MCP documentation for details.
Create
.vscode/mcp.jsonin your workspace (or run MCP: Open User Configuration for a global config).VS Code uses
serversas the top-level key (notmcpServers):{ "servers": { "couchbase-guru": { "command": "uvx", "args": ["couchbase-guru"] } } }Once saved, use the inline action list to
Start/Stop/manage the server.
See the VS Code MCP docs for details.
Install the AI Assistant or Junie plugin.
Navigate to Settings > Tools > AI Assistant or Junie > MCP Server.
Click "+", add the configuration, and click Save, then Apply.
Logs: Help > Show Log in Finder (Explorer) > mcp > couchbase-guru.
Streamable HTTP transport mode
The server can run in Streamable HTTP mode so multiple clients can connect to one instance. Check that your MCP client supports this transport first.
uvx couchbase-guru --transport=http --port=8000The server will be available at http://localhost:8000/mcp:
{
"mcpServers": {
"couchbase-guru-http": {
"url": "http://localhost:8000/mcp"
}
}
}This mode does not include authorization support.
Docker
Build the image:
docker build -t couchbase-guru .Run it (stdio by default; no credentials needed):
{
"mcpServers": {
"couchbase-guru-docker": {
"command": "docker",
"args": ["run", "--rm", "-i", "couchbase-guru"]
}
}
}For HTTP transport, publish the port and set the transport:
docker run --rm -i \
-e CB_MCP_TRANSPORT=http \
-e CB_MCP_HOST=0.0.0.0 \
-e CB_MCP_PORT=8000 \
-p 8000:8000 \
couchbase-guruRisks associated with LLMs
The use of large language models and similar technology involves risks, including the potential for inaccurate or harmful outputs.
Couchbase does not review or evaluate the quality or accuracy of such outputs, and such outputs may not reflect Couchbase's views.
You are solely responsible for determining whether to use large language models and related technology, and for complying with any applicable license terms, terms of use, and your organization's policies.
Troubleshooting
Confirm that
uv/uvxis installed and on yourPATH. You may need to provide an absolute path touv/uvxin thecommandfield.If a search times out, the documentation backend may be busy — retry in a moment.
To rule out the public backend, run against your own agent with
--agent-base-url.If running from source after updating the repo, run
uv syncto refresh dependencies.Check your MCP client's logs (locations above) for errors.
Testing
Unit tests run offline (the backend is mocked):
uv sync --extra dev
uv run pytest tests/Integration tests exercise the tool end-to-end against a live agent backend and are opt-in:
CB_MCP_RUN_INTEGRATION=1 uv run pytest tests/test_docs_tools.pyBy default they use the public agent; set CB_AGENT_BASE_URL to target a different backend.
👩💻 Contributing
Contributions are welcome! To report a bug, request a feature, or contribute improvements, open a GitHub issue.
See CONTRIBUTING.md for developer setup (environment with uv, linting/formatting with Ruff, pre-commit hooks, and project structure).
# Clone and set up
git clone https://github.com/Couchbase-Ecosystem/couchbase-guru.git
cd couchbase-guru
# Install with development dependencies
uv sync --extra dev
# Install pre-commit hooks
uv run pre-commit install📢 Support Policy
We appreciate your interest in this project! It is Couchbase community-maintained, which means it is not officially supported by our support team. Our engineers monitor and maintain this repo and will try to resolve issues on a best-effort basis. Please keep all inquiries within GitHub.
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Tools
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceProvides semantic search over markdown documentation using RAG, allowing natural language queries and integration with MCP clients.1MIT
- AlicenseNot gradedqualityDmaintenanceProvides RAG (Retrieval Augmented Generation) access to technical documentation through MCP, enabling LLMs to search and retrieve relevant documentation on-demand.4MIT
- FlicenseNot gradedqualityDmaintenanceEnables answering natural-language questions from FAQ documents using vector search and LLM generation via an MCP tool.
- FlicenseNot gradedqualityCmaintenanceEnables semantic search and AI-powered Q&A over ingested GitHub documentation repositories via MCP tools.
Related MCP Connectors
Query any docs site via MCP. Submit a URL, ask questions, get cited answers.
Agentic search over your Dewey document collections from any MCP-compatible client.
Apple Developer Documentation with Semantic Search, RAG, and AI reranking for MCP clients
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/Couchbase-Ecosystem/couchbase-guru'
If you have feedback or need assistance with the MCP directory API, please join our Discord server