Productivity
memoshelf.com
An MCP server for persisting and managing owner notes and run logs, with health check and CRUD operations.
ENDPOINT 1
https://memoshelf.com/mcp
MCP server metadata
- Name
- memoshelf
- Version
- 3.70.2
Memoshelf tools: health, log_run, store_note, runs, notes, fetch_md, keys, what_happened_last, usage_summary. runs, notes, and keys take action list/get/update/delete (notes also create; keys use list/mint/revoke). Hidden aliases for one version: public_url_to_md, update_run, update_note, get_run, get_note, delete_run, delete_note, create_run, create_note, list_runs, list_notes, revoke_key, mint_key, list_keys, stale_runs. health is a read-only ping matching GET /health and needs no API key. log_run appends a run; store_note stores a fact, decision, or reading — not a run log. what_happened_last is a keyed workspace-scoped read matching GET /v1/what_happened_last (last N runs with summaries + a notes array of id, title, body, tags, pinned, created_at, pinned first, plus ≤300 tokens of markdown; notes_omitted counts matching notes that array leaves out). usage_summary is a keyed read matching GET /v1/usage (this UTC month plus last 30 days, plus per-key last_request_at, quiet_for_hours, and per-key daily routes). fetch_md wraps keyed POST /v1/md (url required; honors robots.txt; 401 without a key). After initialize, send notifications/initialized. Other tools/call requires X-Api-Key or Authorization: Bearer ar_…
Known tools 9
store_noteStore a persisted owner note — a fact, decision, or reading to keep, not a run log.
Inferred read-onlynotesCreate a note first (action create, body required); then list, get, update, or delete.
Potential side effectsCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.memoshelf]
url = "https://memoshelf.com/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"memoshelf": {
"type": "http",
"url": "https://memoshelf.com/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: memoshelf
Remote MCP URL: https://memoshelf.com/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"memoshelf": {
"url": "https://memoshelf.com/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"memoshelf": {
"type": "http",
"url": "https://memoshelf.com/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "memoshelf",
"transport": "streamable-http",
"url": "https://memoshelf.com/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.