jevmem saves the decisions, rules and failed approaches from your Claude Code chats to JEVMEM.md in your repo, and brings the relevant ones back next session.
Setup
Choose your client, copy the config, then fill in any required environment variables.
claude mcp add jevmem --env TYPESAFE_API_KEY='<TYPESAFE_API_KEY>' -- npx -y jevmem~/.codex/config.toml
[mcp_servers.jevmem]
command = "npx"
args = ["-y", "jevmem"]
env = { TYPESAFE_API_KEY = "<TYPESAFE_API_KEY>" }
# codex mcp add jevmem --env TYPESAFE_API_KEY='<TYPESAFE_API_KEY>' -- npx -y jevmem~/.cursor/mcp.json
{
"mcpServers": {
"jevmem": {
"command": "npx",
"args": [
"-y",
"jevmem"
],
"env": {
"TYPESAFE_API_KEY": "<TYPESAFE_API_KEY>"
}
}
}
}.vscode/mcp.json
{
"servers": {
"jevmem": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"jevmem"
],
"env": {
"TYPESAFE_API_KEY": "<TYPESAFE_API_KEY>"
}
}
}
}~/.gemini/settings.json
{
"mcpServers": {
"jevmem": {
"command": "npx",
"args": [
"-y",
"jevmem"
],
"env": {
"TYPESAFE_API_KEY": "<TYPESAFE_API_KEY>"
}
}
}
}claude_desktop_config.json
{
"mcpServers": {
"jevmem": {
"command": "npx",
"args": [
"-y",
"jevmem"
],
"env": {
"TYPESAFE_API_KEY": "<TYPESAFE_API_KEY>"
}
}
}
}.trae/mcp.json
{
"mcpServers": {
"jevmem": {
"command": "npx",
"args": [
"-y",
"jevmem"
],
"env": {
"TYPESAFE_API_KEY": "<TYPESAFE_API_KEY>"
}
}
}
}Environment variables
TYPESAFE_API_KEY
Replace the placeholders with your own credentials and keep them out of version control.