App

Connect Spike.sh to any app

Spike is an incident management system with unlimited alerts and on-call schedules

Connects with an API keyspike.sh

What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it.

Build solutions, not workarounds.

What do you want to automate with Spike.sh?

Ask the assistant

You'll sign in before anything runs. What you typed comes with you.

Connect your AI client

Give your AI client this address.

https://mcp.apiant.ai

Any client that takes a remote MCP server. Nothing to install. Create your free account, then sign in once in your browser.

Set it up in your client
Claude Code

Run this in the directory you want to work in.

claude mcp add --transport http -s project apiant-ai https://mcp.apiant.ai

Start Claude Code there, approve the server, and sign in in the browser page it opens.

Claude Code guide (opens in a new tab)
Claude, web and desktop

Open Customize, then Connectors, then Add custom connector, and paste the address. On Team and Enterprise an owner adds it first.

Setup guide (opens in a new tab)
Cursor

Add the address to your MCP configuration as a server URL. Cursor signs you in in your browser.

Setup guide (opens in a new tab)
Zed

Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server.

Setup guide (opens in a new tab)
Codex and the ChatGPT desktop app

Open Settings, then MCP servers, then Add server, and choose Streamable HTTP. From the terminal, Codex takes the address with its own add command and then signs you in.

Setup guide (opens in a new tab)
Any other MCP client

Paste the address where the client asks for a remote MCP server URL, and name the server apiant-ai where it lets you. APIANT's skills reach the client over the same connection.

Setup guide (opens in a new tab)

Pair it

Connect Spike.sh with another app

What your agent can do with Spike.sh

Triggers and actions 25 actions

  • Action
    Acknowledge incident

    Acknowledge one or more Spike.sh incidents by counter id or incident id.

  • Action
    Add alert rule

    Create a new alert routing/automation rule with conditions and actions.

  • Action
    Add escalation

    Creates a new escalation policy for a Spike.sh team, defining who is notified, through which channel, and how long to wait between steps.

  • Action
    Add integration

    Create a new integration for a team (source system that sends alerts into Spike).

  • Action
    Add on-call

    Create a new on-call schedule for a team.

  • Action
    Add service

    Create a new service in a team, with name and description.

  • Action
    Create Incident

    Creates a Spike incident through one of your integrations and sends alerts. The integration decides which service and escalation policy the incident is routed to.

  • Action
    Delete alert rule

    Archives (soft-deletes) a Spike alert rule so it no longer applies to incoming incidents.

  • Action
    Delete escalation

    Archives (soft-deletes) a Spike escalation policy by its ID.

  • Action
    Escalate incident

    Escalates one or more Spike incidents to the next step of their escalation policy.

  • Action
    Get escalation

    Get escalation policy details by id.

  • Action
    Get incident

    Fetch a single incident by counter id.

  • Action
    Get integration

    Fetches an integration by its token, including its name, type, service, escalation settings and webhook URL. An error occurs if the integration is not found.

  • Action
    Get service

    Get a Spike service's details, along with its incidents and open-incident count.

  • Action
    List alert rules

    Lists all alert rules (enabled and disabled) configured for a Spike team.

  • Action
    List escalations

    Lists the escalation policies that belong to a Spike team.

  • Action
    List incidents

    Lists the incidents for a Spike.sh team.

  • Action
    List on-calls

    Lists the on-call schedules for a team.

  • Action
    List services

    Lists the services in a Spike team.

  • Action
    List teams

    Lists every team in your Spike organisation. Use a team's ID from here wherever other Spike actions ask for a team.

  • Action
    Resolve incident

    Resolve one or more incidents by counter id array.

  • Action
    Update alert rule

    Replace an existing Spike alert rule's name, conditions and actions.

  • Action
    Update escalation

    Replaces an existing escalation policy's name, steps and start delay. The whole policy is replaced, so send every step you want to keep.

  • Action
    Update on-call

    Updates an on-call schedule's name and/or moves it to another team. Rotations and layers are not changed by this action.

  • Action
    Update service

    Updates the name and/or description of an existing Spike.sh service.

Reviews

What our customers say

Questions

Spike.sh, answered

What can your agent do in Spike.sh?

Any of Spike.sh's 25 actions, including Create Incident, Update alert rule, Update escalation and Update on-call. Your agent maps the data both ways and tests every scenario before it ships.

Which apps can Spike.sh connect to?

Any app in the catalog; the list on this page pairs Spike.sh with each of them. If the other app is missing, point your agent at its API documentation and it builds the connector.

What happens when something fails?

Your agent works that out for you. It plans the failure paths along with the happy path, then tests every scenario before it ships.

Is there a free plan?

Yes. Every plan includes the agent, including free, and building from your own AI client spends no assistant credits.