docstore-mcp
by johwiebe
README.md
# docstore-mcp MCP server
A small chromadb based document storage mcp server
## Components
### Resources
The server implements a simple note storage system with:
- Custom note:// URI scheme for accessing individual notes
- Each note resource has a name, description and text/plain mimetype
### Prompts
The server provides a single prompt:
- summarize-notes: Creates summaries of all stored notes
- Optional "style" argument to control detail level (brief/detailed)
- Generates prompt combining all current notes with style preference
### Tools
The server implements one tool:
- add-note: Adds a new note to the server
- Takes "name" and "content" as required string arguments
- Updates server state and notifies clients of resource changes
## Configuration
[TODO: Add configuration details specific to your implementation]
## Quickstart
### Install
#### Claude Desktop
On MacOS: `~/Library/Application\ Support/Claude/claude_desktop_config.json`
On Windows: `%APPDATA%/Claude/claude_desktop_config.json`
<details>
<summary>Development/Unpublished Servers Configuration</summary>
```
"mcpServers": {
"docstore-mcp": {
"command": "uv",
"args": [
"--directory",
"/Users/johanneswiebe/dev/docstore/docstore-mcp",
"run",
"docstore-mcp"
]
}
}
```
</details>
<details>
<summary>Published Servers Configuration</summary>
```
"mcpServers": {
"docstore-mcp": {
"command": "uvx",
"args": [
"docstore-mcp"
]
}
}
```
</details>
## Development
### Building and Publishing
To prepare the package for distribution:
1. Sync dependencies and update lockfile:
```bash
uv sync
```
2. Build package distributions:
```bash
uv build
```
This will create source and wheel distributions in the `dist/` directory.
3. Publish to PyPI:
```bash
uv publish
```
Note: You'll need to set PyPI credentials via environment variables or command flags:
- Token: `--token` or `UV_PUBLISH_TOKEN`
- Or username/password: `--username`/`UV_PUBLISH_USERNAME` and `--password`/`UV_PUBLISH_PASSWORD`
### Debugging
Since MCP servers run over stdio, debugging can be challenging. For the best debugging
experience, we strongly recommend using the [MCP Inspector](https://github.com/modelcontextprotocol/inspector).
You can launch the MCP Inspector via [`npm`](https://docs.npmjs.com/downloading-and-installing-node-js-and-npm) with this command:
```bash
npx @modelcontextprotocol/inspector uv --directory /Users/johanneswiebe/dev/docstore/docstore-mcp run docstore-mcp
```
Upon launching, the Inspector will display a URL that you can access in your browser to begin debugging.TDQS
A3.7/5.0
Scored across 3 tools
Disambiguation5/5
Each tool has a distinct purpose: listing documents, searching within them, and retrieving info about a specific document. No overlap in functionality.
Naming Consistency4/5
Tools use snake_case. 'list_documents' and 'get_document_info' follow verb_noun, but 'search' is a bare verb, creating a minor inconsistency.
Tool Count3/5
Three tools is minimal for a document store. While the core operations of listing, searching, and getting info are present, the set feels sparse for a full-featured server.
Completeness2/5
The server lacks essential operations like adding or deleting documents. Without ingestion or removal tools, the surface is incomplete for managing a document store.
Maintenance
ActivityInactive
ResponsivenessNo issues