Context7
Feeds AI the latest docs for libraries and frameworks before it answers, so code it writes does not use outdated, removed functions.
Description from the maker (original English)
Agent reasoning, memory, and token-optimized context for AI applications.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
NOCTURNUSAI_URL, NOCTURNUSAI_API_KEY, NOCTURNUSAI_DATABASE, NOCTURNUSAI_TENANTValues marked secret are keys to your account. Never share them or paste them into a chat.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"logic": {
"command": "npx",
"args": [
"-y",
"nocturnusai-mcp"
],
"env": {
"NOCTURNUSAI_URL": "your-value",
"NOCTURNUSAI_API_KEY": "your-value",
"NOCTURNUSAI_DATABASE": "your-value",
"NOCTURNUSAI_TENANT": "your-value"
}
}
}
}Run this in your terminal
claude mcp add logic --env NOCTURNUSAI_URL=your-value --env NOCTURNUSAI_API_KEY=your-value --env NOCTURNUSAI_DATABASE=your-value --env NOCTURNUSAI_TENANT=your-value -- npx -y nocturnusai-mcpFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"logic": {
"command": "npx",
"args": [
"-y",
"nocturnusai-mcp"
],
"env": {
"NOCTURNUSAI_URL": "your-value",
"NOCTURNUSAI_API_KEY": "your-value",
"NOCTURNUSAI_DATABASE": "your-value",
"NOCTURNUSAI_TENANT": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"logic": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"nocturnusai-mcp"
],
"env": {
"NOCTURNUSAI_URL": "your-value",
"NOCTURNUSAI_API_KEY": "your-value",
"NOCTURNUSAI_DATABASE": "your-value",
"NOCTURNUSAI_TENANT": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
NOCTURNUSAI_URL envNOCTURNUSAI_DATABASE envNOCTURNUSAI_TENANT envThese settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026
The registry name was verified against the domain nocturnus.ai (the registry checks domain ownership)
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
You need to fill in: NOCTURNUSAI_API_KEY
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (0.3.11) reached the registry 7 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: Context7, Codebase Memory, Exa
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Feeds AI the latest docs for libraries and frameworks before it answers, so code it writes does not use outdated, removed functions.
Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.
Connect AI agents to Exa for web search, content fetching, and multi-step research.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
The context engineering engine for AI agents: send only what changed.
# ❌ Without NocturnusAI — replay everything, every turn
messages = system_prompt + full_history + tool_outputs # ~1,259 tokens/turn response = llm(messages) # $13,600/mo at scale
ctx = nocturnus.process_turns(raw_turns) # extract → infer → delta messages = system_prompt + ctx.briefing_delta # ~221 tokens/turn response = llm(messages) # $2,400/mo. Same accuracy.
Measured on live APIs. 15-turn product support conversation. Real usage.input_tokens counts. Run it yourself.
| Naive replay | RAG-optimized | NocturnusAI | |
|---|---|---|---|
| Tokens per turn | ~1,259 | ~800 | ~221 |
| Cost per month (1K req/hr, Opus 4, $15/1M) | $13,600 | $12,000 | $2,400 |
| Latency | high | medium | low |
| Truth-preserving | no | no | yes |
Claude Opus 4: 5.7× reduction. Gemini 2.0 Flash: 10.0×. Full calculations.
pip install nocturnusai # Python
npm install nocturnusai-sdk # TypeScript docker run -p 9300:9300 ghcr.io/auctalis/nocturnusai:latest # Docker
Or use the setup wizard:
curl -fsSL https://raw.githubusercontent.com/Auctalis/nocturnusai/main/install.sh | bash
| Framework | Integration | Link |
|---|---|---|
| LangChain / LangGraph | Drop-in NocturnusContextProvider, LangSmith trace pass-through | Docs |
| CrewAI | Task-scoped context per agent role | Docs |
| AutoGen | Context server callable by any agent | Docs |
| MCP | Spec-compliant server for Claude Desktop, Cursor, Continue | Config |
| OpenAI Agents SDK | Context middleware, no tool modifications | Docs |
| Vercel AI SDK | Edge-compatible adapter for Next.js, Nuxt, SvelteKit | Docs |
| Python SDK | pip install nocturnusai | Docs |
| TypeScript SDK | npm install nocturnusai-sdk | Docs |
Three steps. Every turn.
briefingDelta containing only what changed since the last turnThis is not vector search. It is not summarization. It is deterministic inference on a logic engine — Hexastore indexing, backward chaining, and truth maintenance.
LLM required for natural-language turns. The examples below send raw text turns through an LLM to extract structured facts. If you start the server without an LLM provider, natural-language turns will return zero facts. See Quick Start for setup options, or use predicate syntax (e.g.,
"customer_tier(acme_corp, enterprise)") which works without any LLM.
POST /contextcurl -X POST http://localhost:9300/context \
-H 'Content-Type: application/json' \ -H 'X-Tenant-ID: default' \ -d '{ "turns": [ "user: Customer says they are enterprise and blocked on SLA credits.", "tool: CRM says account is Acme Corp with a 2M ARR contract.", "agent: Last week support promised to review SLA eligibility.", "tool: Billing note says renewal is due next month." ], "maxFacts": 12 }'
POST /memory/contextcurl -X POST http://localhost:9300/memory/context \
-H 'Content-Type: application/json' \ -H 'X-Tenant-ID: default' \ -d '{ "goals": [{"predicate":"eligible_for_sla","args":["acme_corp"]}], "maxFacts": 12, "sessionId": "ticket-42" }'
POST /context/diffcurl -X POST http://localhost:9300/context/diff \
-H 'Content-Type: application/json' \ -H 'X-Tenant-ID: default' \ -d '{"sessionId": "ticket-42", "maxFacts": 12}'
Returns only added and removed entries between snapshots.
POST /context/session/clearcurl -X POST http://localhost:9300/context/session/clear \
-H 'Content-Type: application/json' \ -H 'X-Tenant-ID: default' \ -d '{"sessionId":"ticket-42"}'
Python SDK
from nocturnusai import SyncNocturnusAIClient
with SyncNocturnusAIClient("http://localhost:9300") as client: ctx = client.process_turns( turns=[ "user: Customer says they are enterprise and blocked on SLA credits.", "tool: CRM says account is Acme Corp with a 2M ARR contract.", ], scope="ticket-42", session_id="ticket-42", )
diff = client.diff_context(session_id="ticket-42", max_facts=12) client.clear_context_session("ticket-42")
print(ctx.briefing_delta)
TypeScript SDK
import { NocturnusAIClient } from 'nocturnusai-sdk';
const client = new NocturnusAIClient({ baseUrl: 'http://localhost:9300', tenantId: 'default', });
const ctx = await client.processTurns({ turns: [ 'user: Customer says they are enterprise and blocked on SLA credits.', 'tool: CRM says account is Acme Corp with a 2M ARR contract.', ], scope: 'ticket-42', sessionId: 'ticket-42', });
const diff = await client.diffContext({ sessionId: 'ticket-42', maxFacts: 12 }); await client.clearContextSession('ticket-42'); console.log(ctx.briefingDelta);
MCP
{
"mcpServers": { "nocturnus": { "url": "http://localhost:9300/mcp/sse", "transport": "sse" } } }
Use the context tool each turn for a salience-ranked working set. Pair MCP with the HTTP context endpoints when you need goal-driven assembly and diffs.
When you do need backend mechanics, NocturnusAI provides them:
ttl, validFrom, and validUntilX-Database and X-Tenant-IDdocker run -d --name nocturnusai -p 9300:9300 \
--restart unless-stopped \ -v nocturnusai-data:/data \ ghcr.io/auctalis/nocturnusai:latest
curl http://localhost:9300/health # Verify it's running
docker run -d --name nocturnusai -p 9300:9300 \
--add-host=host.docker.internal:host-gateway \ -e LLM_PROVIDER=ollama \ -e LLM_MODEL=granite3.3:8b \ -e LLM_BASE_URL=http://host.docker.internal:11434/v1 \ -e EXTRACTION_ENABLED=true \ ghcr.io/auctalis/nocturnusai:latest
make up-ollama && make smoke
nocturnusai # Interactive REPL
nocturnusai -e "context 10" # Salience-ranked working set nocturnusai -e "compress" # POST /memory/compress nocturnusai -e "cleanup 0.05" # POST /memory/cleanup
Full docs: [nocturnus.ai](https://nocturnus.ai)
| Start Here | The turn-reduction workflow |
| Context Workflow | Raw turns → optimize → diff → clear |
| API Reference | REST endpoints and response shapes |
| SDKs | Python and TypeScript client methods |
| Integrations | LangChain, CrewAI, AutoGen, MCP, and more |
| Benchmark | Measured token reduction on live APIs |
| Calculations | Every number, derived |
| How It Works | The extraction → inference → delta pipeline |
git clone https://github.com/Auctalis/nocturnusai.git && cd nocturnusai
make up # Server using .env.example defaults make up-ollama # + Ollama (reuses host or starts bundled) make up-monitoring # + Prometheus + Grafana make smoke # Verify health + context endpoint
Requires JDK 17+.
./gradlew :nocturnusai-server:run # HTTP server on :9300
./gradlew :nocturnusai-cli:run # Interactive REPL (JVM) ./gradlew :nocturnusai-cli:nativeCompile # Build native binary ./gradlew test # Full test suite
See CONTRIBUTING.md. Issues labelled good first issue are good entry points.
Report vulnerabilities privately via GitHub Security Advisories. See SECURITY.md.
Business Source License 1.1 (SPDX: BUSL-1.1). Free for internal use — including internal production — inside your own organization. Offering NocturnusAI or substantial functionality as a product/hosted service to third parties requires a commercial license (licensing@nocturnus.ai). Converts to Apache 2.0 on 2030-02-19. See LICENSE and DISCLAIMER.md.
Only the beginning is shown; read the rest in the repo