python-mcp-server
by Potato-29
README.md
# python-mcp-server 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": {
"python-mcp-server": {
"command": "uv",
"args": [
"--directory",
"C:\Prayas\Personal\Projects\python-mcp-server",
"run",
"python-mcp-server"
]
}
}
```
</details>
<details>
<summary>Published Servers Configuration</summary>
```
"mcpServers": {
"python-mcp-server": {
"command": "uvx",
"args": [
"python-mcp-server"
]
}
}
```
</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 C:\Prayas\Personal\Projects\python-mcp-server run python-mcp-server
```
Upon launching, the Inspector will display a URL that you can access in your browser to begin debugging.TDQS
C2.7/5.0
Scored across 2 tools
Disambiguation5/5
The two tools serve completely different domains: notes and calendar events. There is no overlap or confusion possible.
Naming Consistency2/5
Tool names use inconsistent conventions: 'add-note' uses snake_case with hyphen, while 'createEvent' uses camelCase. No consistent pattern.
Tool Count2/5
With only two tools, the server feels underdeveloped for a generic Python MCP server. A more complete set would have at least 5-10 tools to justify its name.
Completeness2/5
The server covers only a single operation each for notes and events. Missing essential operations like list, delete, or update for both domains, leaving significant gaps.
Maintenance
ActivityInactive
ResponsivenessNo issues