F
licenseA
qualityC
maintenanceA small Model Context Protocol (MCP) server that gives an AI a personal notes/todo store. Built for learning.
5
-
MCP Personal Tools Server
by Myk3rinos
Related Servers
Alternatives to MCP Personal Tools Server
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityFmaintenanceA Model Context Protocol (MCP) server that gives Claude a persistent personal notebook. Notes are stored on disk as JSON, so they survive restarts and are shared across every tool and resource.-
- FlicenseBqualityDmaintenanceA simple server for saving, listing, and searching notes persisted to a local JSON file. It enables users to manage their personal notes using natural language via the Model Context Protocol.3-
- AlicenseNot gradedqualityCmaintenanceMCP server for AI agents to read, write, and organize notes in a local-first, human-in-the-loop note-taking app.4 npm2MIT
- AlicenseNot gradedqualityDmaintenanceModel Context Protocol server that standardizes tool discovery, execution, and context management for AI applications.MIT
- FlicenseNot gradedqualityDmaintenanceA Model Context Protocol server for managing text notes, with resources (note:// URIs), tools (create_note), and prompts (summarize_notes).-
TDQS
B3/5.0
Scored across 2 tools
Disambiguation5/5
The two tools have completely distinct purposes: one handles file-based note-taking (add-note), while the other manages database users (create-user). There is no overlap or ambiguity between these functions, making it easy for an agent to select the correct tool.
Naming Consistency2/5
The naming is inconsistent: add-note uses a verb-object pattern with a hyphen, while create-user uses a verb-object pattern with a hyphen but differs in verb choice (add vs. create). Although both use hyphens, the verb inconsistency and lack of a clear naming convention (e.g., all using the same verb style) reduce predictability.
Tool Count2/5
With only 2 tools, the server feels severely under-scoped for a 'Personal Tools Server' that implies a broader utility set. This minimal count suggests incomplete coverage of personal tooling needs, such as missing operations for notes (e.g., read, delete) or users (e.g., get, update).
Completeness2/5
The tool surface has significant gaps. For notes, there is only an 'add' operation without read, update, or delete capabilities. For users, only 'create' is provided, lacking get, update, delete, or list functions. This incomplete coverage will likely cause agent failures when trying to perform common workflows.
Maintenance
ActivityInactive
ResponsivenessNo issues