@memcone/cli

Portable coding identity for AI tools.

Bootstrap your repo's stack context in under 30 seconds. memcone init reads your existing files — package.json, AGENTS.md, pyproject.toml, lock files — and writes a .memcone/identity.json that every AI tool in your workflow automatically inherits via Memcone MCP.

npx memcone init

No global install. No config files. Just run it in your repo.

Why

Every time you open Cursor, Claude, or Windsurf in a new project, you re-explain the same things:

"We use pnpm, Next.js App Router, Drizzle ORM, no semicolons, deploy to Vercel."

memcone init extracts that once. memcone link pushes it to your Memcone project. After that, every AI tool that connects via MCP gets your full stack context on every request — automatically, without any prompts.

Install

# Run directly — no install needed
npx memcone init

# Or install globally
npm install -g @memcone/cli

Requires Node.js 18+.

Commands

memcone init

Scans your repo and writes .memcone/identity.json.

npx memcone init

Detects from package.json, tsconfig.json, pyproject.toml, Cargo.toml, go.mod, AGENTS.md, CLAUDE.md, and lock files. Prompts for anything it can't auto-detect (deployment, database, semicolons).

Supports: TypeScript, JavaScript, Python, Rust, Go

memcone link

Links this repo to your Memcone account and pushes identity to the cloud.

npx memcone link

1. Prompts for your API key (saved to ~/.memcone/credentials — never committed)
2. Creates or finds a matching project on your account
3. Sets it as the active project
4. Pushes all identity fields — MCP picks them up immediately

Get your API key at memcone.com/dashboard/keys.

memcone sync

Rescans your repo and pushes changed fields.

npx memcone sync

Run after adding a dependency or updating AGENTS.md. Only diffs are pushed.

memcone doctor

Shows detected stack, cloud sync status, and MCP configuration.

npx memcone doctor
npx memcone doctor --verbose   # show source file for each field

Checks your stack detection, .memcone/identity.json, API key validity, and whether MCP is configured in Claude / Cursor / Windsurf.

What gets committed

.memcone/identity.json is safe to commit — it contains no secrets:

{
  "_version": 1,
  "_projectId": "abc123",
  "projectName": "my-saas",
  "stack": {
    "language": "typescript",
    "framework": "Next.js App Router",
    "auth": "Better Auth",
    "orm": "Drizzle ORM",
    "payments": "Stripe",
    "packageManager": "pnpm",
    "database": "Neon (PostgreSQL)",
    "deployment": "Vercel"
  },
  "conventions": {
    "strictMode": true,
    "semicolons": false
  }
}

Your API key lives in ~/.memcone/credentials (chmod 600) and is never touched by this file.

How MCP picks it up

After memcone link, your active project is set. Every memcone.context call from any connected AI tool automatically includes:

## Project Identity
framework: Next.js App Router
auth: Better Auth
orm: Drizzle ORM
package manager: pnpm
strict mode: true
semicolons: false
deployment: Vercel
database: Neon (PostgreSQL)

No userId. No per-session prompts. Context flows from repo → cloud → agent.

→ Set up MCP

Links

• memcone.com — sign up and get an API key
• Docs — full CLI reference
• MCP setup — connect Cursor, Claude, Windsurf
• Dashboard — manage projects and identity
• @memcone/core — the underlying types and detection engine

License

MIT © Memcone