Remember Me Replication Server
Replication server for the Bible memorization app Remember Me
Getting started
Configuration
The server requires the following environment variables for deployment:
WEB_APP_BASE_URL - Base URL of the frontend web application
- Used for password reset links, activation emails, and redirects
- Format: Full URL with protocol (http or https)
- Allowed domains:
localhost, *.local, *.remem.me
- Examples:
https://web.remem.me, http://localhost:3000
- Default:
https://web.remem.me
For a complete list of configuration options, see CLAUDE.md.
MCP Server
The project includes an MCP server that exposes Remember Me
to AI agents. It runs as two instances:
Public (mcp.remem.me, no sign-in) — read-only access to the published library:
- browse_collections — Search and filter published collections by keyword, language, or popularity
- get_collection_detail — Get full collection with all verse text, references, and topics
- get_collection_metrics — Community engagement stats (progress, mastery, activity)
Authenticated (auth.remem.me, OAuth sign-in) — the public tools plus your own workspace:
- list_accounts / list_verses / get_verse / search_verses / find_existing_verses — find your accounts, lists and verses
- add_verse / update_verse / delete_verse — manage your personal verses; add_verses / update_verses add or change up to 100 at once
- create_collection / update_collection / delete_collection — manage collections you publish
- get_daily_reading — the day's readings from a one-year Bible plan
- get_review_queue — your New/Due/Known boxes for a hands-free spoken review. It mirrors the
app's flashcard run — the same box vocabulary in your language, the same
remembered/forgotten verdicts, the same quiz direction per box — so a spoken session and the
screen agree. The session is transient: nothing is written back and no due date changes.
Local development
python manage.py run_mcp
python manage.py run_mcp --auth
Streamable HTTP transport, served at /mcp.
Production deployment (Alwaysdata)
Each MCP instance runs as its own Alwaysdata site — its own uvicorn process — alongside
the main Django app, which is served via WSGI (rm_replication/wsgi.py). The Django app has no
ASGI entrypoint; uvicorn/ASGI is used only by the MCP servers.
-
In the Alwaysdata admin panel, create a site per instance:
- Type: User program
- Command:
cd ~/rm_replication && venv/bin/python manage.py run_mcp --host 0.0.0.0 --port 8001 --settings=rm_replication.settings.prod
(add --auth and use port 8002 for the authenticated instance)
- Domain:
mcp.remem.me (public) / auth.remem.me (authenticated)
-
Add each site's ID to the post-receive hook so it restarts on deploy. Tool descriptions are
registered once at process startup, so a restart is required for tool changes to reach clients.
-
Set NEW_RELIC_LICENSE_KEY in each site's environment. The servers then send a usage event
per tool call (McpToolCall) and per connection step (McpAuth) to New Relic
(mcp_server/usage.py); without it they send nothing.
-
For OpenAI's plugin portal, set OPENAI_APPS_CHALLENGE on the authenticated site to the
token the portal shows when you connect the server, then restart the site. It is served
as plain text at https://auth.remem.me/.well-known/openai-apps-challenge; without it
that path answers 404.
Need help?
Please use the user forum for help requests and how-to questions.
Please open Gitlab issues for bugs and enhancements only, not general help requests.
Want to contribute?
If you want to contribute through code or documentation, the Contributing
guide is the best place to start. If you have questions, feel free
to ask.
Want to support us?
If you want to support us financially, you can help fund the project
through a Paypal donation.