pypi solucortex-mcpstreamable-httpMITupdated 11d ago
Official Model Context Protocol server for SoluCortex โ living technical memory for AI agents.
What can you do with solucortex mcp?
SoluCortex MCP
Official Model Context Protocol server for SoluCortex โ living technical memory for AI agents.
Connect any MCP-compatible agent (Claude Code, Claude Desktop, Cursor, Codex, Cline, โฆ) to your SoluCortex project so it can recall the decisions, conventions, risks and architecture that matter before it works, and remember what it learns when it's done.
Website: solucortex.ai ยท
Setup guide: solucortex.ai/docs/mcp ยท
Tools reference: solucortex.ai/docs/mcp-tools ยท
PyPI: solucortex-mcp ยท
MCP Registry: io.github.soluai-spa/solucortex-mcp
Tools
| Tool | What it does | When to use |
|---|---|---|
solucortex_recall |
Builds living context for a task (ranked by semantic similarity + importance) | At the start of a task, before touching code |
solucortex_search |
Ad-hoc semantic search over the project's memories | Specific questions mid-task |
solucortex_remember |
Records a memory (stored approved + traced as an authorized agent) |
At close, or on a relevant technical decision |
solucortex_list_memories |
Lists memories without semantic search | Quick inspection / audit |
Requirements
- A SoluCortex account and a project API key (prefix
scx_) โ get it from your SoluCortex dashboard. - One of:
uv(recommended), Python โฅ 3.10, or Docker.
Configuration
stdio mode (default, local)
The server is configured entirely through environment variables:
| Variable | Required | Description |
|---|---|---|
SOLUCORTEX_API_KEY |
โ | Project API key (scx_โฆ) |
SOLUCORTEX_PROJECT_ID |
optional | Default project UUID; if omitted, the backend infers it from the API key |
SOLUCORTEX_URL |
optional | API base URL. Default https://solucortex.ai |
HTTP mode (remote, multi-tenant)
Run with MCP_TRANSPORT=http (or --http) to serve Streamable HTTP on $PORT
(default 8080) โ the mode behind https://mcp.solucortex.ai. Credentials travel with
each request and the environment is ignored:
| Header | Required | Description |
|---|---|---|
Authorization: Bearer scx_โฆ |
โ | The caller's project API key (401 without it) |
X-Solucortex-Project |
optional | Default project UUID; if omitted, the backend infers it from the API key |
GET /health (and /healthz locally; Cloud Run's frontend intercepts /healthz) responds without auth. The MCP endpoint is
/mcp, runs stateless, and shares nothing between requests/tenants.
Never commit your API key. Keep it in your MCP client config's env block or a local .env
(see .env.example).
Install
Remote (recommended โ nothing to install)
The hosted server at https://mcp.solucortex.ai/mcp speaks Streamable HTTP; your key
travels with each request:
claude mcp add --transport http solucortex https://mcp.solucortex.ai/mcp \
--header "Authorization: Bearer scx_xxx" \
--header "X-Solucortex-Project: your-project-uuid"
Or in any client with remote MCP support:
{
"mcpServers": {
"solucortex": {
"type": "http",
"url": "https://mcp.solucortex.ai/mcp",
"headers": {
"Authorization": "Bearer scx_xxx",
"X-Solucortex-Project": "your-project-uuid"
}
}
}
}
Claude Code (local, stdio)
claude mcp add solucortex \
-e SOLUCORTEX_API_KEY=scx_xxx \
-e SOLUCORTEX_PROJECT_ID=your-project-uuid \
-- uvx solucortex-mcp
Claude Desktop / Cursor / Cline (JSON config)
Add to the client's MCP config (claude_desktop_config.json, Cursor mcp.json, etc.):
{
"mcpServers": {
"solucortex": {
"command": "uvx",
"args": ["solucortex-mcp"],
"env": {
"SOLUCORTEX_API_KEY": "scx_xxx",
"SOLUCORTEX_PROJECT_ID": "your-project-uuid"
}
}
}
}
From a local clone
git clone https://github.com/soluai-spa/solucortex-mcp
cd solucortex-mcp
cp .env.example .env # fill in your key
./run.sh # loads .env, then runs via uv
# or, with SOLUCORTEX_* already exported: uv run solucortex-mcp
Docker
Prebuilt image on GHCR:
docker run --rm -i \
-e SOLUCORTEX_API_KEY=scx_xxx \
ghcr.io/soluai-spa/solucortex-mcp:latest
Or build it yourself:
docker build -t solucortex-mcp .
docker run --rm -i \
-e SOLUCORTEX_API_KEY=scx_xxx \
-e SOLUCORTEX_PROJECT_ID=your-project-uuid \
solucortex-mcp
The server speaks MCP over stdio, so clients launch it as a subprocess (-i keeps stdin open).
Development
uv sync
uv run solucortex-mcp # run (stdio)
MCP_TRANSPORT=http uv run solucortex-mcp # run (HTTP on :8080)
uv run pytest # test suite
npx @modelcontextprotocol/inspector uv run solucortex-mcp # interactive test
Notes
- Memory
typevocabulary: the canonical set isarchitecture, decision, risk, convention, bug_history, tech_debt, sensitive_module, learning, external_integration. Some backends accept an older set (technical_decision, historical_bug, current_state, task_closure). The server passestypethrough and surfacesHTTP 422so you can retry with the other set. - Never store real secrets in a memory. Record location, type, severity and action taken instead.
License
MIT โ see LICENSE.
Install
Add solucortex mcp to your client. Pick the one you use.
{
"servers": {
"solucortex-mcp": {
"type": "http",
"url": "https://mcp.solucortex.ai/mcp"
}
}
}Add to `.vscode/mcp.json` in your workspace.
claude mcp add solucortex-mcp -- uvx solucortex-mcpcodex mcp add solucortex-mcp -- uvx solucortex-mcpamp mcp add solucortex-mcp -- uvx solucortex-mcp{
"mcpServers": {
"solucortex-mcp": {
"command": "uvx",
"args": [
"solucortex-mcp"
]
}
}
}Add to `claude_desktop_config.json`, then restart Claude Desktop.
{
"mcpServers": {
"solucortex-mcp": {
"command": "uvx",
"args": [
"solucortex-mcp"
]
}
}
}Add to `~/.cursor/mcp.json`, or `.cursor/mcp.json` for a single project.
{
"mcpServers": {
"solucortex-mcp": {
"command": "uvx",
"args": [
"solucortex-mcp"
]
}
}
}Add to `~/.codeium/windsurf/mcp_config.json`.
{
"mcpServers": {
"solucortex-mcp": {
"command": "uvx",
"args": [
"solucortex-mcp"
]
}
}
}Add to `cline_mcp_settings.json` via the MCP Servers panel.
{
"mcpServers": {
"solucortex-mcp": {
"command": "uvx",
"args": [
"solucortex-mcp"
]
}
}
}Add to `~/.gemini/settings.json`.
{
"mcpServers": {
"solucortex-mcp": {
"type": "local",
"command": "uvx",
"args": [
"solucortex-mcp"
],
"tools": [
"*"
]
}
}
}Add to `~/.copilot/mcp-config.json`, or run `/mcp add` inside the CLI.
{
"context_servers": {
"solucortex-mcp": {
"command": {
"path": "uvx",
"args": [
"solucortex-mcp"
]
}
}
}
}Add to your Zed `settings.json`.
uvx solucortex-mcpRun `goose configure`, choose **Add Extension โ Command-line Extension**, and paste this command.
4 tools
solucortex mcp exposes 4 tools to a connected agent.
- solucortex_recall
- Builds living context for a task (ranked by semantic similarity + importance)
- solucortex_search
- Ad-hoc semantic search over the project's memories
- solucortex_remember
- Records a memory (stored `approved` + traced as an authorized agent)
- solucortex_list_memories
- Lists memories without semantic search
Score
81 / 100
Excellent
- Documentation25/25
- Maintenance19/25
- Trust16/20
- Capability6/15
- Install experience15/15
- Documents what it does and how to connect
- Has a resolvable package or endpoint
- Exposes at least one tool, prompt or resource
- README has substantive content
- Includes a code example
- Documents its configuration
- Mentions credentials or security posture
- Last commit 4 days ago
- Has a release history
- Repository is not archived
- Licensed MIT
- Namespace verified in the official MCP registry
- Claimed by its owner
- Published under an organisation
- 4 tool(s) documented
- Provides prompt templates
- Provides resources
- 18 documented install method(s)
- Published to a package registry
- Offers a hosted endpoint โ no local install
Version history
| Versions | Published |
|---|---|
| 1.0.0Latest | Aug 26, 2026 |