A local-first log sink that turns your coding agent into a runtime companion.
A local-first log sink that turns your coding agent into a runtime companion. The loggles mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 14 defined tools rather than through you.
Everything the assistant can do here goes through one of these:
search_logs — Search with filters: time range, level, service, message text, structured properties. Supports paginationget_log_by_id — Retrieve a single log event by IDget_services — List all source/service names that have emitted logsget_log_levels — List distinct log levels presentget_properties — List distinct structured property keysget_property_values — List distinct values for a property key within a time windowget_log_stats — Log counts grouped by level and serviceget_logs_by_trace_id — Retrieve all logs sharing a trace/correlation IDget_related_logs — Context window of logs around a specific eventget_recent_errors — Last N error/critical log events, optionally filtered by servicetail_logs — Most recent N log eventsget_log_rate — Bucketed log counts over time — observe traffic volume and rhythmBeing a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.
Plenty of monitoring and observability servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Loggles's toolset — search_logs, get_log_by_id, get_services and 11 more — is a fair guide to whether it matches your workflow. It is maintained by bytesquashcom; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| search_logs | Search with filters: time range, level, service, message text, structured properties. Supports pagination. |
| get_log_by_id | Retrieve a single log event by ID |
| get_services | List all source/service names that have emitted logs |
| get_log_levels | List distinct log levels present |
| get_properties | List distinct structured property keys |
| get_property_values | List distinct values for a property key within a time window |
| get_log_stats | Log counts grouped by level and service |
| get_logs_by_trace_id | Retrieve all logs sharing a trace/correlation ID |
| get_related_logs | Context window of logs around a specific event |
| get_recent_errors | Last N error/critical log events, optionally filtered by service |
| tail_logs | Most recent N log events |
| get_log_rate | Bucketed log counts over time — observe traffic volume and rhythm |
| get_message_templates | List distinct message templates, optionally filtered by service |
| find_log_patterns | Cluster messages by recurring pattern |
{
"mcpServers": {
"loggles": {
"command": "npx",
"args": ["-y", "@opentelemetry/sdk-node"]
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
Give your coding agent the full DevTools toolbox: traces, network, console, heap snapshots and Lighthouse.
Dashboards, Prometheus and Loki queries, incidents and alerts — observability by conversation.
Errors with full context — stack traces, issue triage and AI-powered root-cause analysis from Sentry's server.
Enables enhanced web research capabilities for large language models through intelligent search queuing and advanced content extraction.
Automates browser interactions and enables Large Language Models (LLMs) to interact with web pages through Playwright and Chrome DevTools Protocol
Guides tool usage by providing recommendations for MCP tools at each problem-solving stage.