MCP Notes Server
Servidor de notas MCP
Una implementación de servidor de Protocolo de Contexto de Modelo (MCP) para administrar notas con almacenamiento persistente.
Características
Crear, leer, actualizar y eliminar notas
Almacenamiento persistente mediante JSON
Seguimiento de marcas de tiempo para creación y modificaciones
Resumen de notas mediante indicaciones
Acceso basado en recursos mediante el esquema URI note://
Related MCP server: Beeper MCP Note Server
Instalación
Instalación mediante herrería
Para instalar notas para Claude Desktop automáticamente a través de Smithery :
npx -y @smithery/cli install notes --client claudeInstalación manual
Asegúrese de tener instalado Python 3.10 o posterior
Crear un entorno virtual:
python -m venv .venv # On Unix/MacOS: source .venv/bin/activate # On Windows: .venv\Scripts\activateRequisitos de instalación:
pip install MCP
Estructura del proyecto
notes/
├── __init__.py # Package initialization
├── server.py # Main server implementation
├── storage.py # Note persistence layer
├── resources.py # Resource handling (note:// URIs)
├── prompts.py # LLM prompt generation
└── tools/ # Server tools
├── __init__.py # Tools package initialization
├── list_tools.py # Tool listing functionality
└── handle_tools.py # Tool handling implementationHerramientas disponibles
add-note: Crea una nueva notalist-all-notes: Muestra todas las notas almacenadasupdate-note: Modificar una nota existentedelete-note: Eliminar una nota
Uso
Iniciar el servidor:
mcp install src/notes mcp start NotesOperaciones de ejemplo:
# Create a note await client.call_tool("add-note", { "name": "example", "content": "This is a test note" }) # List all notes await client.call_tool("list-all-notes") # Update a note await client.call_tool("update-note", { "name": "example", "content": "Updated content" }) # Delete a note await client.call_tool("delete-note", { "name": "example" })
Almacenamiento
Las notas se almacenan en notes_storage.json con la siguiente estructura:
{
"note_name": {
"content": "Note content",
"created_at": "2025-01-12T11:28:16.721704",
"modified_at": "2025-01-12T11:28:16.721704"
}
}Acceso a recursos
Se puede acceder a las notas como recursos utilizando el esquema URI note:// :
Lista de recursos: devuelve todas las notas disponibles como recursos
Leer recurso: Acceder a una nota específica usando
note://internal/note_name
Generación de indicaciones
El servidor incluye una función de generación de indicaciones para resumir notas:
Admite resúmenes breves y detallados
Notas de formato para la entrada del modelo de lenguaje
Disponible a través del mensaje "resumir notas"
Desarrollo
Para modificar o ampliar el servidor:
Clonar el repositorio
Instalar dependencias de desarrollo
Realizar cambios en el módulo apropiado
Pruebe exhaustivamente antes de implementar
Pruebas
Las pruebas deben cubrir:
Operaciones CRUD básicas
Manejo de múltiples notas
Casos de error
Acceso a recursos
Generación de mensajes rápidos
Licencia
[Agregue su licencia aquí]
Available Tools
4 toolsadd-noteC
Create a new note
Inputs: content (required), name (required).
delete-noteC
Delete an existing note
Inputs: name (required).
list-all-notesB
Read all stored notes
Inputs: no named parameters.
update-noteC
Update an existing note
Inputs: content (required), name (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose targeting specific CRUD operations on notes: add-note for creation, delete-note for deletion, list-all-notes for reading all, and update-note for updates. There is no overlap in functionality, making tool selection unambiguous.
The tools follow a mostly consistent verb-noun pattern (add-note, delete-note, update-note), but list-all-notes deviates slightly by including 'all'. This minor inconsistency does not significantly hinder readability or predictability.
With 4 tools, the server is well-scoped for a notes management system, covering the essential CRUD operations. Each tool earns its place without being overly sparse or bloated, fitting the typical 3-15 tool range appropriately.
The tool set provides complete CRUD coverage for the notes domain: create (add-note), read (list-all-notes), update (update-note), and delete (delete-note). There are no obvious gaps, allowing agents to handle full note lifecycles without dead ends.
Maintenance
Related MCP Connectors
An MCP server that used to create notes
Google Keep-style notes app with an MCP server for AI agents to read/write notes.
Markdown-based note-taking with a hosted MCP server. Your notes serve you and your AI.
Notes, files, GitHub, and Drive through one MCP connection.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceA simple note-taking MCP server that allows storing and summarizing notes with custom URI schemes and provides functionality to add notes and generate summaries with different detail levels.5-
- FlicenseNot gradedqualityDmaintenanceA simple MCP server for creating and managing notes with support for summarization functionality.1-
- FlicenseBqualityDmaintenanceA simple note-taking MCP server that stores notes and can generate summaries of stored content.4-
- FlicenseNot gradedqualityNot gradedmaintenanceA simple MCP server that implements a note storage system allowing users to add and summarize notes with customizable detail levels.3-