Setup

MCP Memory Server on localhost:7878: What to Check

Understand the local daemon boundary behind Origin's MCP memory tools and how to troubleshoot port 7878.

Qi-Xuan LuUpdated Jun 20265 min read

Article packet

Concepts

Developers debugging MCP memory setup

5 min read

The daemon is the local source of truth.

MCP clients talk through origin-mcp to reach that daemon.

doctor and status are the first checks when port 7878 fails.

Quick answer

Origin's daemon listens on 127.0.0.1:7878 by default. MCP clients do not talk to the database directly; they launch origin-mcp, and origin-mcp talks to the local daemon.

Origin keeps this boundary explicit. The daemon owns storage and retrieval, while Claude Code, Cursor, Codex, and other clients call tools through the MCP connector.

When this problem appears

When MCP memory setup fails, users often see only a missing tool or a connection error. The real issue is usually daemon reachability, MCP configuration, or a client restart requirement.

Debug port 7878

Check the daemon before changing every client setting.

Run ~/.origin/bin/origin status.
Run ~/.origin/bin/origin doctor for a fuller setup report.
Run ~/.origin/bin/origin mcp add <client> --dry-run to inspect the origin-mcp command the client should launch.
Run lsof -nP -iTCP:7878 -sTCP:LISTEN and identify which process owns the port before changing client settings.
Restart the MCP client after config changes.
Make sure another development daemon is not owning the wrong data directory.

Daemon and MCP checks

~/.origin/bin/origin status
~/.origin/bin/origin doctor
~/.origin/bin/origin mcp add codex --dry-run
lsof -nP -iTCP:7878 -sTCP:LISTEN

What to check next

Loopback avoids LAN exposure, but 127.0.0.1:7878 is still sensitive local access to a memory API. Do not bind the daemon to a non-loopback address unless you are intentionally doing development or self-hosted networking, and redact memory contents from diagnostics.

Try the local memory loop

Install Origin, connect your AI client, and verify that capture, recall, and handoff work on your machine.

Get started View on GitHub

FAQ

Can I change the daemon port?+

Yes for development, but the daemon port, bind address, CLI target, and MCP connector target are separate settings. Non-default ports should update the daemon and connector together, usually with an isolated data dir.

Why not let each MCP client store its own memory?+

Because separate stores fragment context. Origin uses one daemon so tools share the same source of truth.