For Cursor users on a long-running project
Your agent knows the code. Make it remember why the code is this way.
Push 2–3 of your own notes. Ask one question you keep re-explaining. Get a sourced answer in about five minutes.
Sample project memory
Exact-name answers from sample project memory. Not your repo yet. neither-demo
Searched exact name
PostgreSQLDecision Use PostgreSQL as the system of record for billing and account state.
Rejected MongoDB — rejected because we need ACID transactions across invoice line items and tax rows; eventual consistency was unacceptable for chargebacks.
Searched exact name
KafkaDecision Use Postgres LISTEN/NOTIFY plus an outbox table for domain events.
Rejected Apache Kafka — rejected: ops cost and on-call load too high for a three-person team; we do not need multi-subscriber replay yet.
Searched exact name
invite codesDecision Use invite codes instead of open signup.
Rejected Stripe Checkout on day one — seller/tax gates are not green.
Source Harbor beta signup ADR / invite-codes note
Google's next screen may show our auth provider (Supabase). That's expected.
Free. No card. Google sign-in creates the workspace key. Node 20+ required for Cursor MCP.
- 1Workspace: pending
- 2MCP key: pending
- 3Notes: pending
- 4Ask a question: pending
- 5Confirm it helped: pending
Neither does not automatically index your whole codebase. You choose which notes to push.
Cursor install
After Google sign-in you get a workspace key. Paste it into ~/.cursor/mcp.json or use Add to Cursor on the next screen.
{
"mcpServers": {
"neither": {
"command": "npx",
"args": [
"-y",
"@neitherai/mcp-server@latest"
],
"env": {
"NEITHER_API_KEY": "sk_ctx_…",
"NEITHER_API_BASE": "https://api.neither.online"
}
}
}
}