elog-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ELOG_URL | Yes | Base URL incl. subdir, e.g. https://elog.nd280.org/elog | |
| ELOG_USER | No | Shared credentials (username) | |
| ELOG_API_KEY | No | Require Authorization: Bearer <key> on all OpenAPI endpoints | |
| ELOG_TIMEOUT | No | HTTP timeout seconds | 30 |
| ELOG_LOGBOOKS | No | Comma-separated allow-list used by search * / listing order | |
| ELOG_MCP_HOST | No | Bind address in HTTP modes | 127.0.0.1 |
| ELOG_MCP_PORT | No | Bind port in HTTP modes | 8000 |
| ELOG_PASSWORD | No | Shared credentials (password) | |
| ELOG_SSL_VERIFY | No | true (default) / false — never disable outside local tests | true |
| ELOG_MCP_KEYFILE | No | TLS key file (PEM) | |
| ELOG_CORS_ORIGINS | No | Comma-separated CORS origins for openapi mode | * |
| ELOG_MCP_CERTFILE | No | TLS cert file (PEM) | |
| ELOG_MCP_TRANSPORT | No | stdio (default) · streamable-http · openapi | 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 | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| elog_list_logbooksA | List the logbooks available on the configured ELOG server. Returns a list of {name, description?, url} objects. The optional ELOG_LOGBOOKS environment variable restricts and orders the result. |
| elog_searchA | Search logbook entries by full text, attributes, and/or date. Args: text: Regular expression matched against entry message bodies. Use ^…$ anchors for exact matches. attributes: Exact attribute filters as regular expressions, e.g. {"Author": "^jdoe$", "Category": "DAQ"}. date_from: Inclusive range start, 'YYYY-MM-DD' or 'YYYY-MM-DD HH:MM[:SS]'. date_to: Inclusive range end, same formats (time defaults to 23:59:59). last_days: Show entries from the last N days instead of an explicit range. logbook: Logbook name to search, or "*" to search all known logbooks. max_results: Maximum number of entries returned per page (server cap 100000). reverse: Sort newest-first when true, oldest-first when false. Returns {"total": int, "entries": [{id, logbook?, date_raw, date_iso?, attributes{}, text_excerpt, encoding, encoding_name, attachments[], reply_to[], in_reply_to?, url}]}. Each entry's |
| elog_get_entryA | Read one logbook entry in full: all attributes, complete body, attachments. Args: logbook: Name of the logbook containing the entry. entry_id: Numeric message ID of the entry. Returns the full entry record including the untruncated body text, threading info (reply_to / in_reply_to) and the canonical web URL. |
| elog_get_recent_entriesA | Fetch the newest entries of a logbook, newest first. Args: logbook: Name of the logbook to read. count: Number of recent entries to return. Returns {"total": int, "entries": [...]} with excerpts like elog_search. |
| elog_get_attachmentA | Download an attachment (screenshot, config file, ...) as base64 content. Args: logbook: Name of the logbook holding the attachment. filename: Attachment filename exactly as listed on the entry. Returns {filename, content_b64, mime, size}; embed via MCP resource mechanisms when presenting to users. |
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 5 tools
Each tool maps to a distinct operation (listing logbooks, searching, reading a single entry, browsing recent entries, fetching attachments), so confusion is unlikely. However, elog_get_recent_entries overlaps with elog_search's last_days and reverse options, making the boundary between them slightly less sharp.
The elog_ prefix and verb-first style are consistent, and most tools follow a verb_noun pattern such as elog_list_logbooks, elog_get_entry, and elog_get_attachment. elog_search is the one outlier because it omits an explicit object, which is a minor deviation from the otherwise predictable pattern.
Five tools is a well-scoped size for a read-only logbook client. Each tool covers one essential need—discovering logbooks, searching entries, reading full entries, browsing recent entries, and downloading attachments—without unnecessary redundancy or bloat.
The read-oriented surface is complete for searching, reading, and retrieving attachments from ELOG entries. The only notable gap is the absence of write or lifecycle tools such as creating, replying to, or editing entries, though this appears to be an intentional read-only scope.