ckg-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Capabilities
Features and capabilities supported by this server
| 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 |
|---|---|
| list_domainsA | List every Compressed Knowledge Graph (CKG) domain this server can answer about. Call this FIRST, before the other tools. Each domain is a self-contained dependency
graph for one subject area (e.g. "calculus", "google-dataplex", "glp1-obesity"). The
Returns: One line: the domain count followed by the comma-separated domain names, e.g. "Available domains (65): algebra-1, aws-data-catalog, calculus, ...". |
| query_ckgA | Return the dependency subgraph around a concept: what it requires, and what builds on it. Use this for the local neighborhood of a concept — both the prerequisites it depends on and the downstream concepts that depend on it. For ONLY the upstream prerequisite chain, use get_prerequisites instead. If unsure of the exact concept name, call search_concepts first to find it. Args: domain: Exact domain name from list_domains (e.g. "calculus", "google-dataplex"). concept: Concept to center the subgraph on. Matched case-insensitively; a partial name resolves to the first containing match (e.g. "taylor" -> "Taylor Series"). depth: Upstream prerequisite hops to include, 1-5 (default 3; higher values are capped at 5). Downstream "builds toward" concepts are always included to 2 hops. Returns: A Markdown report titled with the resolved concept, with a "Prerequisites (what you need to know first)" tree and a "Builds toward (concepts that depend on this)" tree, plus the concept's taxonomy tag when present. If the concept is not found, returns a message listing up to 5 similar names to retry with. |
| get_prerequisitesA | Return the full ordered chain of concepts to understand before a target concept. Use this for onboarding, gap-filling, or sequencing study — it walks every upstream dependency back to the root concepts. For a two-directional neighborhood (prerequisites AND dependents) use query_ckg; to resolve an exact concept name use search_concepts. Args: domain: Exact domain name from list_domains. concept: Target concept to trace back to its roots. Matched case-insensitively; a partial name resolves to the first containing match. Returns: One line listing the prerequisite chain in dependency order, e.g. "Prerequisite chain for 'Taylor Series' in calculus (5 concepts): Function -> Derivative -> ... -> Taylor Series". States that the concept is a root if it has no prerequisites, or that it was not found. |
| search_conceptsA | Find concepts in a domain by partial name — use this to discover exact concept labels. Run this before query_ckg or get_prerequisites when you do not know the precise label a concept is stored under. Does a case-insensitive substring match over every concept name in the domain. Args: domain: Exact domain name from list_domains. query: Substring to match against concept names (e.g. "mask", "iceberg", "lineage"). Returns: Up to 20 matching concept names (title-cased), each annotated with its taxonomy tag in brackets when present, e.g. " - Masking Policy [GOV]". Returns a "no concepts matching" message when there are no matches. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/Yarmoluk/ckg-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server