You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/guides/modules/toolkit/pages/using-the-circleci-mcp-server.adoc
+32Lines changed: 32 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -237,6 +237,25 @@ The tool provides:
237
237
* Configuration recommendations.
238
238
* Best practices for CircleCI configuration.
239
239
240
+
=== Rollback Tool (`run_rollback_pipeline`)
241
+
242
+
This tool executes rollback operations for CircleCI projects, enabling you to revert
243
+
deployments to previous versions by either running your configured rollback pipeline or rerunning your workflow.
244
+
245
+
The tool provides:
246
+
247
+
- Interactive rollback process with guided parameter collection.
248
+
- Project resolution from either project slug or project ID.
249
+
- Target environment selection.
250
+
- Component version selection assistance.
251
+
- Rollback pipeline execution or workflow rerun options.
252
+
- Clear error handling and configuration guidance.
253
+
254
+
Prerequisites:
255
+
256
+
- In order to trigger the rollback using a Rollback pipeline, the pipeline must be configured in the project. See the xref:deploy:set-up-rollbacks.adoc[Set up rollbacks] page for help.
257
+
- Deploy markers should be set up for version tracking. See the xref:deploy:configure-deploy-markers.adoc[Configure deploy markers] page for help.
258
+
240
259
== Real-world examples
241
260
242
261
Here are common scenarios where the CircleCI MCP server can help you and your team:
@@ -268,6 +287,19 @@ Your team wastes time with unreliable tests:
268
287
. Your assistant explains the issues and suggests improvements to you.
269
288
. You fix the tests and improve the reliability of your pipeline.
270
289
290
+
=== Example 4: Emergency production rollback using rollback pipeline
291
+
292
+
A critical bug is discovered in production after your latest deployment:
293
+
294
+
. You tell your assistant: "I need to rollback the frontend component in production
295
+
due to a critical bug"
296
+
. The assistant lists your followed projects and you select the affected project.
297
+
. The MCP server fetches available component versions and you choose the last known
298
+
good version.
299
+
. You provide the rollback reason: "Critical authentication bug affecting user login"
300
+
. The assistant executes the rollback pipeline, reverting to the stable version
301
+
within minutes.
302
+
271
303
== Troubleshooting
272
304
273
305
For general MCP server troubleshooting steps, see the link:https://modelcontextprotocol.io/docs/tools/debugging[Model Context Protocol docs].
0 commit comments