Elasticsearch Knowledge Graph for MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DEBUG | No | Enable debug logging | false |
| ES_NODE | No | Elasticsearch URL | http://localhost:9200 |
| AI_MODEL | No | AI model to use for AI-powered features | |
| AI_API_KEY | No | Alternative to GROQ_API_KEY for AI-powered features | |
| AI_API_BASE | No | OpenAI-compatible API URL. Defaults to Groq's endpoint. | |
| ES_PASSWORD | No | Elasticsearch password | |
| ES_USERNAME | No | Elasticsearch username | |
| GROQ_MODELS | No | Comma-separated model list | openai/gpt-oss-120b,llama-3.3-70b-versatile |
| GROQ_API_KEY | No | Groq API key for AI filtering. Optional - enables AI-powered search filtering and zone relevance scoring. | |
| KG_DEFAULT_ZONE | No | Default memory zone | default |
| KG_INDEX_PREFIX | No | Elasticsearch index prefix | knowledge-graph |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| inspect_filesC | Agent driven file inspection that uses AI to retrieve relevant content from multiple files. |
| inspect_knowledge_graphC | Agent driven knowledge graph inspection that uses AI to retrieve relevant entities and relations based on a query. |
| create_entitiesC | Create entities in knowledge graph (memory) |
| update_entitiesC | Update entities in knowledge graph (memory) |
| delete_entitiesC | Delete entities from knowledge graph (memory) |
| create_relationsC | Create relationships between entities in knowledge graph (memory) |
| delete_relationsC | Delete relationships from knowledge graph (memory) |
| search_nodesA | Search entities using ElasticSearch query syntax. Supports boolean operators (AND, OR, NOT), fuzzy matching (~), phrases ("term"), proximity ("terms" |
| open_nodesB | Get details about specific entities in knowledge graph (memory) and their relations |
| add_observationsC | Add observations to an existing entity in knowledge graph (memory) |
| mark_importantB | Mark entity as important in knowledge graph (memory) by boosting its relevance score |
| get_recentB | Get recently accessed entities from knowledge graph (memory) and their relations |
| list_zonesA | List all available memory zones with metadata. When a reason is provided, zones will be filtered and prioritized based on relevance to your needs. |
| create_zoneC | Create a new memory zone with optional description. |
| delete_zoneA | Delete a memory zone and all its entities/relations. |
| copy_entitiesC | Copy entities between zones with optional relation handling. |
| move_entitiesC | Move entities between zones (copy + delete from source). |
| merge_zonesC | Merge multiple zones with conflict resolution options. |
| zone_statsC | Get statistics for entities and relationships in a zone. |
| get_time_utcA | Get the current UTC time in YYYY-MM-DD hh:mm:ss format |
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 20 tools
Most tools have distinct purposes, such as create_entities vs. update_entities or list_zones vs. zone_stats. However, some overlap exists: open_nodes and get_recent both retrieve entity details, and copy_entities vs. move_entities could be confused, though descriptions clarify differences.
Tool names follow a consistent verb_noun pattern throughout, such as create_entities, delete_relations, and inspect_files. All use snake_case with clear, descriptive verbs, making the set predictable and easy to navigate.
With 20 tools, the count is slightly high but reasonable for managing a knowledge graph with zones, entities, and relations. It covers operations like CRUD, inspection, and zone management, though it might feel heavy compared to simpler servers.
The toolset provides comprehensive coverage for a knowledge graph domain, including entity and relation CRUD, zone management (create, delete, merge, list), search capabilities, and utilities like time retrieval. No obvious gaps are present; agents can perform full lifecycle operations.