Overview
QMD integrates with Claude Code (both the CLI and editor) via the Model Context Protocol. Claude Code has two configuration methods: a simplified plugin system, or manual MCP server configuration.Plugin Installation (Recommended)
The Claude Code marketplace provides a one-command installation:Verify Installation
Check that QMD is active:qmd@qmd in the output.
Manual MCP Configuration
If you prefer manual configuration or the plugin isn’t available, edit Claude Code’s settings file.Add QMD server configuration
Edit the JSON file to add QMD under If you already have other servers:
mcpServers:Restart Claude Code
If using the editor, restart it. For the CLI, the config is loaded on each invocation.
Transport Mode
Both the plugin and manual configuration use stdio transport by default. Each Claude Code session launchesqmd mcp as a subprocess.
When to Use HTTP Transport
Switch to HTTP transport if:- You use QMD frequently throughout the day
- You want models to stay loaded in memory
- You use multiple MCP clients (Desktop + Code) and want to share one daemon
Available Tools
Claude Code gets the same six tools as Claude Desktop:query— Deep search with sub-queries (lex/vec/hyde)get— Retrieve document by path or docidmulti_get— Batch retrieve by glob patternstatus— Index health and collections
qmd:// resource URIs.
Troubleshooting
Plugin not found
Ifclaude marketplace add tobi/qmd fails, the plugin may not be published yet. Use manual configuration instead.
Command not found
If Claude Code reportsqmd: command not found, verify installation:
qmd is installed but not in PATH, use the full path in settings.json:
Settings not taking effect
For the CLI:- Settings are loaded on each invocation, no restart needed
- Check for JSON syntax errors
- Completely quit and restart the editor
- Check logs for MCP initialization errors