CortexHelper
The customer portal's assistant for installing, configuring and using CortexDB, and for designing memory for your product. What it answers from, its limits, and how to use it from an agent.
CortexHelper answers questions about installing, configuring and using CortexDB, and about how your product should use memory. Its answers come from the docs and the code of the newest release, and an answer that rests on a release says which one.
Open it from the portal's sidebar (CortexHelper), or ask it from a coding agent through the portal's MCP server (below).
What to ask it
Anything you would ask an engineer who knows CortexDB well, for example:
- "How do I keep each customer's memory separate?"
- "How do I upgrade my CortexDB server?"
- "Which settings turn on cited answers, and what do they cost?"
- "Why does my recall come back empty?" (paste the request and the response, without keys)
- "How should my AI product use memory?"
It explains in plain language unless you go technical, leads with the answer and gives commands you can
paste. It names only what customers use: API routes and fields, CORTEX_* settings, CLI commands and SDK
methods. It doesn't show CortexDB's source code.
Commands in answers
Commands in an answer are written from the docs for your release and checked before you see them, for example that a server start includes your license and that a recall asks only for access your credential has. CortexHelper doesn't run them against your server, and each answer with commands says so. Read a command before you run it, and try it on a test server first when it changes data.
Conversations
- Your conversations are kept under Recent conversations; New conversation starts a fresh one.
- A question keeps running on the server if you reload or lose the connection, and the page picks up the answer when you come back.
- Talking about sets what a conversation is about: CortexDB in general, or one of your Scope Studio projects. What you discuss about a project is remembered on that project, and Scope Studio's Discovery and Design read it.
- Start a project turns the conversation into a Scope Studio project, with the conversation carried along, when you are ready to design your memory. Open project goes to the one it is about.
Limits
- Up to 60 questions an hour per account, from the portal and from agents together. Past that, it asks you to try again a little later.
- A question can be up to 2,000 characters from an agent.
- Never paste a key, a license or a token into a question. Replace each with
<redacted>; CortexHelper never needs one.
From a coding agent
With an agent key, connect your coding agent to
https://customer.cortexdb.ai/mcp and use the ask tool with your question:
claude mcp add --transport http cortexdb https://customer.cortexdb.ai/mcp \
--header "Authorization: Bearer $CORTEXDB_KEY"The agent then gets the same answers you would in the portal, with the release they are based on. The same
server's search_docs and get_doc tools read the docs themselves.
When it can't help
If an answer doesn't fix the problem, or something looks broken, open Support in the portal with the error as it is, your server version and what you tried (Getting help).
Agent Keys
Keys that let your coding agents, scripts and pipelines use the customer portal: how to create and revoke them, what they reach, and the portal's MCP tools.
Scope Studio
Design the memory for your product in the customer portal, from a PRD, a repository, a website or a short brief, and get a handover pack your coding agent builds from.