site-kg
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LLM_API_KEY | No | Optional API key that enables the semantic layer (entity/relation extraction for Q&A) via cognee. Without it, the structural layer (search, page bodies, graph traversal) still works keyless. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| ingest_localA | Build a knowledge graph from a local directory of docs and/or code files. Docs (md/markdown/mdx/txt/wiki/rst/adoc) are indexed as-is with edges from markdown links and [[wikilinks]]; code files contribute import/include edges and searchable symbol headers. Returns site_id plus a graph-quality verdict: READY (traversable edges found) or NOT-READY (no links/imports; use search).
|
| ingest_urlA | Crawl a website, build its knowledge graph, and register it as a queryable site. Returns site_id for later tools plus a graph-quality verdict: READY (traversable edges found) or NOT-READY (tree without links; graph traversal useless).
|
| list_sitesA | List ingested sites with their verdicts and graph sizes. |
| site_statsB | Graph health for one site: doc/edge counts, edge types, verdict, top hubs. |
| searchC | Full-text search over the site's pages (inverted index, idf-weighted). |
| get_pageB | Full markdown body of one page, with title and source URL. |
| neighborsB | Subgraph around a page up to |
| render_siteB | Render the graph as a self-contained HTML viewer (human inspection path). Archive mode returns the file path; mode="live" replays the stored graph over a loopback SSE server and returns {live_url, run_id, last_seq}. AI-facing queries stay on search/ask/neighbors. |
| render_buildB | Render the graph construction process as a self-contained WebGPU viewer (human inspection path). Replays the build: nodes are born in corpus order onto chapter rings, then evidence edges (ref/imports/contains), then one flying wave per derived relation dimension -- every edge grows from its source node and binds to its target with a pulse, while a HUD counts nodes, edges and per-dimension edges as they land. Returns the file path; AI-facing queries stay on search/neighbors/ask. Needs a WebGPU-capable browser. |
| askB | LLM Q&A grounded in the site's pages: keyword retrieval + graph-neighborhood expansion, then embedding rerank and a cited answer. Requires SITE_KG_LLM_BASE and SITE_KG_LLM_KEY in the server environment. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 10 tools
The tools mostly target distinct operations: ingestion, listing/stats, search, page retrieval, neighbor expansion, rendering, and Q&A. The only mild overlap is render_site vs render_build, since both produce visual viewers, but their descriptions distinguish archive/live graph viewing from build-process replay.
All names use lowercase snake_case, which keeps them readable. However, the set mixes verb_noun names (list_sites, ingest_local, get_page, render_site) with bare nouns (site_stats, neighbors) and bare verbs (search, ask), so there is no fully predictable naming pattern.
Ten tools is well-scoped for a knowledge-graph ingestion and query server. Each tool covers a distinct phase: ingest, list/inspect, query, expand, render, or ask.
The surface covers the core lifecycle: build graphs from local/URL sources, list sites, inspect graph health, search/get pages, expand neighbors, render, and ask grounded questions. Minor gaps remain around site deletion, re-ingestion/update management, or explicit graph export, but normal query workflows are covered.