Implementation Guide
The fastest path to adoption is not asking builders to change their whole workflow. MemQ plugs into the MCP-capable clients they already use, then shows value with a simple save, restart, and recall loop.
The editor setup guide includes API-key snippets and config locations by client.
The product page positions MemQ around session continuity, handoffs, and team recall.
The campaign funnel sends technical readers to setup, not to a vague contact form.
Start checkout, create a MemQ API key, paste the MCP config into the client, then ask the agent to store and recall one small decision. That is the minimum first win every builder should see before loading sensitive project context.
Claude and Claude Desktop can use the hosted MCP config.
Cursor and VS Code can use workspace or user-level MCP config.
Codex-style workflows should use API keys for repeatable local and CI sessions.
Good first memories are specific, reusable, and safe: repo conventions, debugging resolutions, release-check commands, architectural decisions, and customer-approved public evidence.
Do not store raw secrets, private keys, sensitive personal data, or customer-private context that has not been approved for the target namespace.
Trial Conversion Path
MemQ's online funnel is built for builders who want a working memory loop before they load real project context. Start checkout, create the API key, paste the MCP config, and test recall in the agent client you already use.