How to Use the Azure Log Analytics Workspace MCP in CrewAI

Equip your CrewAI agents with vision into your Azure logs. Build autonomous teams that monitor, analyze, and respond to system events.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Azure Log Analytics Workspace MCP to CrewAI

Create your Vinkius account to connect Azure Log Analytics Workspace to CrewAI and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup Azure Log Analytics Workspace with CrewAI

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Designate a Monitor Agent

Give one agent in your crew a single job: watch the logs. This agent's sole purpose is to use the `query_logs` tool to periodically check for specific events or error patterns in your Azure Log Analytics Workspace. By specializing this agent, you create a more organized and effective crew. The Monitor Agent becomes the trigger for your entire automated incident response process, kicking off tasks for other agents when it finds something.

Collaborative Incident Response

This is where a crew shines. Your Monitor Agent finds an error using `query_logs`. It then passes the raw log data to an Analyst Agent, which is trained to determine root causes. The Analyst digests the information and tasks a third agent to take action. This multi-agent approach lets you build sophisticated, autonomous operations. Each agent has a clear role, from observation to analysis to action. It's a huge step up from single-agent scripts.

Role-Based Access for Your CrewAI MCP Server

Not every agent needs access to everything. CrewAI's `tool_filter` lets you expose this MCP Server and its `query_logs` tool only to the agents that need it, like your designated "Monitor" or "Auditor" agent. This enforces the principle of least privilege within your autonomous team. The agent responsible for fixing a problem doesn't need to query the logs, and the agent querying the logs doesn't need permissions to fix things. It's a cleaner, more secure design.

Setup guide

Set up Azure Log Analytics Workspace MCP in CrewAI

Prerequisites

Python 3.10+ installed
crewai package (pip install crewai)
Active Vinkius subscription with a valid endpoint token

1

Install CrewAI
Run pip install crewai to install the framework. MCP support is built-in via the mcps parameter.
2

Add the MCP URL to your agent
Pass your Vinkius endpoint directly to the mcps list. Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com. CrewAI handles tool discovery and caching automatically.
3

Kick off your crew
Create a Crew with your agent and tasks. Call crew.kickoff() — the agent will automatically invoke Azure Log Analytics Workspace tools as needed.

crew.py

from crewai import Agent, Task, Crew

agent = Agent(
    role="Azure Log Analytics Workspace Analyst",
    goal="Access and analyze Azure Log Analytics Workspace data via MCP.",
    backstory="Expert analyst with direct Azure Log Analytics Workspace access.",
    mcps=[
        "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    ],
)

task = Task(
    description="List recent Azure Log Analytics Workspace transactions",
    agent=agent,
    expected_output="A summary of recent activity",
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)

Get your connection token →

Prerequisites

Python 3.10+ installed
crewai + crewai-tools packages
Active Vinkius subscription with a valid endpoint token

1

Install dependencies
Run pip install crewai crewai-tools. The MCPServerAdapter handles lifecycle management and tool conversion.
2

Connect with MCPServerAdapter
Use MCPServerAdapter as a context manager with SseServerParameters pointing to your Vinkius endpoint. The adapter automatically manages connection lifecycle.
3

Assign tools and run
Pass the returned mcp_tools to your agent's tools parameter. The adapter converts MCP tools to native BaseTool objects compatible with all CrewAI agents.

crew.py

from crewai import Agent, Task, Crew
from crewai_tools import MCPServerAdapter
from mcp import SseServerParameters

server_params = SseServerParameters(
    url="https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
)

with MCPServerAdapter(server_params) as mcp_tools:
    agent = Agent(
        role="Azure Log Analytics Workspace Analyst",
        goal="Access and analyze Azure Log Analytics Workspace data via MCP.",
        backstory="Expert analyst with direct Azure Log Analytics Workspace access.",
        tools=mcp_tools,
    )

    task = Task(
        description="List recent Azure Log Analytics Workspace transactions",
        agent=agent,
        expected_output="A summary of recent activity",
    )

    crew = Crew(agents=[agent], tasks=[task])
    result = crew.kickoff()
    print(result)

Get your connection token →

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Azure Log Analytics Workspace. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect Azure Log Analytics Workspace now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about Azure Log Analytics Workspace MCP in CrewAI

Agents in a crew share context. The first agent executes the `query_logs` tool as part of its task. Its output, the log data, is automatically available in the shared context for the next agent in the sequence to use for its own task.

Yes. You can set up a sequential or hierarchical crew where a Monitor Agent runs in a loop. Its task would be to call `query_logs` on a timer and pass any findings to the rest of the crew for processing.

When you define your agents, you assign them specific tools. Only give the `query_logs` tool from this MCP server to the agent that should have monitoring capabilities. The other agents simply won't have it in their toolset.

No, it's straightforward. For a simple setup, you can pass the Vinkius URL directly into the `mcps` list when creating your Agent. CrewAI handles the connection and tool discovery.

Only if you design the workflow that way. The MCP server streams log data only to the specific agent that calls the `query_logs` tool. The data flow is explicit; it's passed from one agent to the next as task output, not broadcast to the entire crew. You control who sees what.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript