Skip to main content
Glama
Sign In
Context Engine

Context Engine

by aspose-core-mcp
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Aspose Context Engine

Shared ingestion, indexing, and retrieval infrastructure for documentation-backed AI assistants. The engine normalizes extracted content, builds searchable indexes, resolves API symbols, and serves citation-backed context through REST and MCP interfaces.

This repository contains the engine. Product-specific extraction plugins are installed separately. The default catalog in config/product-platform-plugins.json has empty plugins and compositions arrays; no product corpus or published indexes are bundled.

Quick start · External plugins · Deployment · MCP interfaces

Project family

These repositories work together to provide documentation-backed MCP services and a GitHub Copilot client for Aspose.Words for .NET. The shared engine is maintained under aspose-core-mcp; the Words/.NET components are maintained under aspose-words-mcp.

Repository

Responsibility

context-engine (this repository)

Shared documentation ingestion, indexing, retrieval, and MCP infrastructure

net-plugin

Aspose.Words for .NET documentation/API extraction and retrieval configuration

net-server

Deployment helpers that combine pinned engine and plugin versions

net-copilot-client-agent

GitHub Copilot agent, C# compilation checks, and example-answer showcase

Related MCP server: AI Square Documentation MCP Server

How the components fit together

Source repositories → external extraction plugin → engine ingestion and indexes
                                                         ↓
AI client ← MCP / REST interface ← retrieval and API-symbol lookup

The engine includes hybrid dense/lexical retrieval, citation metadata, structured API lookup, snapshot publication, background jobs, and an optional admin UI. Actual results depend on configured stores, registered plugins, and published content.

Developer setup

Use Python 3.12 or newer. From this repository root:

python3.12 -m venv .venv
. .venv/bin/activate
python -m pip install -e '.[dev]'
PYTHONPATH=src python -m pytest -q tests/test_engine_only_catalog.py

This focused check exercises engine-only catalog behavior without downloading product sources. For broader development checks, run make lint, make typecheck, and make test. The admin UI requires Node.js 22 or newer. See CONTRIBUTING.md.

Do not initialize the legacy source submodules recursively for the external-plugin workflow. Prepare only the sources required by your selected plugin.

Add product content

  1. Obtain a compatible external plugin checkout and prepare its source repositories and examples.

  2. Register its manifest in an engine catalog.

  3. Validate extraction using adcs-platform-ingest with explicit catalog, workspace, and plugin-interpreter paths.

  4. Configure runtime stores and embeddings, then publish indexed content explicitly.

  5. Configure retrieval-profile serving and connect an MCP or REST client.

See the external-plugin guide for commands and catalog examples. Plugin registration does not download sources, install dependencies, or publish data.

Deployment

Local development uses docker-compose.integration.yml; the single-VM template is docker-compose.vm.yml. Kubernetes templates and operational runbooks are under infra/. Configure credentials, embeddings, storage, and external plugin mounts for your environment before deployment. Deployment guidance distinguishes these options.

No hosted endpoint is provided or claimed by this checkout. Use the address of your deployment.

Compatibility boundaries

Legacy Words/.NET, TeX/.NET, and Total/.NET route definitions and the all-product source registry remain in the engine for compatibility. An empty plugin catalog does not disable those routes or remove previously indexed data. Dynamic route registration, automatic remote plugin installation, and hot reload are not supplied by the engine-only split.

Some integration tests require separately installed product plugins and skip when those plugins are absent. A passing engine-only test does not validate a deployed product corpus.

Repository map

Path

Responsibility

src/adcs/plugins/

Manifest loading, extraction contract, ingestion CLI, queued jobs

src/adcs/ingestion/, src/adcs/indexing/

Normalization, staging, embeddings, publication

src/adcs/retrieval/

Retrieval planning, ranking, and context packing

src/adcs/api/, src/adcs/mcp/

REST and MCP gateways

src/adcs/worker/

Background task runtime

config/

Catalogs and runtime policies

frontend/admin/

Optional administration UI

infra/

Deployment templates and operations guidance

tests/

Regression and integration tests

Documentation and provenance

The engine derives from the MIT-licensed Aspose Context Engine / ADCS project. Historical design records and changelog entries remain for provenance; they do not establish deployment status or product availability for this checkout. Existing GitHub Actions checks are retained for Python, the admin UI, and container builds.

License

MIT © Aspose Pty Ltd. Preserve existing attribution and bundled third-party notices. Source corpora and downloaded examples retain their upstream terms. Aspose and GroupDocs product names remain trademarks of their respective owners.

This server cannot be deployed

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues

Resources

Related MCP Connectors

Related MCP Servers

  • MCP RAG Server

    amaralphp
    A
    license
    Not graded
    quality
    C
    maintenance
    Enables document ingestion, semantic search, and retrieval-augmented generation via MCP tools and REST API, using vector embeddings and intelligent chunking.
    MIT

  • DocsFeed MCP Server

    sajannethsara
    F
    license
    Not graded
    quality
    B
    maintenance
    Enables users to ingest documentation from URLs or sitemaps, embed it into a searchable vector index, and expose authenticated MCP tools so AI clients can search and retrieve documentation content directly.
    -

  • Modular RAG MCP Server

    YiYunn-lucky
    A
    license
    Not graded
    quality
    C
    maintenance
    Enables AI assistants to perform retrieval-augmented generation through MCP tools for querying knowledge hubs, listing collections, and retrieving document summaries, with pluggable ingestion, hybrid search, and evaluation components.
    MIT