MCP Personal Tools Server
The MCP Personal Tools Server is a Node.js-based API that enables user management and note-taking through three core functionalities:
Fetch user details: Retrieve user profiles from a JSON database using the
user-detailsresourceCreate users: Add new users to the database with the
create-usertool, specifying parameters like name, email, address, phone, and passwordAdd notes: Append text as new lines to a local notes file using the
add-notetool
Provides a note-taking tool that enables appending timestamped text entries to a local notes file stored in the user's Documents directory.
Serves as the runtime environment for the MCP server, required to run the personal tools server.
Used for package management and running server commands for the MCP personal tools server.
Used as the programming language for implementing the MCP server and custom tools.
Provides schema validation for defining tool parameters and ensuring proper data typing in the MCP server.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@MCP Personal Tools Server add a note to remember to call the dentist tomorrow"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
MCP Demo Server
This project is a demonstration server for the Model Context Protocol (MCP). It provides a set of resources and tools to interact with a simple user database.
Architecture
mcp/
├───.gitignore
├───package-lock.json
├───package.json
├───tsconfig.json
├───.git/...
├───build/
│ └───data/...
└───src/
├───server.ts
└───data/
└───users.jsonThe server is built with Node.js and TypeScript, using the @modelcontextprotocol/sdk. It communicates over standard I/O using a StdioServerTransport.
The server exposes the following:
Resources:
user-details: Fetches user profiles from a JSON file.
Tools:
create-user: Creates a new user in the JSON database.add-note: Adds a note to a local file in the user's documents directory.
Related MCP server: Agent Construct
Installation
Clone the repository.
Install the dependencies:
npm installBuild the server:
npm run server:build
Usage
To start the server, run:
npm startFor development, you can use:
npm run server:devThis will start the server with tsx for automatic recompilation.
Available Scripts
npm start: Starts the production server.npm run server:dev: Starts the development server.npm run server:build: Compiles the TypeScript code.npm run server:build:watch: Compiles the TypeScript code in watch mode.npm run server:inspect: Inspects the server using the MCP Inspector.
Resources
user-details
Description: Get a user's details from the database.
URI:
users://{userId}/profileMIME Type:
application/json
Tools
create-user
Description: Create a new user in the database.
Parameters:
name(string)email(string)address(string)phone(string)password(string)
add-note
Description: Adds a new line to the notes file.
Parameters:
text(string): The text to add to the notes file.
Available Tools
2 toolsadd-noteB
Ajoute une nouvelle ligne au fichier de notes
Inputs: text (required).
create-userB
Create a new user in the database
Inputs: name (required), email (required), address (required), phone (required), +1 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 2 tools
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.
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.
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).
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
Related MCP Connectors
Nifty's MCP server — exposes tasks, projects, messages, and files as tools for AI agents.
Google Keep-style notes app with an MCP server for AI agents to read/write notes.
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yo…
Shared memory for your AI tools: tasks, notes and context every tool can read and write over MCP.
Related MCP Servers
- AlicenseBqualityDmaintenanceA 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.3ISC
- AlicenseNot gradedqualityDmaintenanceModel Context Protocol server that standardizes tool discovery, execution, and context management for AI applications.MIT
- AlicenseNot gradedqualityDmaintenanceMCP server for AI agents to read, write, and organize notes in a local-first, human-in-the-loop note-taking app.2MIT
- FlicenseNot gradedqualityDmaintenanceA Model Context Protocol server for managing text notes, with resources (note:// URIs), tools (create_note), and prompts (summarize_notes).-