@loggydev/mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOGGY_API_URL | No | API URL (default: https://loggy.dev) | https://loggy.dev |
| LOGGY_API_TOKEN | Yes | Your Loggy API token (get one from Settings → API Tokens) |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_heartbeatsB | List all heartbeat monitors for your account |
| create_heartbeatA | Create a new heartbeat monitor for cron jobs or scheduled tasks |
| get_heartbeatB | Get details of a specific heartbeat by ID or slug |
| delete_heartbeatC | Delete a heartbeat monitor |
| list_uptime_monitorsA | List all uptime monitors |
| create_uptime_monitorB | Create a new uptime monitor to check URL availability |
| delete_uptime_monitorB | Delete an uptime monitor |
| list_status_pagesA | List all status pages |
| create_status_pageB | Create a new public status page |
| list_feature_flagsB | List all feature flags |
| create_feature_flagC | Create a new feature flag |
| toggle_feature_flagB | Enable or disable a feature flag |
| list_alertsC | List recent alerts |
| list_projectsB | List all projects |
| get_project_logsB | Get recent logs for a project |
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 15 tools
Each tool targets a distinct resource or action, such as feature flags, heartbeats, status pages, uptime monitors, projects, and alerts. There is no ambiguity between tools.
All tools follow a consistent verb_noun pattern using snake_case (e.g., create_uptime_monitor, list_feature_flags). Naming is predictable and uniform.
15 tools is well within the typical 3-15 range for a server covering multiple domains like monitoring and feature flags. Each tool serves a clear purpose.
The tool set covers basic CRUD for heartbeats and uptime monitors but lacks delete operations for feature flags and status pages. Also, projects only have a list operation, and alerts are only listable. Notable gaps exist.