Skip to main content
If you’re seeing a message that multiple incident.io MCP servers have been detected, it means your coding agent may be connected to incident.io more than once. This can cause unexpected behavior as tools may be duplicated, responses may conflict, or you might see errors. The macOS app already includes a built-in MCP server, so you don’t need a separate one configured alongside it.

​
How to check

Ask your coding agent: “Do I have multiple MCPs enabled for incident.io?” It will be able to check and tell you. If you do have duplicates, follow the steps below to remove them.

​
How to fix it

If you’re using the macOS app, the quickest fix is to turn off its MCP proxy, which stops it serving a duplicate set of tools while keeping your other connection in place. In the desktop app, go to Settings → Problems with MCP? and turn off MCP Proxy. Alternatively, remove the extra server entirely:
  1. Remove the extra incident.io MCP server entry from your coding agent’s settings. If you’re using the macOS app, keep that and remove any other incident.io MCP server (e.g. the one pointing at https://mcp.incident.io/mcp).
  2. Once removed, you can delete the corresponding plugin key in incident.io. You can manage your plugin keys in Settings > Plugin keys.
That’s it — the remaining MCP server will continue to work as normal with no further setup needed.

​
Using both in different tools

This only applies when multiple incident.io MCP servers are installed in the same coding agent. If you have different tools each connected to incident.io separately, there’s no issue — they operate independently.