Notes MCP Server
# mcp-server-on-raspi MCP server
A MCP server project
## 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": {
"mcp-server-on-raspi": {
"command": "uv",
"args": [
"--directory",
"/Users/daikiwatanabe/ghq/github.com/daikw/mcp-server-on-raspi",
"run",
"mcp-server-on-raspi"
]
}
}
```
</details>
<details>
<summary>Published Servers Configuration</summary>
```
"mcpServers": {
"mcp-server-on-raspi": {
"command": "uvx",
"args": [
"mcp-server-on-raspi"
]
}
}
```
</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/daikiwatanabe/ghq/github.com/daikw/mcp-server-on-raspi run mcp-server-on-raspi
```
Upon launching, the Inspector will display a URL that you can access in your browser to begin debugging.TDQS
Scored across 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool 'add-note' has a clear and distinct purpose that cannot be confused with any other tool in this set.
The naming follows a consistent verb-noun pattern with 'add-note', and since there is only one tool, there is no inconsistency to evaluate. The naming is clear and predictable within this minimal set.
A single tool is too few for a server named 'Notes MCP Server', which implies a broader scope for managing notes (e.g., creating, reading, updating, deleting). This minimal set feels incomplete and under-scoped for the apparent domain.
The tool surface is severely incomplete for a notes management server. It only provides an 'add-note' tool, lacking essential operations like retrieving, updating, deleting, or listing notes, which will cause significant agent failures in typical workflows.