fettle-mcp 0.1.0 → 0.1.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +32 -1
- package/package.json +15 -3
package/README.md
CHANGED
|
@@ -13,6 +13,10 @@ incident or pause checks before a deploy — it calls the same public API you wo
|
|
|
13
13
|
"Pause the checkout monitor — we're deploying for the next 20 minutes."
|
|
14
14
|
```
|
|
15
15
|
|
|
16
|
+
In the [official MCP registry](https://registry.modelcontextprotocol.io) this
|
|
17
|
+
server is `sh.fettle/mcp` — one entry covering both channels, for clients that
|
|
18
|
+
install from the registry rather than from a hand-edited config file.
|
|
19
|
+
|
|
16
20
|
## Requirements
|
|
17
21
|
|
|
18
22
|
- Node.js 20 or newer
|
|
@@ -121,6 +125,28 @@ If your client supports remote MCP servers over HTTP, you do not need this
|
|
|
121
125
|
package at all — point it at `https://api.fettle.sh/mcp` with the same API key
|
|
122
126
|
as a Bearer token. Same tools, same behaviour, nothing to install or update.
|
|
123
127
|
|
|
128
|
+
Claude Code adds the remote channel from the command line — a different flag
|
|
129
|
+
set from the stdio one above, with the key as a header rather than an
|
|
130
|
+
environment variable:
|
|
131
|
+
|
|
132
|
+
```bash
|
|
133
|
+
claude mcp add fettle --transport http https://api.fettle.sh/mcp \
|
|
134
|
+
--header "Authorization: Bearer fettle_your_key_here"
|
|
135
|
+
```
|
|
136
|
+
|
|
137
|
+
Clients configured through a JSON file take the same two fields:
|
|
138
|
+
|
|
139
|
+
```json
|
|
140
|
+
{
|
|
141
|
+
"mcpServers": {
|
|
142
|
+
"fettle": {
|
|
143
|
+
"url": "https://api.fettle.sh/mcp",
|
|
144
|
+
"headers": { "Authorization": "Bearer fettle_your_key_here" }
|
|
145
|
+
}
|
|
146
|
+
}
|
|
147
|
+
}
|
|
148
|
+
```
|
|
149
|
+
|
|
124
150
|
Use this package when your client speaks only stdio, or when you would rather
|
|
125
151
|
the credential stayed in a local config file than in a client's cloud
|
|
126
152
|
configuration.
|
|
@@ -164,7 +190,12 @@ the contract there, then re-vendor it with
|
|
|
164
190
|
`pnpm run contract:check -- --write` and commit the result. No source file in
|
|
165
191
|
this package describes a tool.
|
|
166
192
|
|
|
167
|
-
|
|
193
|
+
`server.json` is the entry the [official MCP registry](https://registry.modelcontextprotocol.io)
|
|
194
|
+
serves, and it repeats the version — a test fails if it stops matching
|
|
195
|
+
`package.json`, so bump both together.
|
|
196
|
+
|
|
197
|
+
Releasing is documented in [NPM-SETUP.md](./NPM-SETUP.md) (npm) and
|
|
198
|
+
[REGISTRY.md](./REGISTRY.md) (the MCP registry).
|
|
168
199
|
|
|
169
200
|
## License
|
|
170
201
|
|
package/package.json
CHANGED
|
@@ -1,15 +1,27 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "fettle-mcp",
|
|
3
|
-
"version": "0.1.
|
|
3
|
+
"version": "0.1.1",
|
|
4
|
+
"mcpName": "sh.fettle/mcp",
|
|
4
5
|
"description": "MCP server for Fettle (fettle.sh) uptime monitoring — manage monitors, incidents, heartbeats and status pages from any MCP client.",
|
|
5
6
|
"keywords": [
|
|
6
7
|
"mcp",
|
|
8
|
+
"mcp-server",
|
|
7
9
|
"modelcontextprotocol",
|
|
10
|
+
"model-context-protocol",
|
|
8
11
|
"fettle",
|
|
12
|
+
"fettle.sh",
|
|
9
13
|
"uptime",
|
|
10
|
-
"monitoring",
|
|
14
|
+
"uptime-monitoring",
|
|
15
|
+
"website-monitoring",
|
|
16
|
+
"status-page",
|
|
17
|
+
"incidents",
|
|
18
|
+
"heartbeat",
|
|
19
|
+
"cron-monitoring",
|
|
20
|
+
"ssl-expiry",
|
|
11
21
|
"claude",
|
|
12
|
-
"
|
|
22
|
+
"claude-code",
|
|
23
|
+
"cursor",
|
|
24
|
+
"windsurf"
|
|
13
25
|
],
|
|
14
26
|
"homepage": "https://fettle.sh",
|
|
15
27
|
"repository": {
|