AGENTS.md
+4 −2
https://raw.githubusercontent.com/mnemoverse/mcp-memory-server/HEAD/AGENTS.md
− - Local stdio server: follow `llms-install.md`, which is written for an agent installing on a user's behalf. Ask the user for their key; never invent one and never write a literal `mk_live_` key into a file that gets committed.− Do not edit generated files by hand. They are `server.json`, `manifest.json`, everything under `docs/configs/` and `docs/snippets/`, and the README regions between the `INSTALL_SNIPPETS` and `MORE_CLIENTS` HTML comment markers. A hand edit is overwritten on the next run and fails `verify-configs.yml` in the meantime. If a diff appears in one of these files and `source.json` did not change, discard it.+ - ChatGPT: install the published Mnemoverse Memory plugin and complete browser sign-in. Start with https://mnemoverse.com/docs/api/chatgpt; no local package or custom MCP setup is needed for this route.+ - Local stdio server: follow `llms-install.md`, which is written for an agent installing on a user's behalf. Have the user enter their key in the client's protected settings or a private user-level configuration, not in chat. Never invent a key or write a literal `mk_live_` key into a file that gets committed.+ Do not edit generated files by hand. They are `server.json`, `manifest.json`, everything under `docs/configs/` and `docs/snippets/`, and the README regions between the `INSTALL_SNIPPETS`, `MORE_CLIENTS` and `LOCAL_KEY_SNIPPETS` HTML comment markers. A hand edit is overwritten on the next run and fails `verify-configs.yml` in the meantime. If a diff appears in one of these files and `source.json` did not change, discard it unless it is a regenerated tool-description change in `manifest.json`: the+ After an authorized package release, follow the [wave tracker and deployment checks](CONTRIBUTING.md#the-wave-tracker-what-happens-after-the-release). A successful publication does not prove the docs or hosted connector updated, and does not authorize an otherwise excluded production deployment.