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: apps/docs/content/docs/agents/mcp.mdx
+4Lines changed: 4 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -85,6 +85,10 @@ Tool validation badges appear on servers with issues — for example, if a tool
85
85
86
86
Self-hosted deployments can restrict which MCP server domains are allowed by setting the `ALLOWED_MCP_DOMAINS` environment variable (comma-separated list). When set, only servers on approved domains can be added. When unset, all domains are allowed.
87
87
88
+
This governs which domains may be used. It is separate from where those domains are allowed to resolve: an MCP server on a private address is reached by naming it in `EGRESS_ALLOWED_HOSTS` or `EGRESS_ALLOWED_IP_RANGES`, described in [Security](/platform/self-hosting/security#the-ssrf-boundary). Both checks apply.
89
+
90
+
The allowlist covers the server URL itself. If the server requires OAuth, any endpoint its metadata names on a *different* origin than the server you configured is treated as content rather than as configuration, so that one has to be publicly routable. Endpoints on the server's own origin keep the server's reachability.
91
+
88
92
## Using MCP Tools in Agents
89
93
90
94
Once MCP servers are configured, their tools become available within your agent blocks:
Copy file name to clipboardExpand all lines: apps/docs/content/docs/integrations/github.mdx
+6-5Lines changed: 6 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1019,10 +1019,10 @@ Update branch protection rules for a specific branch, including status checks, r
1019
1019
|`owner`| string | Yes | Repository owner \(user or organization\)|
1020
1020
|`repo`| string | Yes | Repository name |
1021
1021
|`branch`| string | Yes | Branch name |
1022
-
|`required_status_checks`| object |Yes| Required status check configuration\(null to disable\). Object with strict \(boolean\) and contexts \(string array\)|
1023
-
|`enforce_admins`| boolean |Yes| Whether to enforce restrictions for administrators |
1024
-
|`required_pull_request_reviews`| object |Yes| PR review requirements\(null to disable\). Object with optional required_approving_review_count, dismiss_stale_reviews, require_code_owner_reviews |
1025
-
|`restrictions`| object |Yes| Push restrictions\(null to disable\). Object with users \(string array\)and teams \(string array\)|
1022
+
|`required_status_checks`| object |No| Required status check configuration. Object with strict \(boolean\) and contexts \(string array\). Omit to disable status checks — GitHub receives an explicit null.|
1023
+
|`enforce_admins`| boolean |No| Whether to enforce restrictions for administrators. Omit to disable admin enforcement — GitHub receives an explicit null.|
1024
+
|`required_pull_request_reviews`| object |No| PR review requirements. Object with optional required_approving_review_count, dismiss_stale_reviews, require_code_owner_reviews. Omit to disable review requirements — GitHub receives an explicit null.|
1025
+
|`restrictions`| object |No| Push restrictions, available only for organization-owned repositories. Object with users \(string array\), teams \(string array\)and optional apps \(string array\). Omit to disable push restrictions — GitHub receives an explicit null.|
1026
1026
|`apiKey`| string | Yes | GitHub Personal Access Token |
1027
1027
1028
1028
#### Output
@@ -1805,14 +1805,15 @@ Trigger a workflow dispatch event for a GitHub Actions workflow. The workflow mu
1805
1805
1806
1806
### GitHub List Workflow Runs
1807
1807
1808
-
List workflow runs for a repository. Supports filtering by actor, branch, event, and status. Returns run details including status, conclusion, and links.
1808
+
List workflow runs for a repository, or for a single workflow when a workflow ID or filename is given. Supports filtering by actor, branch, event, and status. Returns run details including status, conclusion, and links.
1809
1809
1810
1810
#### Input
1811
1811
1812
1812
| Parameter | Type | Required | Description |
1813
1813
| --------- | ---- | -------- | ----------- |
1814
1814
|`owner`| string | Yes | Repository owner \(user or organization\)|
1815
1815
|`repo`| string | Yes | Repository name |
1816
+
|`workflow_id`| string | No | The ID of the workflow. You can also pass the workflow file name as a string \(e.g., ci.yml\). Omit to list runs across the whole repository. |
1816
1817
|`actor`| string | No | Filter by user who triggered the workflow |
1817
1818
|`branch`| string | No | Filter by branch name |
1818
1819
|`event`| string | No | Filter by event type \(e.g., push, pull_request, workflow_dispatch\)|
| ↳ `call_url`| string | URL for the incident call/bridge |
211
206
| ↳ `severity`| object | Severity of the incident |
@@ -221,7 +216,7 @@ Update an existing incident in incident.io. Can update name, summary, severity,
221
216
| ↳ `name`| string | Type name |
222
217
| ↳ `created_at`| string | Creation timestamp |
223
218
| ↳ `updated_at`| string | Last update timestamp |
224
-
| ↳ `incident_url`| string |URL to the incident |
219
+
| ↳ `permalink`| string |Permalink to the incident in incident.io|
225
220
| ↳ `slack_channel_id`| string | Associated Slack channel ID |
226
221
| ↳ `slack_channel_name`| string | Associated Slack channel name |
227
222
| ↳ `visibility`| string | Incident visibility |
@@ -486,7 +481,7 @@ Create a new workflow in incident.io.
486
481
|`trigger`| string | No | Trigger type for the workflow \(e.g., "incident.updated", "incident.created"\)|
487
482
|`steps`| string | No | Array of workflow steps as JSON string. Example: \[\{"label": "Notify team", "name": "slack.post_message"\}\]|
488
483
|`condition_groups`| string | No | Array of condition groups as JSON string to control when the workflow runs. Example: \[\{"conditions": \[\{"operation": "one_of", "param_bindings": \[\], "subject": "incident.severity"\}\]\}\]|
489
-
|`runs_on_incidents`| string | No | When to run the workflow: "newly_created" \(only new incidents\), "newly_created_and_active" \(new and active incidents\), "active" \(only active incidents\), or "all" \(all incidents\)|
484
+
|`runs_on_incidents`| string | No | When to run the workflow: "newly_created" \(only newly created incidents\) or "newly_created_and_active" \(newly created and already active incidents\)|
490
485
|`runs_on_incident_modes`| string | No | Array of incident modes to run on as JSON string. Example: \["standard", "retrospective"\]|
491
486
|`include_private_incidents`| boolean | No | Whether to include private incidents |
492
487
|`continue_on_step_error`| boolean | No | Whether to continue executing subsequent steps if a step fails |
@@ -569,7 +564,7 @@ Update an existing workflow in incident.io.
569
564
|`name`| string | Yes | New name for the workflow \(e.g., "Notify on Critical Incidents"\)|
570
565
|`steps`| string | Yes | Complete array of workflow steps as a JSON string |
571
566
|`condition_groups`| string | Yes | Complete array of workflow condition groups as a JSON string |
572
-
|`runs_on_incidents`| string | Yes | When to run the workflow: newly_created, newly_created_and_active, active, or all|
567
+
|`runs_on_incidents`| string | Yes | When to run the workflow: newly_createdor newly_created_and_active|
573
568
|`runs_on_incident_modes`| string | Yes | Complete array of incident modes to run on as a JSON string |
574
569
|`include_private_incidents`| boolean | Yes | Whether to include private incidents |
575
570
|`continue_on_step_error`| boolean | Yes | Whether to continue executing subsequent steps if a step fails |
@@ -783,11 +778,15 @@ List all escalation policies in incident.io
783
778
784
779
| Parameter | Type | Description |
785
780
| --------- | ---- | ----------- |
786
-
|`escalations`| array | List of escalation policies |
787
-
| ↳ `id`| string | The escalation policy ID |
788
-
| ↳ `name`| string | The escalation policy name |
789
-
| ↳ `created_at`| string | When the escalation policy was created |
790
-
| ↳ `updated_at`| string | When the escalation policy was last updated |
781
+
|`escalations`| array | List of escalations |
782
+
| ↳ `id`| string | The escalation ID |
783
+
| ↳ `title`| string | The escalation title |
784
+
| ↳ `status`| string | The current escalation status |
785
+
| ↳ `description`| string | Additional detail provided with this escalation |
786
+
| ↳ `priority`| object | The escalation priority |
787
+
| ↳ `name`| string | Priority name |
788
+
| ↳ `created_at`| string | When the escalation was created |
789
+
| ↳ `updated_at`| string | When the escalation was last updated |
0 commit comments