Skip to main content
Glama
mcp-memo-server

mcp-memo-server

by shinji0214

mcp-memo-server

A simple memo management MCP server that can be used from Claude Code. This is a sample implementation for learning purposes. It supports simple user authentication (user registration / login / session tokens), and memos are separated per user.

Provided tools

Tool name

Description

Arguments

register

Register a new user

username: string, password: string

login

Log in and obtain a session token

username: string, password: string

add_memo

Add a memo (login required)

token: string, text: string

list_memos

Get a list of your registered memos (login required)

token: string

delete_memo

Delete one of your memos by ID (login required)

token: string, id: number

Memos are saved to memos.json (in the project root), and user information is saved to users.json. Both are already in .gitignore.

Authentication mechanism (learning points)

  • Passwords are hashed with a salt using Node.js's built-in crypto.scrypt and stored in users.json (never stored in plain text).

  • A successful login issues a random session token. Tokens are managed only in the server process's memory, with a validity period of 2 hours, and they expire when the server restarts.

  • add_memo / list_memos / delete_memo validate the token and return an error if there is no valid session.

  • list_memos / delete_memo filter memos by the userId associated with the token, so other users' memos cannot be seen.

Note: This is a learning-oriented authentication implementation for stdio transport (local process). With stdio, anyone who can start the server already has execution permissions on the process, so this authentication is less about being a "real security boundary" and more about "separating multiple users" and "learning how to implement an authentication flow."

Related MCP server: mcp-memos

Setup

npm install
npm run build

Registering with Claude Code

After building, register it using the project's absolute path.

claude mcp add --transport stdio memo-server -- node /絶対パス/mcp-memo-server/build/index.js

To verify the registration:

claude mcp list

In a Claude Code session, typing /mcp lets you confirm that memo-server shows as connected.

Usage example (conversation within Claude Code)

> ユーザー名 taro、パスワード pass1234 で登録して
> taro でログインして
> 「Qiitaのネタを考える」というメモを追加して
> 今登録されているメモを一覧で見せて
> ID 1 のメモを削除して

Claude remembers the token issued at login within the conversation and automatically reuses it for subsequent add_memo / list_memos / delete_memo calls.

Manual verification

test-client.mjs is a simple script that sends JSON-RPC messages (initialize → tools/list → tools/call) directly to a server launched as a child process and checks the responses.

node test-client.mjs

To remove

claude mcp remove memo-server

Available Tools

5 tools
add_memoメモを追加A

新しいメモをテキストで追加します。ログインが必要です。

Inputs: text (required), token (required).

delete_memoメモを削除A

指定したIDの自分のメモを削除します。ログインが必要です。

Inputs: id (required), token (required).

list_memosメモ一覧を取得A

自分が登録したメモを一覧表示します。ログインが必要です。

Inputs: token (required).

loginログインA

ユーザー名とパスワードでログインし、セッショントークンを取得します。

Inputs: password (required), username (required).

registerユーザー登録A

ユーザー名とパスワードで新しいアカウントを作成します。

Inputs: password (required), username (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.9/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: register/login handle authentication, while add_memo, list_memos, and delete_memo cover distinct memo operations. There is no meaningful overlap or ambiguity between any two tools.

    Naming Consistency4/5

    Most tools follow a clear imperative verb_noun pattern like add_memo, list_memos, and delete_memo. register and login are standard auth verbs without a noun object, and list_memos uses a plural while delete_memo is singular, but the overall naming is predictable and readable.

    Tool Count5/5

    Five tools is well-scoped for a simple memo server requiring authentication and basic memo management. Every tool earns its place, and there are no redundant or unnecessary additions.

    Completeness3/5

    The set covers registration, login, creating memos, listing memos, and deleting memos, but lacks an update/edit memo operation and an explicit logout tool. Editing an existing memo requires deleting and recreating it, which is a notable gap for a memo service.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers