# Statuspage (Atlassian) MCP

> Statuspage (Atlassian) connects your AI agent directly to your status page infrastructure. Manage all corporate announcements, user roles, and branding from a simple chat interface. You can list pages, update domains, control private access for specific clients, and handle permissions—all without logging into the Statuspage dashboard.

## Overview
- **Category:** industry-titans
- **Price:** Free
- **Tags:** incident-management, status-page, atlassian, uptime-monitoring, it-operations

## Description

When an incident hits, you don't want to jump between dashboards or remember complex API calls just to check who has access or what the page domain is. This MCP lets your AI agent monitor and manage your entire incident communication stack through natural conversation. You can list all status pages and pull detailed configurations for specific IDs using simple commands. Need to update a page name, change branding settings, or modify the primary domain? That's handled instantly. Furthermore, if you have private pages for select clients, you can query who has access or create new user accounts with granular controls over components and metrics. This capability is crucial because it lets your agent handle complex tasks like managing user roles and updating permissions across an entire organization. Vinkius brings all these tools together so that regardless of which AI client you use, the functionality stays in one place.

## Tools

### create_page_access_user
Adds a new user account to manage access on private status pages.

### delete_page_access_user_components
Removes specific components associated with a page access user.

### delete_page_access_user_metrics
Deletes performance metrics linked to a page access user account.

### delete_page_access_user
Completely removes an existing page access user from the system.

### get_page_access_user_components
Retrieves a list of components currently assigned to a specific page access user.

### get_page
Fetches all the detailed configuration settings for a single, specified status page ID.

### get_status_embed_config
Gets the current settings used to embed status updates on external websites.

### get_user_permissions
Checks and reports what level of access a given user account possesses within Statuspage.

### list_page_access_users
Retrieves a comprehensive list of all page access users currently set up on the system.

### list_pages
Provides a simple list containing the names and IDs of every status page you own.

### update_page_access_user_components
Adds or replaces component settings for an existing page access user account.

### update_page_access_user_metrics
Adds or replaces metrics linked to a specific page access user's profile.

### update_page_access_user
Modifies the core details and settings for an existing page access user.

### update_page
Updates fundamental properties of a status page, such as its name or associated domain.

### update_status_embed_config
Changes the configuration settings for how your status pages are embedded onto external websites.

### update_user_permissions
Modifies a user's role and permissions across multiple parts of the Statuspage platform.

## Prompt Examples

**Prompt:** 
```
List all my Statuspage pages.
```

**Response:** 
```
I've retrieved your pages. You have access to: 'Main Production' (ID: abc123) and 'Internal Services' (ID: def456).
```

**Prompt:** 
```
Show me the details for page ID abc123.
```

**Response:** 
```
Fetching details for page abc123... The page is named 'Main Production', hosted at status.example.com, and currently has branding enabled.
```

**Prompt:** 
```
Update the name of page abc123 to 'Global Operations Status'.
```

**Response:** 
```
I have successfully updated the name of page abc123 to 'Global Operations Status'.
```

## Capabilities

### List and view page details
Retrieves a list of all status pages and fetches full configuration details for any specific page ID.

### Modify page settings and branding
Allows you to update core elements like the page name, domain, or overall branding across your entire Statuspage setup.

### Manage user permissions and roles
Checks existing user access levels or updates specific roles for users within your organization's status infrastructure.

### Control private page access
Manages audience-specific users, including creating new accounts or deleting access rights for private client pages.

### Update embedded widgets and configurations
Adjusts how status information appears on external sites by managing embed widget settings.

## Use Cases

### Restricting client visibility after a sale
A support manager needs to revoke access for an old customer who shouldn't see the status page anymore. Instead of finding and deleting their profile, they simply tell their agent: 'Delete page access user XYZ.' The agent executes `delete_page_access_user`.

### Changing a domain during a merger
The DevOps team needs to shift the main status page's hosted domain immediately. They instruct their agent to run 'Update page abc123 with new domain.' The agent executes `update_page` and confirms the change.

### Auditing user access before a public release
A Product Owner needs to audit who has permission to edit sensitive pages. They ask their agent to run 'List all page access users' and then use `get_user_permissions` on key accounts.

### Adding new metrics for a premium client
The technical team discovers a new metric needs tracking for a specific private page. They use the agent to run 'Update page access user metrics' to add the required data point without touching the main UI.

## Benefits

- Stop hunting through multiple dashboards. You can list all pages or get detailed configurations using `list_pages` or `get_page`, getting the data you need in one chat exchange.
- Need to onboard a new client? Use `create_page_access_user` and then refine their access with `update_page_access_user`. It handles complex user management without UI clicks.
- Change branding or domains fast. Updating core settings like page names or domains using `update_page` means you can respond to an incident change immediately.
- Control privacy tightly. You don't have to manually verify permissions; use `get_user_permissions` and `list_page_access_users` to see who has access right now.
- Keep your site consistent. If branding changes, you update the embed settings with `update_status_embed_config`, ensuring all external widgets look right.

## How It Works

The bottom line is you manage complex infrastructure changes using plain English prompts instead of logging into multiple dedicated UIs.

1. First, subscribe to this MCP and provide your Statuspage API Key.
2. Next, simply instruct your AI client. For example: 'List all my production pages' or 'Update page abc123 domain'.
3. The agent sends the request to the platform and reports back the status of the action—success, failure, or data retrieved.

## Frequently Asked Questions

**How do I list all my pages using Statuspage (Atlassian) MCP?**
You use the `list_pages` tool. This simply returns a list of names and IDs for every page linked to your account, letting you know what resources you can work with.

**Can I update user roles using Statuspage (Atlassian) MCP?**
Yes, you use the `update_user_permissions` tool. This allows you to modify a user's specific roles and permissions across the platform in natural language.

**What if I need to change the domain name of my status page?**
You must use the `update_page` tool. This function lets you update fundamental properties, including changing the page's associated domain or branding settings.

**How do I delete a client’s access account with Statuspage (Atlassian) MCP?**
You use `delete_page_access_user`. If that user has components or metrics attached, you should first run the respective delete tools to clean up fully.

**Does Statuspage (Atlassian) MCP handle embed widget settings?**
Yes. You use `get_status_embed_config` and `update_status_embed_config` to check or modify how your status is displayed on external websites.