Analyze OpenObserve logs and traces with an AI MCP observability toolkit
Ready for 3.0What this workflow does
This AI workflow has 11 nodes and runs when an MCP client calls one of its tools. Along the way it connects HTTP Request. It also calls host.docker.internal:5080 over HTTP.
How it runs
Trigger: When an MCP client calls one of its tools.
No action steps found in the workflow JSON.
Services it uses
HTTP calls to: host.docker.internal:5080
Before you upgrade to n8n 3.0
Nothing in this workflow is removed in n8n 3.0, so it should import and run after the upgrade.
Nodes used (2)
- Http Request Tool
n8n-nodes-base.httpRequestTool - MCP Server Trigger
@n8n/n8n-nodes-langchain.mcpTrigger
From the author
🔎 AI Observability Toolkit for OpenObserve MCP Server (Logs + Traces) An MCP server that exposes 10 specialized AI tools for deep observability over your OpenObserve logs and traces. Designed for AI agents to perform: - Schema inspection - Error…