Bring Incident Management
to VS Code Copilot
Learn how to connect Statuspage (Atlassian) to VS Code Copilot and start using 16 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
GDPR Free for SubscribersCompatible with every major AI agent and IDE
Gemini
What is the Statuspage (Atlassian) MCP Server?
Connect your Statuspage (Atlassian) account to any AI agent to monitor and manage your incident communication infrastructure through natural conversation.
What you can do
- Page Management — List all status pages and fetch detailed configurations for specific IDs using
list_pagesandget_page. - Configuration Updates — Update page names, domains, and branding settings instantly with the
update_pagetool. - User Permissions — Query and update user roles and permissions within your organization using
get_user_permissionsandupdate_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_usersandcreate_page_access_user.
How it works
- Subscribe to this server
- Enter your Statuspage API Key
- Start managing your status infrastructure from Claude, Cursor, or any MCP-compatible client
Who is this for?
- DevOps & SREs — quickly check and update status page configurations during incident response without leaving the terminal.
- Support Teams — manage private page access for specific customers directly through the AI assistant.
- Product Owners — ensure branding and domains are correctly configured across all status environments.
Built-in capabilities (16)
Add a page access user
Delete page access user
Remove components for page access user
Delete metrics for page access user
Get a specific page
Get components for page access user
Get status embed config settings
Get a user's permissions
Get a list of page access users
Get a list of pages
). Update a page
Update page access user
Add/Replace components for page access user
Add/Replace metrics for page access user
Update status embed config settings
g., page_configuration, incident_manager, maintenance_manager). Update a user's role permissions
Why VS Code Copilot?
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.
- —
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
- —
Project-scoped MCP configs (
.vscode/mcp.json) let you commit server configurations to your repository, ensuring the entire team shares the same tool access - —
Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop
- —
GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services
Statuspage (Atlassian) in VS Code Copilot
Statuspage (Atlassian) and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect Statuspage (Atlassian) to VS Code Copilot through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 4,000+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for Statuspage (Atlassian) in VS Code Copilot
The Statuspage (Atlassian) 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. All 16 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in VS Code Copilot only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.
* 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
How Vinkius secures
Statuspage (Atlassian) for VS Code Copilot
Every tool call from VS Code Copilot to the Statuspage (Atlassian) MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
How can I see all the status pages I have access to?
You can use the list_pages tool. It will return a list of all pages associated with your API key, including their IDs and basic settings.
Can I update the name or domain of a status page using the AI?
Yes! Use the update_page tool. You just need to provide the page_id and the new name, domain, or subdomain you wish to set.
How do I manage users who have access to my private status pages?
You can use list_page_access_users to see current users and create_page_access_user to add new ones to a specific page.
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.
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.
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.
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.
MCP tools not available
Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.
Explore More MCP Servers
View all →
String Operations Engine
3 toolsEquip your AI with deterministic text manipulation. Instantly format casings (camelCase, PascalCase, slugify), truncate safely, and count exact characters local.
JotForm
10 toolsManage forms, submissions, and reports via JotForm API.
AEMO Australian Energy
12 toolsAccess Australian electricity market data — spot prices, demand, generation by fuel type, emissions, and renewable energy proportions via OpenElectricity API.
Azure AI Search
6 toolsExecute RAG queries against Azure AI Search natively — search vectors, full-text documents, and audit cloud indexes directly from your AI agent.