rember

The Rember MCP server enables Claude to create flashcards for Rember directly from chat or from PDFs, using the official Model Context Protocol (MCP). This integration lets Claude send notes from your conversations or documents to Rember as rembs (flashcards) so you can review ideas later with spaced repetition. The server exposes a single primary tool: create_flashcards. When Claude calls this tool with a list of notes, the server routes those notes to the Rember API to generate flashcards for each note. After a user asks to remember something in chat, you can trigger this tool with prompts like “help me remember this,” “create a few flashcards,” or “add to Rember,” and Claude will format the input for the tool accordingly. The tool’s design emphasizes clear inputs and uses the Rember API to batch-generate flashcards tied to your notes, while the MCP framework handles the orchestration and response handling.

Prerequisites:

• Node.js and npm installed on your machine (npx is included with npm).
• A Rember account and an MCP API key from your Rember settings.

Install and run steps:

1. Ensure you have Node.js and npm installed. You can verify with: node -v npm -v

2. Obtain your Rember MCP API key from the Rember settings page (Settings > MCP API).

3. Start the MCP server using npx with your API key: npx -y @getrember/mcp --api-key=YOUR_REMBER_API_KEY

4. If you integrate with Claude Desktop, add your server to claude_desktop_config.json under mcpServers: { "mcpServers": { "rember": { "command": "npx", "args": ["-y", "@getrember/mcp", "--api-key=YOUR_REMBER_API_KEY"] } } }

5. Replace YOUR_REMBER_API_KEY with your actual API key. You can also pass the key via an environment variable if you prefer: REMBER_API_KEY=your_key npx -y @getrember/mcp

6. Test the integration by invoking the create_flashcards tool from Claude or your CLI setup and ensure rembs are created in your Rember account.

Tips and common considerations:

• Logging: Enable and direct logs to stderr early in the process for easier debugging.
• Tool design: Start with a simple tool (like create_flashcards) and iterate on the description to reduce user confusion.
• Tool inputs: Provide clear input shapes and describe what happens after the tool runs (notes are sent to the Rember API to generate flashcards).
• User guidance: Include examples of use cases (e.g., creating flashcards from a conversation, from PDFs) and how users might invoke the tool (e.g., “help me remember this,” “add to Rember,” “create a few flashcards”).
• Telemetry and reliability: Consider adding telemetry for observability and implement retries for transient errors.
• Testing: Build a small test suite to simulate Claude Desktop interactions and verify tool invocation paths.
• Limits and messaging: If users hit limits, guide them toward Rember Pro with the subscription URL.

Environment and configuration notes:

• The MCP tooling relies on your API key to authenticate with Rember. Keep keys secure and rotate as needed.
• If you switch environments (local dev, staging, production), duplicate the configuration with appropriate API keys and update any environment variables accordingly.