solucortex-mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | Port to use when MCP_TRANSPORT is http. Defaults to 8080. | 8080 |
| MCP_TRANSPORT | No | Transport mode: stdio (default, local) or http (Streamable HTTP on $PORT). In http mode, credentials travel with each request and the environment is ignored. | stdio |
| SOLUCORTEX_URL | No | API base URL. Defaults to https://solucortex.ai | https://solucortex.ai |
| SOLUCORTEX_API_KEY | No | Project API key (prefix scx_) for SoluCortex. Required for stdio mode. | |
| SOLUCORTEX_PROJECT_ID | No | Default project UUID. If omitted, the backend infers it from the API key. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| solucortex_recallA | Build living context for a task (POST /context/build). Call this at the START of a task, before touching code: returns approved, active memories (decisions, conventions, risks, sensitive modules, architecture) ranked by semantic similarity + importance. Uses OpenAI embeddings (slower, 20 req/min). |
| solucortex_searchA | Ad-hoc semantic search of memories (POST /search/semantic). Use for specific questions during a task (e.g. 'how is authentication implemented?'), distinct from recall which builds the full startup context. Uses OpenAI embeddings (20 req/min). |
| solucortex_rememberA | Record a memory in SoluCortex (POST /memories). Call when closing a task or making a relevant technical decision. As an authorized agent (Bearer api_key), the memory is stored with status 'approved' and traced. Never store real secrets: if you find one, record location/type/severity and action taken, with a redacted reference. |
| solucortex_list_memoriesA | List the project's memories without semantic search (GET /memories). Useful for quick inspection/audit or to confirm a just-created memory was stored. Does not consume OpenAI quota. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Mostly distinct: recall and search both perform semantic retrieval, but their use cases are clearly separated (start-of-task context building vs. ad-hoc queries). list_memories and remember are unambiguously different. The overlap is minor and well-documented.
All tools share the solucortex_ prefix and use lowercase snake_case, but the naming convention is mixed: recall, search, and remember are single verbs, while list_memories includes an object. Consistent enough to be predictable.
Four tools cover the core memory interactions (list, recall, search, record) without unnecessary bloat. The count is well-scoped for a memory-oriented MCP server.
The set provides create and multiple read/search paths, but lacks update/delete or memory-status management. This creates a moderate lifecycle gap, though the primary agent workflows (build context, ask questions, record decisions) are covered.