home / mcp / status mcp server
Provides MCP-based access to status page data from awesome-status for quick service discovery and details.
Configuration
View docs{
"mcpServers": {
"amkisko-status_mcp.rb": {
"command": "gem",
"args": [
"exec",
"status_mcp"
],
"env": {
"RUBY_VERSION": "3.4.7"
}
}
}
}You run a local MCP server built as a Ruby gem to expose status page information from awesome-status to MCP-enabled clients. It operates offline once installed and lets you search for services and retrieve detailed status links without querying remote endpoints each time.
Set up your MCP client to talk to the local status_mcp server. You will load a local MCP configuration that points to the stdio interface of the gem, which is designed to work with MCP-enabled tools such as your editor or IDE. The server provides three tools you can call from your MCP client: search_services, to find services by name; get_service_details, to get detailed status links for a specific service; and list_services, to list available services (limited to the first 50 items if there are many). Use these tools to discover and inspect status pages relevant to your needs.
Prerequisites: you need Ruby 3.1 or higher installed on your system. You also need a working MCP client configuration that can load stdio-based MCP servers.
Install the status_mcp gem to provide the MCP server functionality.
gem install status_mcpConfigure your MCP client to connect to the local stdio MCP server. Use the following command configuration to run the server via the gem, which uses the local Ruby version you specify.
{
"mcpServers": {
"status": {
"type": "stdio",
"name": "status",
"command": "gem",
"args": ["exec", "status_mcp"],
"env": {
"RUBY_VERSION": "3.4.7"
}
}
}
}All data is bundled with the gem and does not require external authentication. The server runs locally and can operate offline after installation, making it a convenient option for developer environments or restricted networks.
If you want to run the MCP server directly from source during development, you can use Bundler to execute the server in the same Ruby environment you use for your project.
Search for services by name to quickly locate relevant status entries.
Retrieve detailed status links and information for a specific service.
List all available services, with an optional limit parameter to cap results.