edit_incident
Edit Incident
Update an existing incident's properties such as name, summary, severity, status, custom fields, role assignments, and timestamps. Optionally notify the incident channel about the changes.
Ask your agent in plain language. Each of these maps to a real tool on the server.
edit_incident
Update an existing incident's properties such as name, summary, severity, status, custom fields, role assignments, and timestamps. Optionally notify the incident channel about the changes.
list_users
List users in your incident.io organization with pagination. Returns user names, emails, and roles.
list_workflows
List all configured automation workflows. Returns workflow names, triggers, and enabled status. Useful for understanding what automated actions are configured in your incident.io account.
list_incident_roles_and_types
Retrieve all configured incident roles and incident types. Useful for looking up valid IDs when creating or editing incidents, and understanding how incidents are categorized.
list_incidents
List and filter incidents in your incident.io account. Supports filtering by status, severity, status category, incident type, mode, and creation date. Returns paginated results sorted by creation time.
manage_catalog_entry
Create, update, or delete a catalog entry. Use **create** to add a new entry to a catalog type, **update** to modify an existing entry's name, external ID, aliases, or attributes, and **delete** to archive an entry.
create_schedule_override
Create an override on an on-call schedule. Overrides temporarily replace the scheduled on-call person for a specific rotation and layer during a given time window.
list_catalog_entries
List entries for a given catalog type. Catalog entries represent items like services, teams, or environments in your service catalog. Returns names, external IDs, aliases, and attribute values.
get_schedule_entries
Retrieve on-call schedule entries for a given time window. Shows who is on-call during each period, useful for understanding coverage and identifying who is responsible at a given time.
list_severities_and_statuses
Retrieve all configured incident severities and statuses. Useful for looking up valid IDs before creating or editing incidents.
create_incident
Declare a new incident in incident.io. Supports setting visibility, severity, status, type, mode, custom fields, role assignments, and timestamps.
list_schedules
List all on-call schedules configured in your incident.io account. Returns schedule names, timezones, rotation configurations, and team associations.
list_follow_ups
List post-incident follow-up items (actions). Can filter by incident to show follow-ups for a specific incident, or list all follow-ups across the organization.
send_alert_event
Ingest an alert event into incident.io via an HTTP alert source. Use this to trigger or resolve alerts from external monitoring tools. Supports deduplication keys and custom metadata.
list_alerts
List all alerts in your incident.io account with pagination support. Returns alert details including title, status, and source information.
get_incident
Retrieve full details of a single incident by its ID or numeric reference (e.g. "123" for INC-123). Returns complete incident data including severity, status, custom fields, role assignments, timestamps, and duration metrics.
manage_status_page_incident
Create or update a status page incident. Use **create** to publish a new incident to a status page, or **update** to change an existing status page incident's status, message, or affected components. You can also post an update message to an existing incident.
list_catalog_types
List all catalog types in your incident.io service catalog. Catalog types define schemas for entries like services, teams, and environments. Useful for discovering available catalog type IDs before querying entries.
get_schedule
Retrieve an on-call schedule, including rotation and layer configuration needed to create an override.
delete_schedule_override
Remove an on-call override and restore the underlying scheduled coverage. This can change who is paged.
list_status_pages
Discover status page IDs, names and public URLs before publishing an incident.
get_identity
Verify the authenticated API key name, permissions and organization dashboard.
get_catalog_entry
Read a catalog entry, its type, aliases, attributes and archive state.
get_status_page_incident
Read a published status page incident, its current status, updates and component impacts.
list_alert_sources
Discover configured alert sources and HTTP configuration IDs. Secrets are excluded; sending events requires the source secret in authentication.
Every client uses the same Magic MCP URL, and so does any other MCP client. Add it once and sign in with SSO.
{"mcpServers": {"metorial": {"url": "<your-magic-mcp-url>"}}}
claude mcp add --transport http metorial <your-magic-mcp-url>
codex mcp add metorial --url <your-magic-mcp-url>codex mcp login metorial
One governed layer for every app your agents reach, not a separate connector per tool.
Declare, read and edit incidents; ingest HTTP alert events; inspect on-call coverage and manage temporary overrides; maintain catalog entries; discover status pages and publish incident updates. Read incident configuration, users, follow-ups and automation workflows.
Common questions about connecting Incidentio to AI agents with Metorial.