Provides a simple MCP server for note storage, note:// access, and note summarization with add-note and summarize-notes tools.
Configuration
View docs{
"mcpServers": {
"mcp_server_on_raspi": {
"command": "uv",
"args": [
"--directory",
"/Users/daikiwatanabe/ghq/github.com/daikw/mcp-server-on-raspi",
"run",
"mcp-server-on-raspi"
]
}
}
}You can run a lightweight MCP server that stores notes and exposes simple tools to add notes and generate summaries. It’s useful for testing note-based prompts and integrating note data into MCP-driven workflows.
You interact with the MCP server through a client that understands MCP commands. The server stores notes with a custom note:// URI, each note having a name, a description, and a text/plain payload. You can add notes, then request a summarized view of all stored notes. Two core prompts exist: summarize-notes creates summaries of all stored notes, and you can control the level of detail with an optional style parameter (brief or detailed). The server notifies connected clients when the resource state changes, so you can react to updates in real time.
Key capabilities you’ll use: create notes, access them via note:// URIs, and request a comprehensive summary that blends all notes together according to your chosen style. If you need to inspect or debug the live MCP server, you can use the MCP Inspector to connect to the running process and view operations as they occur.
Prerequisites: you need the MCP runtime tooling available in your environment. The runtime supports stdio-based servers and can be started directly or via a published command. The two runtime configurations shown below illustrate how to run the server locally for development and how to run it from a published setup.
Development run (stdio). Start the server using the local runtime with the same component name you’ll use to reference the MCP server. Replace the directory path with the location where you have the server source.
uv --directory /Users/daikiwatanabe/ghq/github.com/daikw/mcp-server-on-raspi \
run mcp-server-on-raspiPublished/run-ready configuration (stdio). If you prefer a streamlined run path using the published binary, start the server with the published command as shown.
uvx mcp-server-on-raspiDiagnostics and debugging. For debugging the MCP server, you can use the MCP Inspector. Launch it with the following command, then open the URL it provides in your browser to start debugging.
npx @modelcontextprotocol/inspector uv --directory /Users/daikiwatanabe/ghq/github.com/daikw/mcp-server-on-raspi run mcp-server-on-raspiThe server exposes two primary tools for working with notes and summaries. You use these through the MCP client by invoking the corresponding prompts and actions supported by the server.
- add-note: Adds a new note to the server. Requires name and content as strings. This updates the server state and notifies connected clients of resource changes.
- summarize-notes: Creates summaries of all stored notes. Accepts an optional style argument to control detail level (brief or detailed). It combines all current notes into a single prompt and executes the summary generation.
Development flow includes synchronizing dependencies, building distributions, and publishing to a package index. The typical steps are to synchronize, build, and publish using the MCP tooling.
Build and publish commands you would run during development are as follows.
uv sync
```
```
uv build
```
```
uv publishIf you need credentials for publishing, provide them via environment variables or command flags, such as a token or username/password pair, as appropriate for your setup.
Adds a new note to the server by supplying a name and content as required strings. This updates server state and notifies clients of resource changes.
Generates summaries of all stored notes. Accepts an optional style argument to control detail level (brief or detailed) and combines current notes into a single prompt for summarization.