接入你的智能体
The publisher's own URL. Not a PlugMCP endpoint.
用我们的密钥与日志托管一份副本。
https://api.fettle.sh/mcpThe Claude button above opens Claude with the name and URL filled in. You still confirm it there.
claude mcp add --transport http sh.fettle-mcp https://api.fettle.sh/mcpRun in a terminal.
{ "mcpServers": { "sh.fettle-mcp": { "command": "npx", "args": [ "-y", "mcp-remote", "https://api.fettle.sh/mcp" ] } }}claude_desktop_config.json
Remote URL or a command on your machine? How the two installs differ
Tools
No tool list yet. Remote servers get one after the first health check.
FAQ
Uptime monitoring — monitors, incidents, heartbeats, maintenance windows, status page incidents
{ "mcpServers": { "sh.fettle-mcp": { "url": "https://api.fettle.sh/mcp", "headers": {} } }}Copy the http config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.
The publisher lists these environment variables: FETTLE_API_KEY, FETTLE_API_URL, FETTLE_TIMEOUT_MS.
Fettle is reached over HTTP.
Last checked 2026-11-10. Uptime monitoring — monitors, incidents, heartbeats, maintenance windows, status page incidents
From the publisher
README is not crawled yet. Open the repository
Uptime monitoring — monitors, incidents, heartbeats, maintenance windows, status page incidents