MCP.so
ログイン

Context Engine MCP Server

@welf

基本情報

カテゴリ

その他

ライセンス

Apache-2.0 license

トランスポート

stdio

作者

welf

Context Engine MCP Server について

Virtual AI-centric IDE for LLMs and AI Agents

Context Engine MCP Server の設定

標準の設定はありません

このサーバーの README には解析可能な MCP 設定ブロックが含まれていません。インストール手順はリポジトリをご確認ください。

リポジトリ

Context Engine MCP Server のツール

ツール一覧はまだありません

この掲載には表示できるツール一覧がまだありません。サーバーにツールがないという意味ではありません。対応機能はプロジェクトのドキュメントをご確認ください。

ツールは README から自動的に抽出されます。メンテナーは ## Tools という見出しの下に記載することで、このタブに反映できます。

概要

What is Context Engine?

Context Engine is a specialized system that transforms how AI coding assistants understand and work with code by providing rich, semantic understanding of a codebase—including complete type information, usage patterns, relationships, and dependencies—instead of treating code as plain text files.

How to use Context Engine?

—

Key features of Context Engine

  • Semantic search by meaning, not just text matching
  • Rich context with type definitions, relationships, and usage patterns
  • Pattern recognition from your codebase
  • Impact analysis for proposed changes
  • Validation that generated code fits project patterns and compiles

Use cases of Context Engine

  • AI coding assistants generating correct, compilable code using current library APIs
  • Developers wanting AI agents to understand project-specific conventions and type relationships
  • Reducing iterative LLM calls by providing complete context upfront

よくある質問

1

What makes Context Engine different from existing LSP-based MCP servers?

Context Engine does not proxy existing LSP responses; it performs sophisticated analysis using static code analysis tools (LSP and Tree-sitter) to extract enhanced context—like usage patterns and relationship graphs—that no LSP provides on its own.

2

What are the runtime requirements?

Context Engine is implemented in Rust with two components: `context-engine-core` (a Rust library for LSP communication and analysis) and `context-engine-server` (an MCP server). It leverages existing Language Servers and Tree-sitter parsers.

3

What are known limitations or current status?

The project is currently in active development. The core architecture and API design are established, with implementation underway.

コメント

「その他」の他のコンテンツ