How to connect Instatus to Grok Bot

Connect Grok Bot to Instatus MCP. Create incident for api outage, update maintenance window status page, and more using natural language, with authentication handled for you.

Instatus logoInstatus
Api Key

Instatus is a status page and incident communication platform for service health, incidents, maintenance, monitors, and subscribers. Use it to keep customers informed during outages, planned work, and live service updates.

15 Tools

Introduction

Grok is xAI's assistant, and its bot builder lets you create a personal agent that holds context, runs skills, and connects to the apps you already use through plugins.

This guide explains how to connect Instatus to a Grok bot using Composio Connect, which handles OAuth, token refresh, and reliability so you do not have to. You add Composio as a plugin, authenticate once, then ask your bot to work with Instatus in plain language.

For exact tool slugs and parameter tables, see the tool catalog in the Composio docs.

Why use Composio?

Composio exposes 1,700+ apps to your Grok bot through a single connection, so you get:

  • Connect to 1,700+ apps with on-demand tool loading, so you do not fill your context window with unnecessary tool definitions.
  • Use programmatic tool calling through a remote workbench, letting the model write its own code to handle complex tool chaining. This reduces back-and-forth for frequent tool calls.
  • Handle large tool responses outside the model context to keep conversations lean.

Connecting Instatus to Grok Bot

Once Grok Bot is set up, you connect Instatus entirely from its interface, and the whole flow takes under a minute.

Set up Grok Bot

Get access. Grok Bot is included with Cursor Ultra, Cursor Premium Teams, and SuperGrok Heavy. Get the desktop app for macOS or Windows from x.ai/bot and sign in. An iPhone companion app is also available, and your bots sync across devices.

Create a bot. Pick a suggested role or define your own, then give it a short name, one primary job, and a short description of how it should work. Focused bots work best, because a clear role gives the bot more useful context over time.

Connect Instatus

1. Add the Composio plugin

Click the button. The Composio listing on x.ai opens and launches Grok Bot for you. If the app does not open on its own, click Add to Grok Bot.

Add to Grok Bot

Composio for Grok Bot listing on x.ai with the Add to Grok Bot button

Grok Bot opens the Composio plugin, showing its connector and skills. Click Add.

Composio plugin sheet in Grok Bot with the Add button

2. Authenticate

Go to the Installed section and click the Composio entry. You'll see its connector and skills listed.

Installed Composio plugin showing the Authenticate button

Click Authenticate. You'll be taken to the Composio consent screen. Review the access it requests and click Authorize. Composio handles the OAuth handshake for you, so you never touch API keys or tokens.

Composio authorization screen with Authorize and Deny

3. Connect your Instatus account

Back in the chat, ask your bot to connect to Instatus or give it any Instatus task.

For example, ask it to:

  • "Create incident for API outage"
  • "Update maintenance window status page"
  • "List subscribers for status updates"

It will prompt you to authenticate and authorize access.

That's it. Composio's tools are now available in your Grok bot, and your Instatus account is ready to use.

What is Grok Bot?

Grok is xAI's assistant, available as a chat interface and a bot builder for creating personal agents that run skills and connect to external apps.

With Composio Connect, your Grok bot can securely access apps like Instatus through MCP without you sharing account credentials directly with the agent.

What is the Instatus MCP server, and what's possible with it?

The Instatus MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Instatus account. It provides structured and secure access to your status pages, components, incidents, maintenance, and service health, so your agent can monitor components, report incidents, publish updates, schedule maintenance, and review service history on your behalf.

  • Status page and service visibility: Have your agent list your status pages, review their components, and check the current health and configuration of a specific service.
  • Incident communication: Let the agent create incidents, review affected components and update history, edit incident details, and publish lifecycle updates as conditions change.
  • Maintenance planning: Direct your agent to schedule or start maintenance, inspect planned and past work, revise schedules and public messages, and post progress updates.
  • Component management: Instruct your agent to create status page components and update their health or presentation when service conditions change.
  • Operational history review: Have your agent list incidents and maintenance events to help your team understand recent disruptions, planned work, and current service status.

Way Forward

Now that Instatus is connected, extend your setup by connecting the other apps you already use every day, so your Grok bot can run true cross-app workflows end to end.

  • Connect Calendar to turn threads into scheduled meetings automatically.
  • Connect Slack or Teams to post summaries, approvals, and alerts where your team works.
  • Connect Notion, Linear, Jira, or Asana to convert requests into tickets, tasks, and docs.
  • Connect Drive, Dropbox, or OneDrive to fetch, file, and share attachments without manual steps.

Start with one workflow you do repeatedly, then keep adding apps as you find new handoffs. With everything behind a single connection, your bot can coordinate multiple tools safely and reliably in one conversation.

TOOLS

Supported Tools

Every Instatus action and event your agent gets out of the box.

Add Incident Update

Post a public lifecycle update to an Instatus incident and change affected component states.

Add Maintenance Update

Post a public progress update to an Instatus maintenance, optionally changing its lifecycle, timing, and affected component states.

Create Component

Create a component on an Instatus status page.

Create Incident

Create an incident on an Instatus status page with optional affected component states.

Create Maintenance

Schedule or start a maintenance on an Instatus status page.

Get Component

Get the current health and configuration of one component on an Instatus status page.

Get Incident

Get one Instatus incident with its affected components and update history.

Get Maintenance

Get one Instatus maintenance with its schedule, affected components, automation settings, and update history.

List Components

List components and their current health for one Instatus status page, including child components where present.

List Incidents

List incidents for an Instatus status page, optionally including or excluding lifecycle statuses.

List Maintenances

List scheduled and historical maintenances for an Instatus status page.

List Status Pages

List status pages available to the connected Instatus account so an agent can discover page IDs for component, incident, and maintenance operations.

Update Component

Change a component's health or presentation on an Instatus status page.

Update Incident

Edit an existing Instatus incident's name, timing, lifecycle status, affected components, or component states.

Update Maintenance

Fully replace an Instatus maintenance's public message, schedule, lifecycle state, affected components and states, and automation settings.

FAQ

Frequently asked questions

Start with Instatus.It takes 30 seconds.

Managed auth, hosted MCP servers, and every Instatus tool your agent needs.Free to start.

Start building