@cronicorn/mcp-server 1.6.1 → 1.7.0
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 +144 -0
- package/dist/index.js +630 -0
- package/dist/index.js.map +1 -1
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -145,6 +145,135 @@ On first run, the server will:
|
|
|
145
145
|
|
|
146
146
|
Subsequent runs will use the stored access token automatically.
|
|
147
147
|
|
|
148
|
+
## Prompts (Slash Commands)
|
|
149
|
+
|
|
150
|
+
Prompts are interactive conversation starters that guide you through common Cronicorn workflows. They're triggered using slash commands in your AI assistant.
|
|
151
|
+
|
|
152
|
+
### Available Prompts
|
|
153
|
+
|
|
154
|
+
#### `/setup-first-job` - Get Started with Cronicorn
|
|
155
|
+
|
|
156
|
+
Interactive guide for creating your first scheduled job. Works for all scenarios including new users and migrations from other cron systems.
|
|
157
|
+
|
|
158
|
+
**Optional Arguments:**
|
|
159
|
+
- `task_description`: What the job should do
|
|
160
|
+
- `endpoint_url`: HTTP endpoint to call
|
|
161
|
+
- `schedule_type`: "interval" or "cron"
|
|
162
|
+
|
|
163
|
+
**Example Usage (GitHub Copilot):**
|
|
164
|
+
|
|
165
|
+
In GitHub Copilot Chat, type:
|
|
166
|
+
```
|
|
167
|
+
@cronicorn /setup-first-job
|
|
168
|
+
```
|
|
169
|
+
|
|
170
|
+
Or with arguments:
|
|
171
|
+
```
|
|
172
|
+
@cronicorn /setup-first-job task_description="check API health every 5 minutes" endpoint_url="https://api.myapp.com/health"
|
|
173
|
+
```
|
|
174
|
+
|
|
175
|
+
The prompt will guide you through:
|
|
176
|
+
1. Understanding jobs vs endpoints
|
|
177
|
+
2. Creating a job container
|
|
178
|
+
3. Adding your HTTP endpoint
|
|
179
|
+
4. Configuring baseline schedules
|
|
180
|
+
5. Setting safety constraints
|
|
181
|
+
6. Enabling AI adaptation
|
|
182
|
+
|
|
183
|
+
**What You'll Learn:**
|
|
184
|
+
- Jobs vs endpoints (containers vs execution units)
|
|
185
|
+
- Baseline schedules (cron vs interval)
|
|
186
|
+
- AI hints for dynamic scheduling
|
|
187
|
+
- Safety constraints (min/max intervals)
|
|
188
|
+
- Response body instrumentation
|
|
189
|
+
|
|
190
|
+
---
|
|
191
|
+
|
|
192
|
+
#### `/troubleshoot-failures` - Debug Failing Endpoints
|
|
193
|
+
|
|
194
|
+
Debug failing job executions and identify solutions.
|
|
195
|
+
|
|
196
|
+
**Optional Arguments:**
|
|
197
|
+
- `job_or_endpoint_name`: Name/ID of failing endpoint
|
|
198
|
+
- `error_description`: Error symptoms
|
|
199
|
+
- `when_started`: "just-now", "today", "this-week", or "longer"
|
|
200
|
+
|
|
201
|
+
**Example Usage (GitHub Copilot):**
|
|
202
|
+
|
|
203
|
+
```
|
|
204
|
+
@cronicorn /troubleshoot-failures job_or_endpoint_name="payment-processor" error_description="timeout errors" when_started="today"
|
|
205
|
+
```
|
|
206
|
+
|
|
207
|
+
The prompt will guide you through:
|
|
208
|
+
1. Identifying the failing endpoint
|
|
209
|
+
2. Reviewing run history for patterns
|
|
210
|
+
3. Analyzing error details (status codes, messages)
|
|
211
|
+
4. Checking AI hints and scheduling state
|
|
212
|
+
5. Inspecting response bodies
|
|
213
|
+
6. Applying fixes (constraints, pausing, configuration)
|
|
214
|
+
|
|
215
|
+
**Common Issues Covered:**
|
|
216
|
+
- Timeout errors (increase timeout/execution time)
|
|
217
|
+
- Rate limiting (429 errors, adjust min interval)
|
|
218
|
+
- Service unavailable (500/503, pause endpoint)
|
|
219
|
+
- Authentication failures (401/403, fix headers)
|
|
220
|
+
- Network issues (connection refused, DNS)
|
|
221
|
+
- Response body problems (size limits, structure)
|
|
222
|
+
|
|
223
|
+
---
|
|
224
|
+
|
|
225
|
+
### Using Prompts in GitHub Copilot
|
|
226
|
+
|
|
227
|
+
**In VS Code with GitHub Copilot Chat:**
|
|
228
|
+
|
|
229
|
+
1. Open GitHub Copilot Chat (Click the chat icon or `Ctrl+Shift+I` / `Cmd+Shift+I`)
|
|
230
|
+
|
|
231
|
+
2. Use the `@cronicorn` agent with a slash command:
|
|
232
|
+
```
|
|
233
|
+
@cronicorn /setup-first-job
|
|
234
|
+
```
|
|
235
|
+
|
|
236
|
+
3. Copilot will run the prompt and guide you through the workflow
|
|
237
|
+
|
|
238
|
+
4. Provide arguments inline:
|
|
239
|
+
```
|
|
240
|
+
@cronicorn /migrate-from-cron current_system="vercel-cron" job_count="10"
|
|
241
|
+
```
|
|
242
|
+
|
|
243
|
+
5. Follow the interactive guidance to complete your task
|
|
244
|
+
|
|
245
|
+
**Tips for Best Results:**
|
|
246
|
+
|
|
247
|
+
- **Start broad**: Use prompts without arguments to get full guidance
|
|
248
|
+
- **Provide context**: Include arguments when you have specific info
|
|
249
|
+
- **Follow suggestions**: Prompts reference specific tools to use next
|
|
250
|
+
- **Check resources**: Prompts include doc links for deeper learning
|
|
251
|
+
|
|
252
|
+
**Note:** GitHub Copilot doesn't automatically load bundled resources like Claude Desktop does, but prompts include embedded summaries and hosted doc URLs for universal access.
|
|
253
|
+
|
|
254
|
+
---
|
|
255
|
+
|
|
256
|
+
### Using Prompts in Claude Desktop
|
|
257
|
+
|
|
258
|
+
**In Claude Desktop:**
|
|
259
|
+
|
|
260
|
+
1. Type a slash command in the chat:
|
|
261
|
+
```
|
|
262
|
+
/setup-first-job
|
|
263
|
+
```
|
|
264
|
+
|
|
265
|
+
2. Claude will execute the prompt and start guiding you
|
|
266
|
+
|
|
267
|
+
3. Prompts can reference bundled documentation resources:
|
|
268
|
+
```
|
|
269
|
+
file:///docs/quick-start.md
|
|
270
|
+
file:///docs/core-concepts.md
|
|
271
|
+
```
|
|
272
|
+
|
|
273
|
+
4. Claude automatically loads these resources for additional context
|
|
274
|
+
|
|
275
|
+
---
|
|
276
|
+
|
|
148
277
|
## Keeping Updated
|
|
149
278
|
|
|
150
279
|
The MCP server does not automatically update. When using `npx` or global installation, you'll continue using the cached version until you manually update.
|
|
@@ -345,6 +474,21 @@ git push --follow-tags
|
|
|
345
474
|
|
|
346
475
|
**Note**: Only production dependency is `@modelcontextprotocol/sdk` - everything else is bundled.
|
|
347
476
|
|
|
477
|
+
## Alternative: Context7 Documentation Access
|
|
478
|
+
|
|
479
|
+
If you have the [Context7 MCP server](https://context7.com) installed alongside Cronicorn MCP, you can access Cronicorn documentation directly in your AI assistant:
|
|
480
|
+
|
|
481
|
+
```
|
|
482
|
+
@context7 /weskerllc/cronicorn
|
|
483
|
+
```
|
|
484
|
+
|
|
485
|
+
This provides an alternative way to access up-to-date Cronicorn documentation without leaving your conversation. Context7 complements the Cronicorn MCP server's prompts and bundled resources.
|
|
486
|
+
|
|
487
|
+
**Use cases:**
|
|
488
|
+
- Quick doc lookups while working with Cronicorn MCP tools
|
|
489
|
+
- Access to the latest documentation updates
|
|
490
|
+
- Cross-reference between different sections of the docs
|
|
491
|
+
|
|
348
492
|
## Security
|
|
349
493
|
|
|
350
494
|
- OAuth 2.0 Device Authorization Grant for secure authentication
|