Be the first to get access to new connectors. Get early access →
ConnectorBay Early access
Discover
incident.io (BYOK) icon

incident.io (BYOK)

Read your incident.io incidents, updates, severities, statuses, roles, types, actions, follow-ups, users, on-call schedules and alerts with your own API key

Unify Dynamics LLC

Tools12read-only
Sign-inBYOKbring your own key
Key keptNeverused for one call only
PriceFreeoptional Pro limits
Providerincident.iounofficial, not affiliated
Works withMCP · RESTany agent

Try asking

Real questions, and the tools your agent calls to answer them.

What incidents are live in incident.io right now?
Tools called
list_incidents
Show the details of incident.io incident 01FCNDV6P870EA6S7TK1DSYDG0
Tools called
get_incident
What updates were posted on incident 01FCNDV6P870EA6S7TK1DSYDG0?
Tools called
list_incident_updates
What severity levels does incident.io have?
Tools called
list_severities
What incident statuses are configured in incident.io?
Tools called
list_incident_statuses
Which incident roles are defined in incident.io?
Tools called
list_incident_roles

About

incident.io (BYOK) lets an AI assistant read your own incident.io data through the incident.io API with a key you supply (incident.io API key (Settings > API keys; view scopes are enough)). Read-only: 12 tools (list_incidents, get_incident, list_incident_updates, list_severities, list_incident_statuses, list_incident_roles, list_incident_types, list_actions, list_follow_ups, list_users, list_schedules, list_alerts). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to api.incident.io. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by incident.io. incident.io and its logos are trademarks of their owners and are used only to say which service the connector works with.

Sources: Live from the incident.io API (api.incident.io) with a BYOK key; documentation: https://docs.incident.io/api-reference/incidents-v2/list. Endpoints checked against that documentation on 2026-10-16.

Privacy

The publisher, Unify Dynamics LLC, states that tool inputs are processed in memory and not retained.

Data not collectedNo account, no profile, no stored prompts or results.

What it can do

12 tools, grouped by job. Every one is read-only or compute-only.

OpenAPI
Read your data12 tools
  • List incidentsList incidents (newest first by default) with reference, name, summary, link, status and category, severity, type and timestamps.
  • Get incidentGet one incident by id with name, summary, status, severity, type, role assignments, timestamps and links.
  • List incident updatesList incident updates (status posts) with message, new status and severity and who posted it, optionally for one incident; cursor-paged.
  • List severitiesList the severity levels with name, description and rank.
  • List incident statusesList the incident statuses with name, category (triage, live, learning, paused, closed, declined, canceled, merged) and rank.
  • List incident rolesList incident roles (for example lead and reporter) with name, short form, type and instructions.
  • List incident typesList incident types with name, description, default flag and whether they start in triage.
  • List actionsList incident actions (tasks) with description, status (outstanding, completed, deleted, not_doing), assignee and completion time, optionally for…
  • List follow upsList follow-ups with title, status, priority, assignee, labels and completion time, optionally for one incident or one assignee team.
  • List usersList users with name, email, role, whether active and Slack id; filter by email; cursor-paged.
  • List schedulesList on-call schedules with name, time zone, team ids, who is on call now and rotations.
  • List alertsList alerts with title, status (firing or resolved), description, source link, tags and times; filter by status or creation time; cursor-paged.

Information

PublisherUnify Dynamics LLC
CategoryDeveloper tools
LanguagesEnglish
Built forWorldwide
CompatibilityAny MCP client · any agent · REST
Version0.1.0
MCP endpointhttps://byok-incidentio.connectorbay.com/mcp
REST APIopenapi.json
SupportGet help · Status
CountryWorldwide
FunctionOther
LayerDeep connectors

More like this

More in Other

Hetzner Cloud Load Balancers (BYOK)

Read your Hetzner Cloud load balancers, certificates, primary IPs and placement groups with your own project API token

Live · MCP + REST5 tools

Hetzner Cloud DNS (BYOK)

Read your Hetzner Cloud DNS zones, delegation status and record sets (RRSets) with your own project API token

Live · MCP + REST5 tools

Hetzner Cloud Catalog (BYOK)

Read the Hetzner Cloud server types, load balancer types, OS images, ISOs and price list with your own project API token

Live · MCP + REST7 tools

Front Knowledge Base (BYOK)

Read the structure of your Front knowledge bases: bases, categories and articles with locales, slugs and dates (no article text), with your own API token

Live · MCP + REST7 tools

Front Workspace (BYOK)

Read how your Front workspace is set up: teams, teammate groups, rules (names only), shifts, ticket statuses, tags and custom field definitions, with your own API token

Live · MCP + REST12 tools

Pipedrive Access (BYOK)

Read how access is organised in Pipedrive: roles, role settings, permission sets, teams and users (no email or phone) with your own personal API token

Live · MCP + REST8 tools

Get incident.io (BYOK)

Free · BYOK · Read-only

BYOK: bring your own keyThis connector uses your own incident.io incident.io API key (Settings > API keys; view scopes are enough). Create one at https://docs.incident.io/api-reference/incidents-v2/list, with the fewest permissions it needs (read-only if the provider offers it). Your assistant sends it in the X-Upstream-Key header with every request. It is used for that one call only: never stored, logged or cached, and only ever sent to incident.io. Revoke it at the provider whenever you like. Unofficial connector: not affiliated with incident.io.