MCPgee
MCPgee
MCPgeeMCPgee

Context Engine

v1.0.0•Developer Tools•stable

Context-Engine MCP - Agentic Context Compression Suite

aiai-agentscodexcompressioncontext
Share:
392
Stars
0
Downloads
0
Weekly
0/5
View on GitHub

What is Context Engine?

Context Engine is a Model Context Protocol (MCP) server that allows AI assistants like Claude, Cursor, and VS Code to context-engine mcp - agentic context compression suite

Context-Engine MCP - Agentic Context Compression Suite

This server falls under the Developer Tools category on MCPgee, the world's largest MCP server directory with 33,000+ servers.

Features

  • Context-Engine MCP - Agentic Context Compression Suite

Use Cases

Agentic context compression
Token optimization
Codex and Cursor integration
Context-Engine-AI

Maintainer

LicenseNOASSERTION
Languagesvelte
Versionv1.0.0
UpdatedMay 16, 2026
Statushealthy
Maintenanceactive

Works with

ClaudeOpenAIwindowsmacoslinux
View SourceBrowse All Servers

Installation

Manual Installation

npx context-engine

Configuration

Configuration Details

Config File

claude_desktop_config.json

Performance

Response Metrics

Response Time< 200ms
ThroughputMedium

Resource Usage

Memory UsageLow
CPU UsageLow

How to Set Up and Use Context Engine

Context Engine is an agentic context compression suite that connects your AI coding assistant to a cloud-indexed version of your codebase, exposing 30+ MCP tools for semantic search, symbol graph navigation, cross-repo tracing, and persistent memory. It routes queries to the best backend — semantic search, Q&A, symbol graph, or git history — automatically. Teams use it to slash token usage by up to 75% through batch operations while giving AI assistants a much deeper, more accurate understanding of large codebases than context alone can provide.

Prerequisites

  • Node.js 18+ installed (for the CLI bridge)
  • A Context Engine account at context-engine.ai (API key required)
  • Claude Desktop, Claude Code, Cursor, or another MCP-compatible client
  • Your codebase uploaded/indexed via the VS Code extension or CLI
1

Sign up and get your API key

Create an account at context-engine.ai. After signing in, navigate to Settings to find your API key. You will need this key when connecting the CLI bridge to your workspace.

2

Install the MCP bridge CLI

Install the Context Engine MCP bridge globally via npm. This package provides the `ctxce` command used to authenticate, index your workspace, and serve the MCP endpoint.

npm install -g @context-engine-bridge/context-engine-mcp-bridge
3

Connect and index your workspace

Run the connect command with your API key and the path to your repository. The --daemon flag keeps the bridge running in the background and watches for file changes.

ctxce connect <your-api-key> --workspace /path/to/repo --daemon
4

Verify daemon status

Check that the background daemon is running correctly before configuring your MCP client. Use ctxce status to confirm it is active and ctxce mcp-serve to test stdio mode.

ctxce status
5

Configure your MCP client

Add Context Engine to your claude_desktop_config.json (or equivalent MCP config). The server runs in stdio mode via ctxce mcp-serve.

{
  "mcpServers": {
    "context-engine": {
      "command": "ctxce",
      "args": ["mcp-serve"]
    }
  }
}
6

Copy the skill file for Claude Code

For Claude Code specifically, copy the bundled skill definition into your project's .claude directory so the assistant knows how to use the 30+ tools exposed by the server.

cp -r skills/context-engine/ your-project/.claude/

Context Engine Examples

Client configuration

Add Context Engine to Claude Desktop's mcpServers configuration to enable all 30+ code intelligence tools.

{
  "mcpServers": {
    "context-engine": {
      "command": "ctxce",
      "args": ["mcp-serve"]
    }
  }
}

Prompts to try

Once connected, you can ask Claude to search your codebase, trace symbols, or recall past session context.

- "Find all callers of the processPayment function across the entire repo"
- "Search my codebase for how we handle rate limiting in the API layer"
- "Show me the git history for src/auth/token.ts and explain the recent changes"
- "Find all classes that extend BaseController and list their method signatures"
- "Search commits for when we removed the legacy caching logic"

Troubleshooting Context Engine

ctxce command not found after npm install

Ensure your global npm bin directory is on your PATH. Run `npm bin -g` to find the path and add it to your shell profile (e.g., export PATH="$(npm bin -g):$PATH" in ~/.zshrc).

MCP tools return no results for searches

The workspace must be indexed before search works. Run `ctxce connect <api-key> --workspace /path/to/repo` and wait for initial indexing to complete. Check daemon logs at ~/.context-engine/daemon.log for indexing progress.

Daemon stops after terminal closes

Use the --daemon flag when connecting: `ctxce connect <api-key> --workspace /path/to/repo --daemon`. This detaches the process. Verify with `ctxce status`.

Frequently Asked Questions about Context Engine

What is Context Engine?

Context Engine is a Model Context Protocol (MCP) server that context-engine mcp - agentic context compression suite It connects AI assistants to external tools and data sources through a standardized interface.

How do I install Context Engine?

Follow the installation instructions on the Context Engine GitHub repository. Clone the repo, install dependencies, and add the server config to your AI client.

Which AI clients work with Context Engine?

Context Engine works with all major MCP-compatible AI clients including Claude Desktop, Claude Code, Cursor, VS Code (GitHub Copilot), Windsurf, and Cline.

Is Context Engine free to use?

Yes, Context Engine is open source and available under the NOASSERTION license. You can use it freely in both personal and commercial projects.

Learn More About MCP Servers

Getting Started with MCP

Set up your first MCP server in minutes

MCP Setup Guide

Configure MCP in Claude, Cursor & VS Code

All MCP Tutorials

18+ hands-on guides for developers

MCP FAQ

40+ answers about Model Context Protocol

Context Engine Alternatives — Similar Developer Tools Servers

Looking for alternatives to Context Engine? Here are other popular developer tools servers you can use with Claude, Cursor, and VS Code.

Ecc

★ 188.2k

The agent harness performance optimization system. Skills, instincts, memory, security, and research-first development for Claude Code, Codex, Opencode, Cursor and beyond.

Javaguide

★ 155.8k

Java 面试 & 后端通用面试指南，覆盖计算机基础、数据库、分布式、高并发、系统设计与 AI 应用开发

Gemini CLI

★ 104.5k

A secure MCP server that wraps the Google Gemini CLI, allowing clients to query Gemini models using local OAuth sessions without requiring an API key. It provides tools for model interaction and diagnostics with built-in protection against command in

Awesome MCP Servers

★ 87.3k

⭐ Curated list of Model Context Protocol (MCP) servers - tools that extend Claude Desktop, Cursor, Windsurf, and other MCP clients with custom capabilities.

MCP Servers

★ 86.0k

Model Context Protocol Servers

CC Switch

★ 77.5k

A cross-platform desktop All-in-One assistant for Claude Code, Codex, OpenCode, OpenClaw, Gemini CLI & Hermes Agent. Only official website: ccswitch.io

Browse More Developer Tools MCP Servers

Explore all developer tools servers available in the MCPgee directory. Each server includes setup guides for Claude, Cursor, and VS Code.

Developer ToolsBrowse All Servers

Quick Config Preview

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

Add this to your claude_desktop_config.json or .cursor/mcp.json

Read the full setup guide →

Ready to use Context Engine?

Browse our complete directory of 33,000+ MCP servers, read setup guides for your editor, and start building with the Model Context Protocol.

33,000+ ServersFree & Open SourceStep-by-Step Guides
Explore All ServersRead Our Guides