Cloud, for memory that follows you across apps

This is the hosted path: your memory graph lives in Postgres on a server we run, reachable over HTTPS from any MCP-capable client. Same five tools as the local version, same behavior — the difference is where the data lives and how you authenticate. Note this currently covers MCP-capable clients (Claude Desktop, Cursor, and similar) — not a browser-based web app, and not ChatGPT's or Gemini's web UIs.

Why you'd pick this over local

If you don't want to run a Python environment locally at all, or you want the same memory graph reachable from more than one machine or client, this is for you. If you're a single developer using one machine with Claude Desktop or Cursor, the local path is simpler and keeps your data off any server entirely.

Option A — API key

Simple header-based auth, good for clients that don't support OAuth (Cursor, ModelScope's directory, mcp-remote). Register to get a key:

curl -X POST https://api.yliuai.com/users/register \
  -H "Content-Type: application/json" \
  -d '{"email": "you@example.com"}'
# the api_key in the response (starts with mck_) is shown only this once -- save it

Configure a remote MCP connection in your client with url https://api.yliuai.com/mcp-apikey/ and header x-api-key: <your key>. Exact JSON shape depends on your client's current docs.

There's no web sign-up form yet — registration is a single curl call, shown above. A browser-based form is on the roadmap but needs a CORS-enabled endpoint on the API side first, which hasn't shipped.

Option B — OAuth 2.1 (for Claude's Connector flow)

Anthropic's official Connector Directory requires OAuth 2.1 + PKCE, which plain API keys don't satisfy. This deployment supports it, but hasn't been submitted to the official directory yet — so there's no one-click "Connect" button in Claude's UI. Add it manually:

In Claude Desktop or Cursor, add a custom connector / remote MCP server with URL https://api.yliuai.com/mcp
The client will redirect you through an OAuth authorization flow.
Sign-in is a magic link — enter your email, click the link you receive, and you'll be redirected back to the client, now connected.

This is a manual connection, not an official Anthropic-listed connector — we're not implying otherwise. Once Connector Directory submission happens, this section will be updated with the official one-click flow.

Both paths (API key and OAuth) resolve to the same user_id and the same underlying memory graph for a given account — they're two doors into one house, not two separate datasets.

Other marketplaces (ModelScope, Cursor directory)

Not submitted yet. Once listed, this section will link directly to the listing instead of asking you to paste in a URL by hand.

What's different from the local version

Your graph lives in a shared Postgres database, strictly isolated per account (user_id) — not a local SQLite file.
There's no automatic sync between your local and cloud memories — they're two independent stores today.
See the Privacy page for exactly what's collected, what third parties are involved (an LLM provider for extraction, Resend for magic-link email), and the known gaps in the current setup.

Full remote-access doc on GitHub (deployment details, verification history) →