log-extractor-mcp-server
Provides integration with Render's Logs API to search live logs from the order-orchestration-simulator-py service, enabling retrieval of order failure diagnostics and read-only operational insights.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@log-extractor-mcp-serverPull order failure logs from the last 24 hours"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
log-extractor-mcp-server
MCP server exposing read-only Order Orchestrator diagnostic tools, plus one tool backed by real telemetry: search_order_failure_logs, which queries order-orchestration-simulator-py's live logs on Render via Render's Logs API. The other 6 tools are mock-data-backed (see mcp_server/mock_data.py).
Running locally over stdio
pip install -r requirements.txt
python -m mcp_server.serverRelated MCP server: OpenSearch Logs MCP Server
Running over HTTP (cloud deploy)
mcp_server/http_server.py exposes the same server instance over streamable-HTTP transport at /mcp, so a remote client can reach it at https://<deployed-host>/mcp.
cp .env.example .env # fill in MCP_API_KEY + RENDER_* vars
python -m mcp_server.http_serverEnv vars (see .env.example):
HOST(default0.0.0.0),PORT(default8000, most cloud platforms inject this automatically)MCP_API_KEY— optional; if set, every request must sendAuthorization: Bearer <key>. Leave blank for local testing, set it before deploying anywhere internet-reachable.RENDER_API_KEY,RENDER_OWNER_ID,RENDER_SERVICE_ID— required forsearch_order_failure_logsto reach Render's Logs API for order-orchestration-simulator-py. If unset, that tool returns a clean "could not reach the telemetry backend" message; the other 6 tools are unaffected.
Deploying to Render
This repo includes a render.yaml Blueprint. In the Render dashboard: New → Blueprint, point it at this repo, and it will pick up the Docker build automatically. Set MCP_API_KEY, RENDER_API_KEY, RENDER_OWNER_ID, and RENDER_SERVICE_ID as env vars on the service (marked sync: false in the blueprint so Render prompts for them rather than storing them in the file).
Or manually:
docker build -t log-extractor-mcp-server .
docker run -p 8000:8000 -e MCP_API_KEY=<your-key> log-extractor-mcp-serverThis server cannot be deployed
Maintenance
Related MCP Connectors
Read-only access to Auralogs production logs: search logs, inspect errors, review AI analyses.
Read-only ArcadeOps discovery for developer docs, OAuth, OpenAPI and synthetic sandbox.
Query Churn Solution cancellation-flow metrics, revenue, and feedback analytics (read-only).
- OpsLevelOAuthcom.opslevel
Query your OpsLevel internal developer portal: catalog, maturity data, and tech docs.
Related MCP Servers
- AlicenseBqualityDmaintenanceEnables querying Azure Application Insights logs by order number through natural language. Provides secure access to Azure Monitor logs with comprehensive error handling and rate limiting.11MIT
- FlicenseAqualityDmaintenanceEnables querying OpenTelemetry logs stored in OpenSearch across development and production environments. Provides tools for searching logs by various criteria including free-text Lucene queries, trace IDs, service names, error levels, and specific fields.8-
- AlicenseNot gradedqualityBmaintenanceRead-only health and storage diagnostics for an enrolled CMDOP machine fleet.Apache 2.0
- FlicenseNot gradedqualityCmaintenanceA safe, read-only MCP server that gives Codex structured access to engineering operations evidence, with validated queries, secret redaction, and audit logging. Provides a search_logs tool for filtering logs by service, environment, severity, and time range.-