ontology
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@ontology What object types are defined in the ontology?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
py-ontology-server-starter
Ontology knowledge server starter — FastAPI semantic layer + Apache Jena Fuseki triplestore, consumed via both REST and MCP.
Declare Palantir-style object-centric ontologies (Object Type / Property / Link Type) in code, and handle storage and querying with W3C standards (RDF / SPARQL 1.1). Since the application code uses only the SPARQL standard, you can swap the store for GraphDB or another triplestore without changing the app.
┌─ 소비자 ──────────────────────────────┐
│ AI 에이전트(MCP) 앱·사람(REST) │
└──────────┬───────────────┬───────────┘
│ │
mcp_server.py api/rest.py ← 이중 어댑터
└───────┬───────┘
ontology/ + store/ ← 코어: 온톨로지 정의 + SPARQL 클라이언트
│
Apache Jena Fuseki (docker) ← 저장·SPARQL·추론
▲
ingest/ 파이프라인 ← 지식원 → RDF 변환·적재Quick Start
# 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/organizationRelated MCP server: mcp-ubergraph-query
MCP Adapter (for AI agents)
Runs over the stdio transport. In a Claude Code project's .mcp.json:
{
"mcpServers": {
"ontology": {
"command": "/절대경로/.venv/bin/python",
"args": ["-m", "ontology_server.mcp_server"]
}
}
}Provided tools: list_object_types (schema discovery) · search_objects (instance lookup by type) · sparql_query (read-only direct query).
Adapting to Your Domain
Replace
src/ontology_server/ontology/sample.pywith your domain ontology — change only the Object Type / Link Type declarations and the REST, MCP, and query builders follow along.Add per-source ingestion modules under
src/ontology_server/ingest/(seeexample_csv.py).If external integration or standards compliance is required, settle on a real URI scheme for namespaces and maintain an OWL schema document alongside.
Tests
pytest # 단위 테스트 (Fuseki 불필요)
RUN_INTEGRATION=1 pytest # Fuseki 기동 상태에서 통합 테스트 포함Structure
Path | Role |
| Object/Link Type definition framework (Palantir-style) |
| Sample ontology — the file you replace in your project |
| SPARQL 1.1 client (the point where you can swap the store) |
| REST adapter |
| MCP adapter |
| Knowledge source → RDF ingestion pipeline |
| Starts Fuseki |
License
MIT
Available Tools
3 toolslist_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
Scored across 3 tools
Each tool has a distinct purpose: schema discovery, instance search, and raw SPARQL querying. There is no overlap between them.
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.
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.
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.
Maintenance
Related MCP Connectors
Query your own knowledge graph from any MCP client. The graph lives in a database you own.
Knowledge graph for AI agents. Query concepts, walk edges, get advisories.
Read-only search of your Sortio knowledge graph (files and entities) for Claude and ChatGPT.
Search and fetch Wikidata entities, execute SPARQL queries, and resolve external identifiers.
Related MCP Servers
- AlicenseBqualityDmaintenanceA Model Context Protocol server that provides read-only access to Ontotext GraphDB, enabling LLMs to explore RDF graphs and execute SPARQL queries.29 npm17GPL 3.0
- AlicenseAqualityDmaintenanceEnables AI assistants to query the Ubergraph biomedical ontology SPARQL endpoint with tools for custom SPARQL queries, term lookup, search, and hierarchy traversal.4MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to interact with ontologies through the Ontology Access Kit, providing ontology querying and management capabilities.5MIT
- AlicenseAqualityCmaintenanceEnables AI assistants to query, modify, and reason over OWL/TTL/RDF ontology files using natural language, without needing SPARQL or OWL syntax.146MIT