Skip to main content
Glama
ontology
by nrwoodpsh

py-ontology-server-starter

Ontologie-Wissensserver-Starter — FastAPI-Semantikschicht + Apache-Jena-Fuseki-Triplestore, für Konsumenten sowohl REST als auch MCP.

Eine Palantir-artige objektzentrierte Ontologie (Object Type / Property / Link Type) wird im Code deklariert, Speicherung und Abfrage erfolgen nach W3C-Standards (RDF / SPARQL 1.1). Da der Anwendungscode ausschließlich den SPARQL-Standard verwendet, bleibt die App unverändert, auch wenn der Datenspeicher z. B. durch GraphDB ersetzt wird.

┌─ 소비자 ──────────────────────────────┐
│  AI 에이전트(MCP)      앱·사람(REST)   │
└──────────┬───────────────┬───────────┘
           │               │
   mcp_server.py       api/rest.py      ← 이중 어댑터
           └───────┬───────┘
            ontology/ + store/           ← 코어: 온톨로지 정의 + SPARQL 클라이언트
                   │
        Apache Jena Fuseki (docker)      ← 저장·SPARQL·추론
                   ▲
             ingest/ 파이프라인           ← 지식원 → RDF 변환·적재

Schnellstart

# 1. 트리플스토어 기동
docker compose up -d fuseki          # http://localhost:3030 (admin / admin)

# 2. 앱 설치
python -m venv .venv && source .venv/bin/activate
pip install -e ".[dev]"

# 3. 샘플 데이터 적재 (CSV → RDF → Fuseki)
python -m ontology_server.ingest.example_csv data/sample/organizations.csv \
  --object-type organization --push

# 4. REST 서버 기동
uvicorn ontology_server.main:app --reload
# → http://localhost:8000/docs
curl localhost:8000/objects/organization

Related MCP server: mcp-ubergraph-query

MCP-Adapter (für KI-Agenten)

Läuft über den stdio-Transport. In der .mcp.json des Claude-Code-Projekts:

{
  "mcpServers": {
    "ontology": {
      "command": "/절대경로/.venv/bin/python",
      "args": ["-m", "ontology_server.mcp_server"]
    }
  }
}

Bereitgestellte Werkzeuge: list_object_types(Schema ermitteln) · search_objects(Instanzen nach Typ abfragen) · sparql_query(schreibgeschützte Direktabfrage).

An die eigene Domäne anpassen

  1. Ersetze src/ontology_server/ontology/sample.py durch die Domänen-Ontologie — wenn du nur die Deklarationen von Object Type und Link Type änderst, passen sich REST-, MCP- und Abfrage-Builder automatisch an.

  2. Füge in src/ontology_server/ingest/ pro Wissensquelle ein Erfassungsmodul hinzu (siehe example_csv.py).

  3. Wenn externe Anbindung und Standardkonformität erforderlich sind, lege die Namespaces als reales URI-Schema fest und pflege die OWL-Schema-Dokumente ebenfalls.

Tests

pytest                       # 단위 테스트 (Fuseki 불필요)
RUN_INTEGRATION=1 pytest     # Fuseki 기동 상태에서 통합 테스트 포함

Aufbau

Pfad

Rolle

ontology/model.py

Framework zur Definition von Object/Link Type (Palantir-artig)

ontology/sample.py

Beispiel-Ontologie — die Datei, die im Projekt ersetzt wird

store/sparql.py

SPARQL-1.1-Client (Stelle, an der der Datenspeicher ersetzt werden kann)

api/rest.py

REST-Adapter

mcp_server.py

MCP-Adapter

ingest/

Erfassungspipeline von Wissensquellen → RDF

docker-compose.yml

Fuseki-Start

Lizenz

MIT

Available Tools

3 tools
list_object_typesA

온톨로지에 정의된 Object Type·Link Type 전체를 반환한다. 질의 전에 먼저 호출해 스키마를 파악할 것.

Inputs: no named parameters. Returns: result

search_objectsB

지정한 Object Type의 인스턴스를 조회한다. object_type은 list_object_types의 api_name.

Inputs: object_type (required), limit. Returns: result

sparql_queryA

읽기 전용 SPARQL(SELECT/ASK/CONSTRUCT/DESCRIBE)을 직접 실행한다. 복잡한 관계 질의용.

Inputs: query (required). Returns: result

Tool Schema Changelog

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

Loading tool schema changelog…

    TDQS

    A3.8/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a distinct purpose: schema discovery, instance search, and raw SPARQL querying. There is no overlap between them.

    Naming Consistency4/5

    Tool names follow a consistent verb_noun pattern (list_object_types, search_objects, sparql_query). sparql_query is slightly less parallel because it uses a noun rather than a verb, but it is still clear and predictable.

    Tool Count4/5

    Three tools is a minimal but reasonable set for an ontology server: schema listing, instance search, and flexible SPARQL access. It is on the thin side but not inadequate.

    Completeness4/5

    The surface covers schema discovery, instance lookup, and arbitrary read-only queries, which covers most ontology use cases. Missing write operations are likely intentional for a read-only server, so the gap is minor.

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      B
      quality
      D
      maintenance
      A Model Context Protocol server that provides read-only access to Ontotext GraphDB, enabling LLMs to explore RDF graphs and execute SPARQL queries.
      2
      9 npm
      17
      GPL 3.0
    • A
      license
      A
      quality
      D
      maintenance
      Enables AI assistants to query the Ubergraph biomedical ontology SPARQL endpoint with tools for custom SPARQL queries, term lookup, search, and hierarchy traversal.
      4
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to interact with ontologies through the Ontology Access Kit, providing ontology querying and management capabilities.
      5
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables AI assistants to query, modify, and reason over OWL/TTL/RDF ontology files using natural language, without needing SPARQL or OWL syntax.
      14
      6
      MIT