Skip to main content
Glama

Context-First MCP

The MCP server that keeps your AI grounded, coherent, and honest — across every turn.

npm version npm downloads License: MIT MCP Compatible Smithery Glama Node ≥18 TypeScript

npx context-first-mcp

Works instantly with Claude Desktop · Cursor · VS Code · any MCP client · Vercel remote — zero API keys needed.


37 research-backed tools across 7 layers — context health, state, sandboxing, persistent memory, advanced reasoning, truthfulness verification, orchestration, structured research, and autonomous file export. One context_loop call replaces 6–7 individual tools and returns a unified action directive.


Why Your AI Conversations Break Down

Long AI conversations fail in predictable ways. Context-First fixes all four:

Failure Mode

What Goes Wrong

Context-First Solution

Context Drift

AI forgets earlier decisions and intent as the conversation grows

context_loop + detect_drift continuously re-anchor every turn

Silent Contradiction

New inputs silently overrule established facts — the AI doesn't notice

detect_conflicts compares every input against locked ground truth

Vague Execution

AI proceeds on underspecified requirements, producing misaligned output

check_ambiguity + abstention_check ask clarifying questions instead of guessing

Hallucinated Success

Tool outputs look successful but didn't actually achieve the goal

verify_execution rechecks whether the outcome matches the stated intent


Related MCP server: nautilus-compass

What You Get

37 production-ready tools grouped into 7 layers — plus 1 orchestrator that runs them all:

context_loop  ─────────────────────────────────────────────────────────────────
  ├─ Layer 1 · Context Health   (9 tools)   recap, conflict, ambiguity, depth …
  ├─ Layer 2 · Sandbox          (3 tools)   discover_tools, quarantine, merge
  ├─ Layer 3 · Persistent Memory(6 tools)   store, recall, compact, graph …
  ├─ Layer 4 · Advanced Reasoning(5 tools)  InftyThink, Coconut, KAG, MindEvo …
  ├─ Layer 5 · Truthfulness     (7 tools)   NCB, IOE, verify_first, self_critique…
  └─ State + Research Pipeline + Export     (7 tools)

One call. One directive. One score.

{
  "directive": {
    "action": "clarify",
    "contextHealth": 0.62,
    "instruction": "Resolve with the user: (1) Is this a firm requirement? (2) Which framework?",
    "autoExtractedFacts": { "deploy_to": "Vercel" },
    "suggestedNextTools": ["verify_execution", "quarantine_context"]
  }
}

Quick Start

npx — zero install

npx context-first-mcp

Claude Desktop

{
  "mcpServers": {
    "context-first": {
      "command": "npx",
      "args": ["-y", "context-first-mcp"]
    }
  }
}

Cursor / VS Code

{
  "mcp": {
    "servers": {
      "context-first": {
        "command": "npx",
        "args": ["-y", "context-first-mcp"]
      }
    }
  }
}

Remote (Streamable HTTP)

{
  "mcpServers": {
    "context-first": {
      "url": "https://context-first-mcp.vercel.app/api/mcp"
    }
  }
}

Deploy your own Vercel instance

Deploy with Vercel


Tool Reference

Layer 1: Core Context Health (9 tools)

Tool

Purpose

context_loop

One-call orchestrator. Runs 8 stages (ingest→recap→conflict→ambiguity→entropy→abstention→discovery→synthesis) and returns a single directive with action, contextHealth score, extracted facts, and suggested next tools

recap_conversation

Extracts hidden intent, key decisions, and produces consolidated state summaries

detect_conflicts

Compares new input against ground truth; surfaces contradictions

check_ambiguity

Identifies underspecified requirements and generates clarifying questions

verify_execution

Validates whether tool outputs actually achieved the stated goal

entropy_monitor

Proxy-entropy scoring via lexical diversity, contradiction density, hedge frequency, and n-gram repetition (ERGO)

abstention_check

5-dimension confidence scoring — abstains with questions rather than hallucinating (RLAAR)

detect_drift

Detects conversation drift from the original intent

check_depth

Evaluates response depth against question complexity

Layer 1b: State Management (4 tools)

Tool

Purpose

get_state

Retrieve confirmed facts and task status

set_state

Lock in ground truth — subsequent conflict checks run against these values

clear_state

Reset specific keys or all state

get_history_summary

Compressed conversation history with intent annotations

Layer 2: Sandbox & Discovery (3 tools)

Tool

Method

Purpose

discover_tools

MCP-Zero + ScaleMCP

Natural-language tool routing — returns only semantically relevant tools, reducing context bloat by up to 98%

quarantine_context

Multi-Agent Quarantine

Create isolated memory silos for sub-tasks, preventing intent dilution

merge_quarantine

Multi-Agent Quarantine

Merge silo results with noise filtering — only promoted keys return to main context

Layer 3: Persistent Memory (6 tools)

Tool

Purpose

memory_store

Store findings, decisions, and intermediate results with metadata

memory_recall

Retrieve relevant memories by semantic query

memory_compact

Compress and consolidate memory entries

memory_graph

Build and query a knowledge graph from stored memories

memory_inspect

Inspect memory store contents and statistics

memory_curate

Deduplicate and organize memory entries

Layer 4: Advanced Reasoning (5 tools)

Tool

Method

Purpose

inftythink_reason

InftyThink

Infinite-depth reasoning with adaptive stopping

coconut_reason

Coconut

Chain-of-Continuous-Thought in latent space

extracot_compress

ExtraCoT

Compress chain-of-thought while preserving reasoning fidelity

mindevolution_solve

MindEvolution

Evolutionary search over the solution space

kagthinker_solve

KAG-Thinker

Knowledge-augmented generation with structured thinking

Layer 5: Truthfulness & Verification (7 tools)

Tool

Purpose

probe_internal_state

Probe model consistency across paraphrased prompts

detect_truth_direction

Detect whether model reasoning is trending toward or away from truth

ncb_check

Neighborhood consistency check across semantically equivalent inputs

check_logical_consistency

Verify logical coherence of reasoning chains

verify_first

Pre-verification before committing to claims

ioe_self_correct

Intrinsic-extrinsic self-correction

self_critique

Structured self-critique with improvement suggestions

Research Pipeline & Export (2 tools)

Tool

Purpose

research_pipeline

Structured research orchestration across init → gather → analyze → verify → finalize. Covers all 34 underlying tool-equivalents — state, sandboxing, memory, reasoning, truthfulness, context health. Writes files autonomously to disk as the pipeline runs; no LLM cooperation needed for file output.

export_research_files

Writes every verified report chunk and/or every raw evidence batch to disk in a single call.


Built on Peer-Reviewed Research

Every core algorithm traces back to a published paper:

Algorithm

Paper

arXiv

Tool

MCP-Zero

Active Tool Request

2506.01056

discover_tools

ScaleMCP

Semantic Tool Grouping

2505.06416

discover_tools registry

ERGO

Entropy-based Quality

2510.14077

entropy_monitor

RLAAR

Calibrated Abstention

2510.18731

abstention_check

Implementation highlights:

  • Proxy Entropy (ERGO): 4 response-level proxy signals (lexical diversity, contradiction density, hedge-word frequency, n-gram repetition) replace inaccessible token-level logprobs. Composite score above threshold triggers adaptive context reset.

  • TF-IDF Discovery (MCP-Zero): Pure TypeScript, zero external dependencies. Indexes all tool descriptions at startup; cosine similarity routes queries to the top-k relevant tools only.

  • Inference-Time Abstention (RLAAR): 5-dimension confidence scoring replaces the RL training loop. Abstains with targeted questions when confidence < threshold — no hallucination fallback.

Export Helper (1 tool)

Tool

Description

export_research_files

Writes research artifacts directly to disk. It can automatically expand and write every verified report chunk without asking the LLM to loop finalize manually, and it can also write every gathered raw-evidence batch even when verify has not passed.

context_loop Pipeline

context_loop (single MCP tool call)
├── Stage 1: INGEST     — Store messages to session history
├── Stage 2: RECAP      — Extract intents, decisions, summaries
├── Stage 3: CONFLICT   — Detect contradictions against ground truth
├── Stage 4: AMBIGUITY  — Check for underspecified requirements
├── Stage 5: ENTROPY    — Monitor output quality degradation (ERGO)
├── Stage 6: ABSTENTION — Multi-dimensional confidence check (RLAAR)
├── Stage 7: DISCOVERY  — Suggest relevant next tools (MCP-Zero)
└── Stage 8: SYNTHESIS   — Combine signals → action recommendation + LLM directive

Synthesis Priority: abstain > reset > clarify > proceed

Each stage runs with independent error isolation — a failure in one stage doesn't block the others. The result includes per-stage timing, status, and detailed results for observability.

LLM Directive (NEW)

The context_loop response includes a top-level directive object designed for LLM consumption — a compact, actionable instruction that replaces the need to parse nested stage results:

{
  "directive": {
    "action": "clarify",
    "instruction": "Before proceeding, resolve these issues with the user:\n1. Could you specify exactly what you mean?\n2. Is this a firm requirement or still open for discussion?",
    "questions": ["Could you specify exactly what you mean?", "Is this a firm requirement?"],
    "contextHealth": 0.62,
    "autoExtractedFacts": { "framework": "React", "deploy_to": "Vercel" },
    "suggestedNextTools": ["verify_execution", "quarantine_context"]
  }
}

How context_loop Works

context_loop (single MCP tool call)
├── Stage 1: INGEST     — Store messages to session history
├── Stage 2: RECAP      — Extract intents, decisions, summaries
├── Stage 3: CONFLICT   — Detect contradictions against ground truth
├── Stage 4: AMBIGUITY  — Check for underspecified requirements
├── Stage 5: ENTROPY    — Monitor output quality degradation (ERGO)
├── Stage 6: ABSTENTION — Multi-dimensional confidence check (RLAAR)
├── Stage 7: DISCOVERY  — Suggest relevant next tools (MCP-Zero)
└── Stage 8: SYNTHESIS  — Combine signals → action + directive

Synthesis priority: abstain > reset > clarify > proceed

Each stage runs with independent error isolation. The directive response field carries everything an LLM needs:

Field

Description

action

proceed · clarify · reset · abstain

instruction

Plain-language guidance for the LLM's next step

questions

Aggregated clarifying questions (ambiguity + abstention + conflicts)

contextHealth

0–1 composite score. 1 = healthy, 0 = degraded

autoExtractedFacts

Key-value facts auto-extracted from user messages and stored as ground truth

suggestedNextTools

Relevant tools the LLM should consider next

Smart defaults: currentInput is auto-inferred from the last user message. Facts like "use React" are extracted and stored automatically.


Usage Protocol: Getting the Most from Context-First

The #1 mistake: LLMs treat context_loop as optional. It's not — it's the backbone.

Built-in Enforcement (v1.2.1+)

The server ships with four compliance mechanisms that require zero configuration:

  1. Server Instructions — Full usage protocol injected at MCP handshake via ServerOptions.instructions

  2. Bootstrap Gate — First non-context_loop call appends a strong redirect reminder

  3. Cross-Tool Reminders — After 3 consecutive calls without context_loop, reminders appear in tool responses

  4. MCP Prompts — context-first-protocol and research-protocol prompt templates available on demand

Reinforce in Your System Prompt (Optional)

When using Context-First MCP:
1. Call context_loop BEFORE any complex task
2. Call context_loop every 2–3 tool calls
3. Call context_loop AFTER generating long-form output
4. ALWAYS follow directive.action (proceed/clarify/reset/abstain/deepen/verify)
5. Use memory_store to save findings; memory_recall to retrieve them

Research Task Workflow

research_pipeline orchestrates memory, phase control, reasoning, and autonomous file writing. It is not a web crawler — bring your own sources from web search, GitHub, fetch tools, PDFs, or any other MCP.

Phase 1 · Init     research_pipeline(init) → sets up state, enables autonomous file writing
Phase 2 · Gather   ONE web search → research_pipeline(gather) → file written to disk → repeat
Phase 3 · Analyze  research_pipeline(analyze) → reasoning engines produce clean analysis file
Phase 4 · Verify   research_pipeline(verify) → context health gate (non-blocking)
Phase 5 · Finalize research_pipeline(finalize) → synthesis.md + all batch files on disk

Automation shortcut:
  export_research_files(outputDir, exportVerifiedReport=true)  → write all report chunks
  export_research_files(outputDir, exportRawEvidence=true)     → write all evidence batches

Autonomous file writing is always on. Files are written to ./context-first-research-output/ by default — no LLM cooperation required. Pass outputDir to override.


Architecture

┌──────────────────────────────────────────────────────────────┐
│               @xjtlumedia/context-first-mcp-server            │
│                     (Core — shared logic)                     │
│                                                               │
│  Layer 1: Context Health    (9 tools)                         │
│  Layer 2: Sandbox           (3 tools)                         │
│  Layer 3: Persistent Memory (6 tools)                         │
│  Layer 4: Advanced Reasoning(5 tools)                         │
│  Layer 5: Truthfulness      (7 tools)                         │
│  State (4) · Orchestrator · Pipeline · Export                 │
└──────────────┬───────────────────────┬──────────────────────┘
               │                       │
        ┌──────▼──────┐         ┌──────▼────────┐
        │ stdio-server │         │ remote-server │
        │ (npx local)  │         │   (Vercel)    │
        │   stdio      │         │ Streamable    │
        │  37 tools    │         │    HTTP       │
        └──────────────┘         │   37 tools    │
                                 └───────────────┘
  • Core library (@xjtlumedia/context-first-mcp-server): All tool implementations. Zero external API keys — heuristic-based by default.

  • stdio-server (context-first-mcp): npx entry point, stdio transport, 37 tools.

  • remote-server: Vercel serverless, Streamable HTTP transport, 37 tools.


Frontend Demo

Try all 37 tools live in your browser at context-first-mcp.vercel.app.


Development

git clone https://github.com/XJTLUmedia/Context-First-MCP.git
cd Context-First-MCP
pnpm install

# Build everything
pnpm build

# Run stdio server
cd packages/stdio-server && pnpm start

# Run frontend
cd packages/frontend && pnpm dev

# Tests
pnpm test

Contributing

See CONTRIBUTING.md.

License

MIT


Context-First MCP · @xjtlumedia/context-first-mcp-server · context-first-mcp

Built for every developer tired of watching their AI lose the plot.

Available Tools

8 tools
context_healthA

[CONTEXT & STATE] 13 sub-tools: recap, conflict, ambiguity, verify, entropy, abstention, grounding, drift, depth, get_state, set_state, clear_state, history. Auto-selects based on params or use 'check' to override. TIP: context_loop runs all health checks automatically — prefer context_loop for comprehensive analysis, use context_health for targeted checks.

Inputs: sessionId, check, params.

context_loopA

[ORCHESTRATOR — CALL THIS FIRST] CALL THIS TOOL every 2-3 turns and at the start of ANY task. It is the single most important tool — it replaces calling recap, conflict, ambiguity, entropy, grounding, drift, depth, and discovery tools individually.

What it does: Runs ALL context health checks in one call. Auto-extracts facts from conversation, detects contradictions, checks answer quality, and tells you exactly what to do next.

Returns a 'directive' object with:

  • action: proceed | clarify | reset | abstain | deepen | verify

  • instruction: Plain English telling you what to do

  • contextHealth: 0-1 score

  • autoExtractedFacts: Key facts pulled from conversation

  • suggestedNextTools: What tools to call next

  • constraints: Machine-readable rules you must follow

ESSENTIAL for: research tasks, multi-step workflows, long conversations, preserving context across turns, knowledge management, and any task requiring memory or fact-checking.

Minimal call: { "messages": [{"role":"user","content":"","turn":1}] } — most fields have smart defaults.

Inputs: sessionId, messages, currentInput, claim, +4 more.

export_research_filesA

[EXPORT] Automatically writes research artifacts to disk. It can expand and write every verified report chunk without asking the LLM to loop finalize manually, and it can also write every gathered raw-evidence batch even when verify has not passed yet.

Inputs: outputDir (required), sessionId, baseFileName, exportVerifiedReport, +4 more.

memoryB

[MEMORY] 6 sub-tools: store (hierarchical ingest), recall (adaptive gate retrieval), compact (compress with integrity), graph (knowledge graph with PageRank), inspect (tier status), curate (importance-based curation). Auto-selects based on params or use 'action' to override. TOOL NAME: memory (use underscores).

Inputs: sessionId, action, params.

reasonA

[REASONING] 5 engines: inftythink (iterative bounded reasoning), coconut (multi-perspective latent analysis), extracot (reasoning chain compression), mindevolution (evolutionary search), kagthinker (structured logical decomposition with dependency DAG). Auto-selects based on params or use 'method' to override.

Inputs: sessionId, method, params.

research_pipelineA

[PIPELINE] RECOMMENDED for research tasks. Orchestrates all underlying Context-First layers through 6 phases (init→gather→review→analyze→verify→finalize). NEW: plan→draft→review→fix loop — like compile→test→fix in coding. Init generates a research outline (12+ sections). Each gather adds depth to one section with quality gate (25K char / 500 line min — multiple gathers per section expected). Review runs quality tests and identifies gaps. CRITICAL: Interleave web search and gather — after EACH search, IMMEDIATELY call gather with deeply written content. Do NOT batch searches. Each gather writes a file to disk. After sufficient gathers, call review to run quality tests. Fix failed sections by gathering again with metadata.targetSection=N. Coverage must reach 60% before analyze. Autonomous file writing is ALWAYS ON — files are written to disk during gather, analyze, and finalize phases. Provide outputDir to control destination, or let the pipeline auto-create a temp directory. Finalize works even if verify hasn't passed. It does not browse the web or invent source material for you; use it to structure, preserve, pressure-test, and export sourced findings collected from web, GitHub, fetch, or other MCP tools.

Inputs: phase (required), content (required), sessionId, outputDir, +4 more.

sandboxA

[SANDBOX] 3 sub-tools: discover (semantic tool search via TF-IDF), quarantine (isolated state sandbox), merge (merge/discard silo). Auto-selects based on params or use 'action' to override.

Inputs: sessionId, action, params.

truthcheckA

[TRUTHFULNESS] 7 tools: probe (linguistic truth signals), truth_direction (truth vector projection), ncb (perturbation robustness), logic (formal logical consistency), verify_first (5-dimension verification), ioe (confidence-based correction), self_critique (iterative refinement). Auto-selects or use 'check' to override. Set cascade=true for auto-correction on low scores.

Inputs: sessionId, check, cascade, params.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.7/5.0

    Scored across 8 tools

    Disambiguation3/5

    The tools have distinct high-level purposes (e.g., context management, memory, reasoning, research), but the sub-tools within each main tool (like context_health's 13 sub-tools or memory's 6 sub-tools) create significant internal overlap and ambiguity. For example, context_health and context_loop both handle context checks, with context_loop described as replacing many individual checks, which could confuse an agent about when to use each. The auto-selection features mitigate this somewhat, but the boundaries between tools like context_health, context_loop, and truthcheck are not clearly defined, leading to potential misselection.

    Naming Consistency2/5

    The naming is inconsistent across tools, with a mix of styles: some use snake_case (context_health, context_loop, export_research_files), others use single words (memory, reason, sandbox, truthcheck), and research_pipeline uses a hybrid format. There is no predictable verb_noun pattern, and the sub-tools within each main tool further add to the inconsistency (e.g., inftythink vs. extracot in reason). While the names are readable, the lack of a uniform convention makes the set harder to navigate and predict.

    Tool Count4/5

    With 8 main tools, the count is reasonable for a server focused on context management and research workflows, as it covers key areas like health checks, memory, reasoning, and pipeline orchestration. However, the extensive sub-tools (e.g., 13 in context_health) make the effective surface larger, which could feel heavy but is justified by the server's complex domain. The count is slightly high but still appropriate given the scope, avoiding extreme over- or under-provisioning.

    Completeness5/5

    The tool set provides comprehensive coverage for context-aware AI tasks, including context health monitoring (context_health, context_loop), memory storage and retrieval (memory), reasoning engines (reason), research pipeline management (research_pipeline), truth verification (truthcheck), sandboxing (sandbox), and export functionality (export_research_files). There are no obvious gaps; it supports full lifecycle operations from initialization to analysis and export, with tools like context_loop and research_pipeline ensuring no dead ends in workflows. The domain is well-covered with tools that interlock effectively.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      D
      maintenance
      Automatically saves and retrieves AI conversation sessions to maintain context continuity, preventing re-explaining architecture decisions.
      4
      25 npm
      6
      Creative Commons Attribution Non Commercial 4.0 International
    • A
      license
      Not graded
      quality
      C
      maintenance
      A visual canary that detects context rot and silent model degradation in long agent conversations by embedding externally verified checkpoints and self-reported status into each response.
      7 npm
      MIT