mackerel-mcp-server

Created By
ryuichi1208a year ago
MCP server implementation for Mackerel monitoring service.
Overview

what is mackerel-mcp-server?

The mackerel-mcp-server is a server project designed for monitoring Mackerel servers, providing tools to retrieve and manage server monitoring information using the Mackerel API.

how to use mackerel-mcp-server?

To use the mackerel-mcp-server, install it via pip or from source, set your Mackerel API key as an environment variable, and configure it to work with the Claude AI assistant for interactive monitoring.

key features of mackerel-mcp-server?

  • Lists all registered hosts in Mackerel with detailed information.
  • Retrieves specific host information based on host ID.
  • Integrates with Claude AI for conversational interaction.

use cases of mackerel-mcp-server?

  1. Monitoring the status of multiple servers in real-time.
  2. Retrieving detailed information about specific hosts for troubleshooting.
  3. Interacting with server data through a conversational interface.

FAQ from mackerel-mcp-server?

  • How do I install mackerel-mcp-server?

You can install it using pip with the command pip install mackerel-mcp-server or clone the repository and install from source.

  • What is required to run the server?

You need to set your Mackerel API key as an environment variable to access the Mackerel API.

  • Can I use it without Claude?

While the server is designed to work with Claude, you can still use the API directly for monitoring without the conversational interface.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
ryuichi1208
Star
1
Language
Python
License
-
Category
monitoring
Tags

Recommend Servers

View All
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

8 hours ago