Fettle — Claude Code MCP server: uptime checks from chat
Wires Fettle into your coding agent so monitors, incidents and maintenance windows can be handled without leaving the editor.
MIT updated 2026-10-22
claude mcp add --env FETTLE_API_KEY=<FETTLE_API_KEY> --env FETTLE_API_URL=<FETTLE_API_URL> --env FETTLE_TIMEOUT_MS=<FETTLE_TIMEOUT_MS> --transport stdio fettle -- npx -y fettle-mcpWhat Fettle does
The server exposes 49 tools. You can list monitors with their status and SSL expiry, read one monitor's full config, create a single check or up to 100 in one all-or-nothing call, pause and resume checks, and pull an uptime summary. MCP hints on every tool (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) let the client separate reads from writes and ask for confirmation only where it matters. Five delete_* tools are the destructive ones.
An API key is tied to a single organization and carries read or write scope. Listing and inspecting work with read; creating, editing, pausing and deleting need write. The server exits on startup when FETTLE_API_KEY is missing. Two optional variables exist: FETTLE_API_URL (default https://api.fettle.sh) and FETTLE_TIMEOUT_MS (default 30000), the per-call limit.
Nothing gets installed globally: clients launch the package through npx -y fettle-mcp. Node.js 20+ is required. Clients with HTTP transport support can skip the local process and connect to https://api.fettle.sh/mcp.
What it helps with
- set up an HTTP check on an API endpoint every 5 minutes from Europe
- find out which monitors failed during the week
- halt checks ahead of a deploy and bring them back afterwards
- push one interval and region set onto a hundred monitors at once
- probe a target from one region before committing to a monitor
Example prompts for the agent
- Add an HTTP monitor for
https://api.acme.dev, checking every 5 minutes from Europe. - Which monitors had incidents this week?
How to install Fettle
1Platform CLI
claude mcp add --env FETTLE_API_KEY=<FETTLE_API_KEY> --env FETTLE_API_URL=<FETTLE_API_URL> --env FETTLE_TIMEOUT_MS=<FETTLE_TIMEOUT_MS> --transport stdio fettle -- npx -y fettle-mcpReplace <…> with your own values
2Platform CLI: remote server
claude mcp add --transport http fettle https://api.fettle.sh/mcp1Platform CLI: remote server
codex mcp add fettle --url https://api.fettle.sh/mcp2Platform CLI
codex mcp add fettle --env FETTLE_API_KEY=<FETTLE_API_KEY> --env FETTLE_API_URL=<FETTLE_API_URL> --env FETTLE_TIMEOUT_MS=<FETTLE_TIMEOUT_MS> -- npx -y fettle-mcpReplace <…> with your own values
Config file
{
"mcpServers": {
"fettle": {
"url": "https://api.fettle.sh/mcp"
}
}
}{
"mcpServers": {
"fettle": {
"command": "npx",
"args": [
"-y",
"fettle-mcp"
],
"env": {
"FETTLE_API_KEY": "<FETTLE_API_KEY>",
"FETTLE_API_URL": "<FETTLE_API_URL>",
"FETTLE_TIMEOUT_MS": "<FETTLE_TIMEOUT_MS>"
}
}
}
}Replace <…> with your own values
Config file
{
"servers": {
"fettle": {
"type": "http",
"url": "https://api.fettle.sh/mcp"
}
}
}{
"servers": {
"fettle": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"fettle-mcp"
],
"env": {
"FETTLE_API_KEY": "<FETTLE_API_KEY>",
"FETTLE_API_URL": "<FETTLE_API_URL>",
"FETTLE_TIMEOUT_MS": "<FETTLE_TIMEOUT_MS>"
}
}
}
}Replace <…> with your own values
1Platform CLI: remote server
gemini mcp add -t http fettle https://api.fettle.sh/mcp2Platform CLI
gemini mcp add -e FETTLE_API_KEY=<FETTLE_API_KEY> -e FETTLE_API_URL=<FETTLE_API_URL> -e FETTLE_TIMEOUT_MS=<FETTLE_TIMEOUT_MS> fettle npx -y fettle-mcpReplace <…> with your own values
Step by step, with commands for each platform: How to add an MCP server to Claude Code, Codex, Cursor, VS Code, Gemini CLI and more
Questions about Fettle
How do I install Fettle in Claude Code?
Run claude mcp add fettle --env FETTLE_API_KEY=fettle_your_key_here -- npx -y fettle-mcp, then restart the client.
What does Fettle do?
It gives the assistant Fettle's monitor, incident and maintenance tools: create a check, trace why something went down, acknowledge an incident, stop checks before a release.
What is the difference between read and write keys?
A read-scope key can only list and inspect monitors and results. Creating, updating, pausing and deleting require a write-scope key.