Fettle

fettle-mcp

Website: fettle.sh · MCP docs: fettle.sh/docs/mcp · Dashboard: dashboard.fettle.sh · Support: support@fettle.sh

MCP server for Fettle — uptime monitoring you can drive from Claude Code, Codex, Claude Desktop, Cursor, Windsurf or anything else that speaks the Model Context Protocol.

Ask your assistant to create a monitor, look up why one went down, acknowledge an incident, check a deploy or draft a status page post — it calls the same public API you would.

"Add an HTTP monitor for https://api.acme.dev, check it every 5 minutes from Europe."

"Which of my monitors had incidents this week?" "Silence alerts on the checkout monitor for the next 20 minutes — we're deploying." "We just deployed a1b2c3d — did any of the API monitors get worse?"

In the official MCP registry this server is sh.fettle/mcp — one entry covering both channels, for clients that install from the registry rather than from a hand-edited config file.

Requirements

• Node.js 20 or newer
• A Fettle account and an API key (Settings → API Keys at https://fettle.sh)

An API key belongs to one organization and carries either read or write scope. Read-scope keys can list and inspect; the write tools below need a write-scope key.

Install

There is nothing to install — MCP clients run the package with npx on demand. Add one entry to your client's config and restart it.

Claude Code

claude mcp add fettle --env FETTLE_API_KEY=fettle_your_key_here -- npx -y fettle-mcp

Codex

codex mcp add fettle --env FETTLE_API_KEY=fettle_your_key_here -- npx -y fettle-mcp

Or by hand in ~/.codex/config.toml (.codex/config.toml for one trusted project):

[mcp_servers.fettle]

command = "npx" args = ["-y", "fettle-mcp"]

[mcp_servers.fettle.env] FETTLE_API_KEY = "fettle_your_key_here"

Claude Desktop

~/Library/Application Support/Claude/claude_desktop_config.json on macOS, %APPDATA%\Claude\claude_desktop_config.json on Windows:

{

"mcpServers": { "fettle": { "command": "npx", "args": ["-y", "fettle-mcp"], "env": { "FETTLE_API_KEY": "fettle_your_key_here" } } } }

Cursor

~/.cursor/mcp.json (global) or .cursor/mcp.json (per project):

{

"mcpServers": { "fettle": { "command": "npx", "args": ["-y", "fettle-mcp"], "env": { "FETTLE_API_KEY": "fettle_your_key_here" } } } }

Windsurf

~/.codeium/windsurf/mcp_config.json:

{

"mcpServers": { "fettle": { "command": "npx", "args": ["-y", "fettle-mcp"], "env": { "FETTLE_API_KEY": "fettle_your_key_here" } } } }

Configuration

Tools

56 tools, grouped by what they work on. Read-scope keys can call the read ones; everything marked write needs a write-scope key.

Every tool carries the MCP hints readOnlyHint, destructiveHint, idempotentHint and openWorldHint, so a client can tell reads from changes without parsing names and ask for confirmation only where it matters. Only the five delete_* tools are destructive. preview_maintenance_window and check_target are marked read-only although they need a write-scope key: they change nothing. check_now and check_target reach the target host, so they are open-world.

Every tool whose result is a JSON object declares an outputSchema and returns the result as structuredContent as well as text, so a client can read typed fields instead of parsing the text. The four exceptions return the text only: list_monitors (its compact rows) and the three tools whose result is a list — list_active_maintenance, preview_maintenance_window and list_channels.

Monitors

Results and uptime

Incidents

Deploys and changes

Heartbeats

Maintenance windows

Tags

| bulk_update_heartbeat_tags | write | Add and/or remove tags across up to 300 heartbeats in one call.