Skip to main content
Glama
loggy-dev

@loggydev/mcp-server

by loggy-dev
README.md
# @loggydev/mcp-server

MCP (Model Context Protocol) server for Loggy. Manage heartbeats, status pages, uptime monitors, feature flags, and more directly from your AI coding assistant.

## Installation

```bash
npm install -g @loggydev/mcp-server
```

Or use directly with npx:

```bash
npx @loggydev/mcp-server
```

## Configuration

### Environment Variables

| Variable | Required | Description |
|----------|----------|-------------|
| `LOGGY_API_TOKEN` | Yes | Your Loggy API token (get one from Settings → API Tokens) |
| `LOGGY_API_URL` | No | API URL (default: `https://loggy.dev`) |

### Claude Desktop

Add to your `~/.config/claude/claude_desktop_config.json`:

```json
{
  "mcpServers": {
    "loggy": {
      "command": "npx",
      "args": ["@loggydev/mcp-server"],
      "env": {
        "LOGGY_API_TOKEN": "lgky_your_token_here",
        "LOGGY_API_URL": "https://loggy.dev"
      }
    }
  }
}
```

### Windsurf / Cascade

Add to your MCP configuration:

```json
{
  "mcpServers": {
    "loggy": {
      "command": "npx",
      "args": ["@loggydev/mcp-server"],
      "env": {
        "LOGGY_API_TOKEN": "lgky_your_token_here",
        "LOGGY_API_URL": "https://loggy.dev"
      }
    }
  }
}
```

## Available Tools

### Heartbeats

- **list_heartbeats** - List all heartbeat monitors
- **create_heartbeat** - Create a new heartbeat monitor
- **get_heartbeat** - Get details of a specific heartbeat
- **delete_heartbeat** - Delete a heartbeat monitor

### Uptime Monitors

- **list_uptime_monitors** - List all uptime monitors
- **create_uptime_monitor** - Create a new uptime monitor
- **delete_uptime_monitor** - Delete an uptime monitor

### Status Pages

- **list_status_pages** - List all status pages
- **create_status_page** - Create a new public status page

### Feature Flags

- **list_feature_flags** - List all feature flags
- **create_feature_flag** - Create a new feature flag
- **toggle_feature_flag** - Enable/disable a feature flag

### Alerts

- **list_alerts** - List recent alerts

### Projects & Logs

- **list_projects** - List all projects
- **get_project_logs** - Get recent logs for a project

## Example Usage

Once configured, you can use natural language with your AI assistant:

- "Create a heartbeat called 'daily-backup' that expects a ping every 24 hours"
- "Set up an uptime monitor for api.myapp.com/health that checks every 5 minutes"
- "Create a feature flag called 'new-dashboard' and enable it for 25% of users"
- "Show me the last 10 error logs from my payment-service project"
- "List all my heartbeats and their current status"

## Requirements

- Node.js 18+
- Loggy Team subscription (API tokens are a Team feature)

## Getting an API Token

1. Go to [loggy.dev/settings#api-tokens](https://loggy.dev/settings#api-tokens)
2. Click "Create Token"
3. Give it a name like "MCP Server"
4. Set permissions (use "Set All Write" for full access)
5. Copy the token immediately (it's only shown once)

## License

MIT
# loggy-mcp

TDQS

B3.4/5.0

Scored across 15 tools

Disambiguation5/5

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.

Naming Consistency5/5

All tools follow a consistent verb_noun pattern using snake_case (e.g., create_uptime_monitor, list_feature_flags). Naming is predictable and uniform.

Tool Count5/5

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.

Completeness3/5

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.

Maintenance

ActivityInactive
ResponsivenessNo issues