"DeskCrew - Workspace or Office Crew Management Platform" matching MCP connectors:
GET /v1/connectors – MCP directory API referenceMatching Connector Tools:
Is GitHub, npm, Cloudflare or your AI provider down right now? 20 status pages, one call.
Analytics for MCP servers. Find out which of your tools agents get wrong. MCPulse shows you which tools AI agents retry, which come back empty, and which they never call at all. Two lines inside your own server. It never sees your arguments or your results. getmcpulse.com
Free-trial AI fleet spend meter. Quote agent fleet spend from token usage. 100 calls or 14 days. No auth. Official MCP Registry: io.github.mtardy90-sudo/bootlace-ai-spendmap.
Fixter's MCP provides a stream-lined agentic way to onboard, setup and use the Fixter monitoring and observability platform. Check out more at https://fixter.dev/
Search + patterns, maturity assessment, context pricing, redaction checks - a practice as tools.
A managed runtime for custom API integrations. Manage lines, endpoints, keys, logs and DLQ via MCP.
Live status for 172 cloud and SaaS vendors from their official feeds. Is it you, or is it them?
Read monitors, incidents, heartbeats, on-call and status pages; acknowledge or resolve incidents.
Uptime and website monitoring for AI agents. Query monitor status, incidents, heartbeats, domain expiry, and status pages in your Vantaj Uptime workspace.
RUM platform for web performance analytics, Core Web Vitals, and third-party script monitoring.
The Google GKE MCP server is a managed Model Context Protocol server that provides AI applications with tools to manage Google Kubernetes Engine (GKE) clusters and Kubernetes resources. It exposes a structured, discoverable interface that allows AI agents to interact with GKE and Kubernetes APIs, enabling them to inspect cluster configurations, retrieve Kubernetes resource YAMLs, monitor operations like cluster upgrades, diagnose issues, and optimize costs—all without needing to parse text output or use complex kubectl commands.
Mezmo MCP is a remote Model Context Protocol (MCP) server that lets AI assistants and IDE chat agents interact with the Mezmo observability platform via the Model Context Protocol. Use it for streamlined observability, log analysis, and root-cause analysis in your favorite tools. Add Mezmo MCP and you can: 🕵️ Run advanced Root-cause analysis over recent logs 📦 List and describe Pipelines 📤 Export and filter Logs with powerful query syntax
Research honeypot. Logs connections and tool arguments; injects instructions. Read README first.
Free MCP tools: the only MCP linter, health checks, cost estimation, and trust evaluation.
Append an operations activity entry
- openstatusOAuth via extensiondev.openstatus
Manage monitors, status pages, incidents and maintenances in your openstatus workspace.
- SpikeOAuthsh.spike.mcp
Official Spike MCP server for incident management, alerting, and on-call.
- LuciqOAuthai.luciq.api
Mobile observability for AI agents. Investigate crashes, hangs, ANRs, bugs, and app performance, and triage app store reviews, directly from your IDE or terminal.
The Polar Signals MCP server enables AI assistants to connect directly with performance profiling data, allowing users to analyze application performance through natural language queries. Key capabilities include querying CPU performance and memory usage, exploring profiling metadata like profile types and labels, and providing AI-driven code optimization suggestions directly within development environments like Claude Code or Cursor.
The Buildkite MCP server exposes Buildkite product data (pipelines, builds, jobs, and test data) to AI tools, editors, and agents through the Model Context Protocol. It provides capabilities including pipeline creation and management, build monitoring with specialized tools like 'wait_for_build', efficient log querying using Apache Parquet conversion and caching, and OAuth-based authentication for both read-write and read-only access to Buildkite's REST API.
