memopaper-mcp

MCP server for memopaper — gives AI agents direct access to your memo buffer.

Configuration

Claude Desktop

Add to claude_desktop_config.json:

{
  "mcpServers": {
    "memopaper": {
      "command": "npx",
      "args": ["memopaper-mcp@latest"],
      "env": {
        "MEMOPAPER_API_KEY": "mp_..."
      }
    }
  }
}

Claude Code

Add .mcp.json to your project root:

{
  "mcpServers": {
    "memopaper": {
      "command": "npx",
      "args": ["memopaper-mcp@latest"],
      "env": {
        "MEMOPAPER_API_KEY": "mp_..."
      }
    }
  }
}

Get your API key at memopaper.dev under Dashboard → API Keys.

Note: Never commit .mcp.json containing your API key to version control. Add it to .gitignore.

Related MCP server: mem0-agent-memory

Tool

Exposes a single memo tool with the following actions:

Optional params on most actions: group, visibility, limit.

Environment Variables

Claude Code Skills

For Claude Code users, optional slash commands are available in the skills/ directory:

Install:

mkdir -p ~/.claude/commands/memopaper
cp skills/watch.md ~/.claude/commands/memopaper/watch.md
cp skills/help.md  ~/.claude/commands/memopaper/help.md

Usage:

/memopaper:watch @tasks
/memopaper:watch @tasks 10
/memopaper:watch @tasks --shell

Warning: All memo execution — whether as AI instructions or shell commands — runs on your machine with your permissions. You are fully responsible for the content and consequences of every memo in the queue. Use only with memo groups you fully control and trust.

Shell execution is disabled by default. Pass --shell to enable it. Even then, destructive commands (rm, del, git reset --hard, dd, etc.) are automatically blocked and logged to @warning.

Related

• memopaper.dev — web dashboard

• memopaper — CLI client