4,000+ servers built on vurb.ts
Vinkius

Statuspage (Atlassian) MCP Server for VS Code CopilotGive VS Code Copilot instant access to 16 tools to Create Page Access User, Delete Page Access User, Delete Page Access User Components, and more

MCP Inspector GDPR Free for Subscribers

GitHub Copilot in VS Code is the most widely adopted AI coding assistant, embedded directly into the world's most popular code editor. With MCP support in Agent mode, Copilot can access external data and APIs to generate context-aware code grounded in real-time information.

Ask AI about this MCP Server for VS Code Copilot

The Statuspage (Atlassian) MCP Server for VS Code Copilot is a standout in the Industry Titans category — giving your AI agent 16 tools to work with, ready to go from day one.

Built for AI Agents by Vinkius

Vinkius delivers Streamable HTTP and SSE to any MCP client

ClaudeClaude
ChatGPTChatGPT
CursorCursor
GeminiGemini
WindsurfWindsurf
VS CodeVS Code
JetBrainsJetBrains
VercelVercel
+ other MCP clients
Classic Setup·json
{
  "mcpServers": {
    "statuspage-atlassian": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}
RecommendedModern Approach — Zero Configuration

Vinkius Desktop App

The modern way to manage MCP Servers — no config files, no terminal commands. Install Statuspage (Atlassian) and 4,000+ MCP Servers from a single visual interface.

Vinkius Desktop InterfaceVinkius Desktop InterfaceVinkius Desktop InterfaceVinkius Desktop Interface
Download Free Open SourceNo signup required
Statuspage (Atlassian)
Fully ManagedVinkius Servers
60%Token savings
High SecurityEnterprise-grade
IAMAccess control
EU AI ActCompliant
DLPData protection
V8 IsolateSandboxed
Ed25519Audit chain
<40msKill switch
Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About Statuspage (Atlassian) MCP Server

Connect your Statuspage (Atlassian) account to any AI agent to monitor and manage your incident communication infrastructure through natural conversation.

GitHub Copilot Agent mode brings Statuspage (Atlassian) data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 16 tools. Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.

What you can do

  • Page Management — List all status pages and fetch detailed configurations for specific IDs using list_pages and get_page.
  • Configuration Updates — Update page names, domains, and branding settings instantly with the update_page tool.
  • User Permissions — Query and update user roles and permissions within your organization using get_user_permissions and update_user_permissions.
  • Embed Widgets — Manage status embed configurations to control how status is displayed on your site via get_status_embed_config.
  • Access Control — Manage audience-specific users for private status pages, including creation and updates with list_page_access_users and create_page_access_user.

The Statuspage (Atlassian) MCP Server exposes 16 tools through the Vinkius. Connect it to VS Code Copilot in under two minutes — credentials fully managed, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

All 16 Statuspage (Atlassian) tools available for VS Code Copilot

When VS Code Copilot connects to Statuspage (Atlassian) through Vinkius, your AI agent gets direct access to every tool listed below — spanning incident-management, status-page, atlassian, and more. Every call runs in a secure, isolated environment with full audit visibility. Beyond a simple connection, you get real-time monitoring of agent activity, enterprise governance, and optimized token usage.

create

Create page access user on Statuspage (Atlassian)

Add a page access user

delete

Delete page access user on Statuspage (Atlassian)

Delete page access user

delete

Delete page access user components on Statuspage (Atlassian)

Remove components for page access user

delete

Delete page access user metrics on Statuspage (Atlassian)

Delete metrics for page access user

get

Get page on Statuspage (Atlassian)

Get a specific page

get

Get page access user components on Statuspage (Atlassian)

Get components for page access user

get

Get status embed config on Statuspage (Atlassian)

Get status embed config settings

get

Get user permissions on Statuspage (Atlassian)

Get a user's permissions

list

List page access users on Statuspage (Atlassian)

Get a list of page access users

list

List pages on Statuspage (Atlassian)

Get a list of pages

update

Update page on Statuspage (Atlassian)

). Update a page

update

Update page access user on Statuspage (Atlassian)

Update page access user

update

Update page access user components on Statuspage (Atlassian)

Add/Replace components for page access user

update

Update page access user metrics on Statuspage (Atlassian)

Add/Replace metrics for page access user

update

Update status embed config on Statuspage (Atlassian)

Update status embed config settings

update

Update user permissions on Statuspage (Atlassian)

g., page_configuration, incident_manager, maintenance_manager). Update a user's role permissions

Connect Statuspage (Atlassian) to VS Code Copilot via MCP

Follow these steps to wire Statuspage (Atlassian) into VS Code Copilot. The entire setup takes under two minutes — your credentials stay safe behind Vinkius.

01

Create MCP config

Create a .vscode/mcp.json file in your project root
02

Add the server config

Paste the JSON configuration above
03

Enable Agent mode

Open GitHub Copilot Chat and switch to Agent mode using the dropdown
04

Start using Statuspage (Atlassian)

Ask Copilot: "Using Statuspage (Atlassian), help me...". 16 tools available

Why Use VS Code Copilot with the Statuspage (Atlassian) MCP Server

GitHub Copilot for Visual Studio Code provides unique advantages when paired with Statuspage (Atlassian) through the Model Context Protocol.

01

VS Code is used by over 70% of developers. adding MCP tools to Copilot means your team can leverage external data without leaving their primary editor

02

Project-scoped MCP configs (`.vscode/mcp.json`) let you commit server configurations to your repository, ensuring the entire team shares the same tool access

03

Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop

04

GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services

Statuspage (Atlassian) + VS Code Copilot Use Cases

Practical scenarios where VS Code Copilot combined with the Statuspage (Atlassian) MCP Server delivers measurable value.

01

Live API integration: Copilot can query an MCP server, inspect the response schema, and generate typed API client code in the same step

02

DevSecOps workflows: security teams can give developers access to domain intelligence tools directly in their editor for real-time vulnerability assessment during code review

03

Data pipeline development: Copilot fetches sample data via MCP and generates transformation scripts, validators, and test fixtures from actual API responses

04

Documentation generation: Copilot queries available tools and auto-generates README sections, API reference docs, and usage examples

Example Prompts for Statuspage (Atlassian) in VS Code Copilot

Ready-to-use prompts you can give your VS Code Copilot agent to start working with Statuspage (Atlassian) immediately.

01

"List all my Statuspage pages."

02

"Show me the details for page ID abc123."

03

"Update the name of page abc123 to 'Global Operations Status'."

Troubleshooting Statuspage (Atlassian) MCP Server with VS Code Copilot

Common issues when connecting Statuspage (Atlassian) to VS Code Copilot through Vinkius, and how to resolve them.

01

MCP tools not available

Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.

Statuspage (Atlassian) + VS Code Copilot FAQ

Common questions about integrating Statuspage (Atlassian) MCP Server with VS Code Copilot.

01

Which VS Code version supports MCP?

MCP support requires VS Code 1.99 or later with the GitHub Copilot extension. Ensure both are updated to the latest version. Older versions of Copilot may not expose the Agent mode toggle.
02

How do I switch to Agent mode?

Open the Copilot Chat panel and look for two mode options: "Ask" and "Agent". Click "Agent" to enable autonomous tool calling. In Ask mode, Copilot provides conversational answers but cannot invoke MCP tools.
03

Can I restrict which MCP tools Copilot can access?

Yes. VS Code shows a tool consent dialog before any MCP tool is invoked for the first time. You can also configure tool access policies at the organization level through GitHub Copilot settings.
04

Does MCP work in VS Code Remote or Codespaces?

Yes. MCP servers configured via .vscode/mcp.json work in Remote SSH, WSL, and GitHub Codespaces environments. The MCP connection is established from the remote host, so ensure the server URL is accessible from that environment.

Explore More MCP Servers

View all →