Frequently asked questions
Can't find your question? Email us to arrange a time to discuss. We'd love to chat!
-
What is the StatusGator MCP server?
The MCP (Model Context Protocol) server is an interface that allows AI agents and LLM-based systems to interact with StatusGator using structured tools instead of raw API calls. It provides a tool for every major StatusGator operation, from monitoring and incidents to subscribers and historical data. -
What can I do with the MCP server?
You can read board and service status, create and manage monitors (website, ping, custom, and service), create and update incidents, manage status page subscribers, organize monitors into groups, and access historical uptime data—all through structured MCP tools. -
How is the MCP server different from the API?
MCP tools wrap the same API endpoints in a structured, agent-friendly format. While the API uses standard HTTP requests and JSON responses, MCP provides tool definitions that AI agents can discover and invoke directly, making integration with LLM workflows simpler. -
Who should use the MCP server?
Teams building AI-powered workflows, automation pipelines, or integrating with LLM copilots that need to read or manage status data programmatically. If you are connecting AI agents to StatusGator, MCP is the recommended approach. -
Do I need coding experience to use the MCP server?
No. MCP is designed for use with AI agents and LLM-based tools, which handle the technical details of invoking tools. Point your MCP client at the StatusGator MCP endpoint and approve the connection in your browser, or configure the client with a StatusGator API token, and the server will handle the rest.
Can't find your question? Email us to arrange a time to discuss. We'd love to chat!