DevOps
use.observer
Manages incidents, maintenance windows, and change events for status page operations.
ENDPOINT 1
https://mcp.use.observer/mcp
MCP server metadata
- Name
- observer
- Version
- 0.1.0
Known tools 27
appendIncidentMessageAppend a timeline message; type=Resolved auto-resolves the parent (requires scope: write:incidents)
Potential side effectsapplyConfigApply a config-as-code document (idempotent upsert by config_key) (requires scope: write:config)
Potential side effectscancelMaintenanceCancel a maintenance before completion (requires scope: write:maintenances)
Potential side effectscompleteMaintenanceManually transition an in-progress maintenance to completed (requires scope: write:maintenances)
Potential side effectscreateChangeEventIngest a deploy / commit / release event for status-transition correlation (requires scope: write:change_events)
Potential side effectscreateIncidentCreate incident (draft or published) (requires scope: write:incidents)
Potential side effectscreateMaintenanceSchedule a maintenance window (requires scope: write:maintenances)
Potential side effectsdraftIncidentFromMetricPre-fill a draft incident from the metric's current state (idempotent within 30 minutes) (requires scope: write:incidents)
Potential side effectsexportConfigExport the org's config as a canonical apply document (requires scope: read:config)
Inferred read-onlygetMetricHistoryAggregated metric values over a window (max 30 days) (requires scope: read:metrics)
Inferred read-onlypatchIncidentPatch incident (title, severity, affected services, visibility) (requires scope: write:incidents)
Potential side effectspatchMaintenanceEdit maintenance (only allowed before actual_start_at is set) (requires scope: write:maintenances)
Potential side effectsresolveIncidentResolve an incident with optional final message (requires scope: write:incidents)
Potential side effectssetManualMetricStatusSet status on a manually-managed metric (requires scope: write:metrics)
Potential side effectsstartMaintenanceManually transition a scheduled maintenance to in_progress (requires scope: write:maintenances)
Potential side effectsCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.observer]
url = "https://mcp.use.observer/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"observer": {
"type": "http",
"url": "https://mcp.use.observer/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: observer
Remote MCP URL: https://mcp.use.observer/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"observer": {
"url": "https://mcp.use.observer/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"observer": {
"type": "http",
"url": "https://mcp.use.observer/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "observer",
"transport": "streamable-http",
"url": "https://mcp.use.observer/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.