pxt-anzu-diary-mcp
by djanzu
README.md
# pxt-anzu-diary-mcp MCP server
PXT日記MCP
## 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": {
"pxt-anzu-diary-mcp": {
"command": "uv",
"args": [
"--directory",
"/Users/anzu/kaisha/pxt-anzu-diary-mcp",
"run",
"pxt-anzu-diary-mcp"
]
}
}
```
</details>
<details>
<summary>Published Servers Configuration</summary>
```
"mcpServers": {
"pxt-anzu-diary-mcp": {
"command": "uvx",
"args": [
"pxt-anzu-diary-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/anzu/kaisha/pxt-anzu-diary-mcp run pxt-anzu-diary-mcp
```
Upon launching, the Inspector will display a URL that you can access in your browser to begin debugging.
## Gemini CLIでの設定
```settings.json
{
"mcpServers": {
"pxt-anzu-diary-mcp": {
"command": "uv",
"args": [
"run",
"--directory",
"/Users/your_directory/pxt-anzu-diary-mcp",
"pxt-anzu-diary-mcp"
],
"env": {
"DIARY_API_BASE": "http://localhost:8000/api"
}
}
}
}
```
TDQS
B3.4/5.0
Scored across 2 tools
Disambiguation5/5
The two tools, add-note and get-note, are clearly distinct: one creates a diary entry and the other retrieves one. No overlap or ambiguity exists between them.
Naming Consistency5/5
Both tool names follow the same verb_noun pattern with a hyphen separator: add-note and get-note. This is fully consistent and predictable.
Tool Count3/5
With only 2 tools, the server feels borderline thin. While each tool has a clear purpose, the count is at the low end of what is considered reasonable for a domain-specific server.
Completeness3/5
The server covers create and get operations only, missing update, delete, and list functionality. These are notable gaps for a diary management server, though the core add/retrieve flow is present.
Maintenance
ActivityInactive
ResponsivenessNo issues