datacore-mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DATACORE_PATH | No | Full installation path | ~/Data |
| DATACORE_TIMEZONE | No | IANA timezone (e.g., Europe/Ljubljana) | System |
| DATACORE_CACHE_TTL | No | File cache TTL in seconds | 60 |
| DATACORE_CORE_PATH | No | Core mode storage path | ~/Datacore |
| DATACORE_HTTP_HOST | No | HTTP bind address | 127.0.0.1 |
| DATACORE_HTTP_PORT | No | HTTP transport port | 3100 |
| DATACORE_LOG_LEVEL | No | debug, info, warning, error | warning |
| DATACORE_TRANSPORT | No | stdio or http | stdio |
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 | {} |
| logging | {} |
| prompts | {} |
| resources | {
"subscribe": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| datacore_captureA | Capture a journal entry or knowledge note. Call proactively to record important decisions, meeting outcomes, and significant events. |
| datacore_searchB | Search journal entries and knowledge notes by keyword |
| datacore_ingestC | Ingest text content as a knowledge note |
| datacore_statusA | Show Datacore status: note counts, module health, update info |
| datacore_dateA | Canonical date operations — ALWAYS use this instead of typing dates from memory. LLMs hallucinate day-of-week names and anchor to training-era dates. Returns today's date, validates day-of-week, adds/subtracts days, parses relative expressions, and formats org-mode timestamps. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| datacore-capture-guide | Write a journal entry or knowledge note to Datacore. |
| datacore-guide | Guide to Datacore tools and workflows. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Datacore Status | Current system status summary |
| Today's Journal | Today's journal entry |
| Datacore Agent Guide | Workflow guide for AI agents: capture, search, ingest, modules |
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose: capture for journal entries, ingest for knowledge notes, search for querying, status for system health, and date for date operations. No overlap between any of the tools, so an agent can reliably select the correct one.
All tools follow the same datacore_ prefix followed by a simple, consistent verb: capture, search, ingest, status, date. The naming pattern is uniform and predictable across the entire set.
With 5 tools, the server is well-scoped for a knowledge management utility. Each tool earns its place, covering core operations plus a necessary date utility, and there is no bloat or redundancy.
The server covers the primary lifecycle of creating and searching notes, with status and date utilities supporting the workflow. Minor gaps include lack of update/delete operations for notes, but the core functionality is solid and agents can work around these limitations.