Protocol-0
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tasks | {
"list": {},
"cancel": {},
"requests": {
"tools": {
"call": {}
}
}
} |
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": true
} |
| resources | {
"subscribe": true,
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| startMonitoringA | Start continuous live polling of enterprise SaaS systems (GitHub, Jira, Datadog, Calendar) every 30 seconds. |
| stopMonitoringA | Stop continuous live polling of enterprise SaaS systems. |
| getMonitoringStatusA | Get the active status of SaaS polling, last run timestamp, and recent Gmail/Slack alerts. |
| getSecurityAuditLogsA | Fetches recent security audit logs, including IAM role modifications, Zero-Trust Gate executions, and unauthorized access attempts. |
| getEngineeringHealthA | Get the detailed engineering health report computed from weighted metrics (Deployment Success 25%, CI/CD Success 20%, Sprint Health 20%, Issue Rate 15%, Infrastructure 20%). |
| getKubernetesStateA | Fetches the current live state of the Kubernetes production clusters, identifying failing pods (CrashLoopBackOff, OOMKilled). |
| getIncidentReportA | Get the complete analysis for one incident: timeline, root cause, confidence, affected systems, business impact and recommendations. Renders the incident detail view. |
| getRecommendationsA | Get prioritized AI recommendations (high/medium/low). Optionally scoped to one incident. Exposes Approve/Reject actions. |
| list_incidentsB | List active incidents. |
| get_incidentB | Legacy alias for getIncidentReport. |
| getPagerDutyIncidentsA | Fetches the active on-call PagerDuty incidents and alerts across all engineering escalation policies. |
| getCompanyHealthA | Get the live Protocol-0 dashboard: overall system health score, per-subsystem health, open incidents, and top recommendations. |
| executiveChatA | Executive Copilot: Ask natural-language operational questions like "Why is engineering health low?", "Summarize today's risks", etc. |
| getAgentActivityB | Show the live multi-agent execution pipeline (Monitoring -> Infrastructure -> Incident Commander -> Action) and agent logs. |
| get_company_healthC | Legacy alias for getCompanyHealth. |
| get_agent_activityD | Legacy alias for getAgentActivity. |
| approveRecommendationA | Action Agent: approve and execute a recommended action through its designated MCP server. |
| rejectRecommendationB | Action Agent: reject a recommended action, marking it as rejected in the timeline. |
| triggerIncidentB | Hackathon Simulator: Trigger one of the 10 supported incident scenarios to observe how the LangGraph multi-agent pipeline reasons and mitigates in real-time. |
| simulate_disasterA | What-If Disaster Simulator: Simulate the catastrophic failure of a specific sub-system or cloud region to test auto-remediation and cascading impacts. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| digital_twin_dashboard | Get an overview of the global IT infrastructure health dashboard |
| incident_investigation | Analyze and summarize details for a specific incident |
| recommendation_review | Get details on a specific recommendation and advice on whether to approve or reject it |
| run_simulation_drill | Get guidance on triggering a simulated incident drill to test the multi-agent pipeline |
| sre_post_mortem_generator | Generates a detailed, SRE-compliant post-mortem report for a resolved incident |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| datadog-alerts | Fetch the latest critical Datadog alerts and CPU/Memory metrics |
| github-actions-failed | Fetch the latest failed GitHub Actions workflows |
| jira-sprints-active | Fetch active Jira sprints and story point burndown metrics |
| slack-ops-history | Fetch the latest incident notifications sent to the ops Slack channel |
| audit-trail | Fetch the tamper-evident, PII-redacted audit trail of all agent actions |
| Health Checks | Current health status of all registered health checks |
| Monitoring | UI component for Monitoring |
| Security Audit Logs | UI component for Security Audit Logs |
| Engineering Health | UI component for Engineering Health |
| Kubernetes State | UI component for Kubernetes State |
| Incident Detail | UI component for Incident Detail |
| Recommendation | UI component for Recommendation |
| List Incidents | UI component for List Incidents |
| Pagerduty Incidents | UI component for Pagerduty Incidents |
| System Health | UI component for System Health |
| Executive Chat | UI component for Executive Chat |
| Agent Activity | UI component for Agent Activity |
| Trigger Incident | UI component for Trigger Incident |
| Simulate Disaster | UI component for Simulate Disaster |
| Widget Examples | Provides metadata and examples for all registered UI widgets |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/paarthureddy/TheBlacklisted-NitroStack'
If you have feedback or need assistance with the MCP directory API, please join our Discord server