# How to connect Instatus to Grok Bot

```json
{
  "title": "How to connect Instatus to Grok Bot",
  "toolkit": "Instatus",
  "toolkit_slug": "instatus",
  "framework": "Grok Bot",
  "framework_slug": "grok-bot",
  "url": "https://composio.dev/toolkits/instatus/framework/grok-bot",
  "markdown_url": "https://composio.dev/toolkits/instatus/framework/grok-bot.md",
  "updated_at": "2026-11-15T06:01:18.514Z"
}
```

## 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](https://docs.composio.dev/toolkits/instatus).

## TL;DR

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.

## Connect Instatus to Grok Bot

### 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](https://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](https://x.ai/bot/plugin/32661537)
Grok Bot opens the Composio plugin, showing its connector and skills. Click Add.
### 2. Authenticate
Go to the Installed section and click the Composio entry. You'll see its connector and skills listed.
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.
### 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.

## Supported Tools

| Tool slug | Name | Description |
|---|---|---|
| `INSTATUS_ADD_INCIDENT_UPDATE` | Add Incident Update | Post a public lifecycle update to an Instatus incident and change affected component states. This can send external notifications to page and affected-component subscribers when notify is true. |
| `INSTATUS_ADD_MAINTENANCE_UPDATE` | Add Maintenance Update | Post a public progress update to an Instatus maintenance, optionally changing its lifecycle, timing, and affected component states. This can send external notifications to page and affected-component subscribers when notify is true. |
| `INSTATUS_CREATE_COMPONENT` | Create Component | Create a component on an Instatus status page. This changes the page's component configuration and can make the new component and its initial health status publicly visible. |
| `INSTATUS_CREATE_INCIDENT` | Create Incident | Create an incident on an Instatus status page with optional affected component states. The incident is published publicly by default; notify=true can send notifications to page and affected-component subscribers. |
| `INSTATUS_CREATE_MAINTENANCE` | Create Maintenance | Schedule or start a maintenance on an Instatus status page. The required notification controls are side-effecting: notify can contact subscribers immediately, while notify_start, notify_end, and notify_early schedule later subscriber notifications. |
| `INSTATUS_GET_COMPONENT` | Get Component | Get the current health and configuration of one component on an Instatus status page. |
| `INSTATUS_GET_INCIDENT` | Get Incident | Get one Instatus incident with its affected components and update history. |
| `INSTATUS_GET_MAINTENANCE` | Get Maintenance | Get one Instatus maintenance with its schedule, affected components, automation settings, and update history. |
| `INSTATUS_LIST_COMPONENTS` | List Components | List components and their current health for one Instatus status page, including child components where present. Pass the response's next_cursor back unchanged to fetch another page. |
| `INSTATUS_LIST_INCIDENTS` | List Incidents | List incidents for an Instatus status page, optionally including or excluding lifecycle statuses. Results are paginated, with up to 100 incidents per page and a cursor for retrieving the next page when more may be available. |
| `INSTATUS_LIST_MAINTENANCES` | List Maintenances | List scheduled and historical maintenances for an Instatus status page. |
| `INSTATUS_LIST_STATUS_PAGES` | 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. |
| `INSTATUS_UPDATE_COMPONENT` | Update Component | Change a component's health or presentation on an Instatus status page. |
| `INSTATUS_UPDATE_INCIDENT` | Update Incident | Edit an existing Instatus incident's name, timing, lifecycle status, affected components, or component states. Setting notify to true sends notifications to page and affected-component subscribers. |
| `INSTATUS_UPDATE_MAINTENANCE` | Update Maintenance | Fully replace an Instatus maintenance's public message, schedule, lifecycle state, affected components and states, and automation settings. Call INSTATUS_GET_MAINTENANCE first and preserve unchanged values; setting notify to true sends subscriber notifications. |

## Supported Triggers

None listed.

## Creating MCP Server - Stand-alone vs Composio SDK

Once connected, your Grok bot can access the Instatus MCP server through Composio to run the actions you authorize, using plain language in the chat.

## Complete Code

None listed.

## Conclusion

### 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.

## How to build Instatus MCP Agent with another framework

None listed.

## Related Toolkits

- [Supabase](https://composio.dev/toolkits/supabase) - Supabase is an open-source backend platform offering scalable Postgres databases, authentication, storage, and real-time APIs. It lets developers build modern apps without managing infrastructure.
- [Codeinterpreter](https://composio.dev/toolkits/codeinterpreter) - Codeinterpreter is a Python-based coding environment with built-in data analysis and visualization. It lets you instantly run scripts, plot results, and prototype solutions inside supported platforms.
- [GitHub](https://composio.dev/toolkits/github) - GitHub is a code hosting platform for version control and collaborative software development. It streamlines project management, code review, and team workflows in one place.
- [1password](https://composio.dev/toolkits/_1password) - 1Password is a password manager and digital vault for storing logins, secrets, notes, and secure documents. It helps individuals and teams protect credentials, share access safely, and reduce password risk.
- [Ably](https://composio.dev/toolkits/ably) - Ably is a real-time messaging platform for live chat and data sync in modern apps. It offers global scale and rock-solid reliability for seamless, instant experiences.
- [Abuselpdb](https://composio.dev/toolkits/abuselpdb) - Abuselpdb is a central database for reporting and checking IPs linked to malicious online activity. Use it to quickly identify and report suspicious or abusive IP addresses.
- [Alchemy](https://composio.dev/toolkits/alchemy) - Alchemy is a blockchain development platform offering APIs and tools for Ethereum apps. It simplifies building and scaling Web3 projects with robust infrastructure.
- [Algolia](https://composio.dev/toolkits/algolia) - Algolia is a hosted search API that powers lightning-fast, relevant search experiences for web and mobile apps. It helps developers deliver instant, typo-tolerant, and scalable search without complex infrastructure.
- [Anakin](https://composio.dev/toolkits/anakin_io) - Anakin is a web automation platform offering scraping, crawling, search, and browser automation. Use it to extract structured data, automate site tasks, and monitor web changes reliably.
- [Anchor browser](https://composio.dev/toolkits/anchor_browser) - Anchor browser is a developer platform for AI-powered web automation. It transforms complex browser actions into easy API endpoints for streamlined web interaction.
- [AnyAPI](https://composio.dev/toolkits/anyapi) - AnyAPI is a marketplace of utility APIs for validation, currency conversion, holidays, documents, and web data. It brings common application workflows together through one practical API platform.
- [Apiflash](https://composio.dev/toolkits/apiflash) - Apiflash is a website screenshot API for programmatically capturing web pages. It delivers high-quality screenshots on demand for automation, monitoring, or reporting.
- [Apiverve](https://composio.dev/toolkits/apiverve) - Apiverve delivers a suite of powerful APIs that simplify integration for developers. It's designed for reliability and scalability so you can build faster, smarter applications without the integration headache.
- [Appcircle](https://composio.dev/toolkits/appcircle) - Appcircle is an enterprise-grade mobile CI/CD platform for building, testing, and publishing mobile apps. It streamlines mobile DevOps so teams ship faster and with more confidence.
- [Appdrag](https://composio.dev/toolkits/appdrag) - Appdrag is a cloud platform for building websites, APIs, and databases with drag-and-drop tools and code editing. It accelerates development and iteration by combining hosting, database management, and low-code features in one place.
- [Appveyor](https://composio.dev/toolkits/appveyor) - AppVeyor is a cloud-based continuous integration service for building, testing, and deploying applications. It helps developers automate and streamline their software delivery pipelines.
- [Authyo](https://composio.dev/toolkits/authyo) - Authyo is a REST API service for passwordless authentication, OTP verification, session management, and transactional notifications. Use it to add secure login flows and user verification without building auth infrastructure from scratch.
- [AWS Marketplace MCP](https://composio.dev/toolkits/aws_marketplace_mcp) - AWS Marketplace MCP provides MCP access to AWS Marketplace's cloud software, data, and services catalog. Use it to discover, compare, and evaluate 30K+ AWS Marketplace listings faster.
- [Azure Monitor Activity Log](https://composio.dev/toolkits/azure_monitor_activity_log) - Azure Monitor Activity Log is Azure's service that records management and control-plane events for a subscription. Use it to audit changes, troubleshoot issues, and track resource operations across your Azure resources.
- [Backendless](https://composio.dev/toolkits/backendless) - Backendless is a backend-as-a-service platform for mobile and web apps, offering database, file storage, user authentication, and APIs. It helps developers ship scalable applications faster without managing server infrastructure.

## Frequently Asked Questions

### What are the differences in Tool Router MCP and Instatus MCP?

With a standalone Instatus MCP server, the agents and LLMs can only access a fixed set of Instatus tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Instatus and many other apps based on the task at hand, all through a single MCP endpoint.

### Can I use Tool Router MCP with Grok Bot?

Yes, you can. Grok Bot fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right Instatus tools.

### Can I manage the permissions and scopes for Instatus while using Tool Router?

Yes, absolutely. You can configure which Instatus scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do.

### How safe is my data with Composio Tool Router?

All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your Instatus data and credentials are handled as safely as possible.

---
[See all toolkits](https://composio.dev/toolkits) · [Composio docs](https://docs.composio.dev/llms.txt)
