Grok solucortex mcp solucortex_flag_memory
How to: Grok solucortex mcp solucortex_flag_memory
Add solucortex mcp to Grok
-
01
Open .mcp.json (in your project root) and merge this in. Keep any servers already there.
{
"mcpServers": {
"solucortex-mcp": {
"type": "http",
"url": "https://mcp.solucortex.ai/mcp"
}
}
}-
02
Save the file and restart Grok.
-
03
Ask for something solucortex_flag_memory does. Grok lists the server's tools on connect and calls solucortex_flag_memory itself — you do not invoke it by name.
-
04
If nothing happens, check the server is running and that solucortex mcp's identifier in your config matches the one above exactly.
Grok Build reads Claude Code's .mcp.json and Claude Desktop's config unchanged, so a server you have already set up there needs nothing new. The Grok web app and X integration do not take custom servers. Grok docs
Set these first
solucortex mcp will not start until these are set, so solucortex_flag_memory never becomes available.
-
SOLUCORTEX_API_KEY -
SOLUCORTEX_PROJECT_ID
Same tool, other clients
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.