Azure Log Analytics Workspace Connector for AI agents.
1 live capability
Query specific cloud logs for faster production troubleshooting.
Waiting for input…
Why people use Azure Log Analytics Workspace
Azure Log Analytics Workspace Cloud Monitoring
This Connector lets your agent do that work for you. You just tell the agent what's wrong, and it runs the KQL queries directly against your logs. You get the answer in seconds instead of minutes of manual clicking.
What Vinkius changes
You get secure, scoped access to specific cloud logs without compromising your entire Azure environment.
Use it from Claude, ChatGPT, Cursor or another AI client you already have.
One account · 6,100+ Connectors
- Real-world use case 01
Identify why the app crashed
An engineer asks the agent to find 500 errors in the last 30 minutes.
- Real-world use case 02
Analyze traffic spikes
An SRE notices a spike in traffic.
- Real-world use case 03
Filter for specific users
A support lead asks for all logs related to a specific user ID from the last 24 hours.
Complete set · 1capability
The complete Azure Log Analytics Workspace capability set.
These are the exact actions your AI can choose when you ask it to work with Azure Log Analytics Workspace.
01
1 capability in this set.
Part of 1 available through Azure Log Analytics Workspace.
- 01 Capability
Query logs
Run a KQL query against your authorized table. It handles the table naming automatically so you can just provide the query logic.
Set up in minutes
One URL. Then ask Azure Log Analytics Workspace to work.
Claude and ChatGPT only need the Connector URL. Copy it once, add it in settings, and use Azure Log Analytics Workspace from the conversation.
Choose your client
Live previewAdvanced clients IDE · CLI
Claude · Web + desktop
Connector URL · ready to paste
Streamable HTTPhttps://edge.vinkius.com/vk_preview_h8mzxcilFYlijQMfr5u3GIGk82xs7W4r1G5Um6EK/mcp - Step 01
Open Connectors
In Claude Web or Claude Desktop, open Settings and choose Connectors.
- Step 02
Add the URL
Choose Add custom connector, name it Azure Log Analytics Workspace, and paste the URL above.
- Step 03
Turn it on in chat
Select +, open Connectors, and enable Azure Log Analytics Workspace for the conversation.
ChatGPT · Web + desktop
Connector URL · ready to paste
Streamable HTTPhttps://edge.vinkius.com/vk_preview_h8mzxcilFYlijQMfr5u3GIGk82xs7W4r1G5Um6EK/mcp - Step 01
Open MCP settings
On desktop, open Settings and MCP servers. On web, open your workspace app or connector settings.
- Step 02
Add the URL
Choose Add server with Streamable HTTP, or create a custom MCP app, then paste the Azure Log Analytics Workspace URL.
- Step 03
Save and start
Save the connection and enable Azure Log Analytics Workspace in your conversation. Desktop may ask you to restart once.
Cursor · IDE configuration
Advanced setup
{
"mcpServers": {
"azure-log-analytics-workspace": {
"url": "https://edge.vinkius.com/vk_preview_h8mzxcilFYlijQMfr5u3GIGk82xs7W4r1G5Um6EK/mcp"
}
}
}- Step 01
Open MCP Settings
Press Cmd+Shift+P (macOS) or Ctrl+Shift+P (Windows/Linux) → search "MCP Settings"
- Step 02
Add the server config
Paste the JSON configuration above into the mcp.json file that opens
- Step 03
Save the file
Cursor will automatically detect the new Connector
- Step 04
Start using Azure Log Analytics Workspace
Open Agent mode in chat and ask: "Using Azure Log Analytics Workspace, help me...". 1 tools available
VS Code Copilot · IDE configuration
Advanced setup
{
"mcpServers": {
"azure-log-analytics-workspace": {
"url": "https://edge.vinkius.com/vk_preview_h8mzxcilFYlijQMfr5u3GIGk82xs7W4r1G5Um6EK/mcp"
}
}
}- Step 01
Create MCP config
Create a .vscode/mcp.json file in your project root
- Step 02
Add the server config
Paste the JSON configuration above
- Step 03
Enable Agent mode
Open GitHub Copilot Chat and switch to Agent mode using the dropdown
- Step 04
Start using Azure Log Analytics Workspace
Ask Copilot: "Using Azure Log Analytics Workspace, help me...". 1 tools available
Windsurf · IDE configuration
Advanced setup
{
"mcpServers": {
"azure-log-analytics-workspace": {
"url": "https://edge.vinkius.com/vk_preview_h8mzxcilFYlijQMfr5u3GIGk82xs7W4r1G5Um6EK/mcp"
}
}
}- Step 01
Open MCP Settings
Go to Settings → MCP Configuration or press Cmd+Shift+P and search "MCP"
- Step 02
Add the server
Paste the JSON configuration above into mcp_config.json
- Step 03
Save and reload
Windsurf will detect the new server automatically
- Step 04
Start using Azure Log Analytics Workspace
Open Cascade and ask: "Using Azure Log Analytics Workspace, help me...". 1 tools available
Cline · IDE configuration
Advanced setup
{
"mcpServers": {
"azure-log-analytics-workspace": {
"url": "https://edge.vinkius.com/vk_preview_h8mzxcilFYlijQMfr5u3GIGk82xs7W4r1G5Um6EK/mcp"
}
}
}- Step 01
Open Cline MCP Settings
Click the Connectors icon in the Cline sidebar panel
- Step 02
Add remote server
Click "Add Connector" and paste the configuration above
- Step 03
Enable the server
Toggle the server switch to ON
- Step 04
Start using Azure Log Analytics Workspace
Ask Cline: "Using Azure Log Analytics Workspace, help me...". 1 tools available
Claude Code · Terminal command
Advanced setup
claude mcp add azure-log-analytics-workspace --transport http "https://edge.vinkius.com/vk_preview_h8mzxcilFYlijQMfr5u3GIGk82xs7W4r1G5Um6EK/mcp"- Step 01
Install Claude Code
Run npm install -g @anthropic-ai/claude-code if not already installed
- Step 02
Add the Connector
Run the command above in your terminal
- Step 03
Verify the connection
Run claude mcp to list connected servers, or type /mcp inside a session
- Step 04
Start using Azure Log Analytics Workspace
Ask Claude: "Using Azure Log Analytics Workspace, show me...". 1 tools are ready
Where the request belongs
Work Azure Log Analytics Workspace can move forward.
This is for the ops engineer who is tired of clicking through dashboards at 2am or the SRE who needs to find a needle in a haystack of telemetry without opening broad permissions.
DevOps Engineer
Investigating a sudden spike in 500 errors during a deployment to see which service is failing.
SRE
Monitoring infrastructure health and identifying bottlenecks in real time during an incident.
Security Analyst
Checking specific application logs for suspicious activity patterns in a targeted environment.
Cloud Architect
Auditing traffic patterns to plan for scaling and identifying common request paths.
Build the capability set
Add more capabilities.
Each Connector adds new actions and data without changing how you work.
Browse ConnectorsLogflare (Log Management Analytics)
Streamline log management and analytics via Logflare. ingest events, execute ad-hoc SQL queries, and trigger pre-configured endpoints directly from your AI agent.
Axiom
Manage logs and observability data via Axiom. ingest data, run APL queries, and manage datasets or monitors directly from any AI agent.
Google Cloud Logging Stream
This MCP does exactly one thing: it queries logs using Google Cloud Logging. That's its only function, and nothing else. Incredible for giving your AI secure observability.
Azure Synapse Analytics
Manage your Azure Synapse data pipelines seamlessly. audit Spark pools, SQL pools, datasets, and integration pipelines via your AI agent.
HyperDX (Open Source Observability)
Monitor logs, events, and alerts via HyperDX. search logs, manage alert rules, and inspect dashboards directly from your AI agent.
Logz.io
Query logs, manage alerts, and monitor triggered events in Logz.io directly from your AI agent using Elasticsearch DSL.
Bring your own AI
Change the model, client or framework. Keep Azure Log Analytics Workspace connected.
-
Claude -
ChatGPT -
Gemini -
Cursor -
VS Code -
Windsurf -
ZCode -
Cline -
Zed -
Continue -
Kiro -
Roo Code -
Zencoder -
Goose -
Void -
Augment Code -
Amp -
Qodo -
Tabnine -
Pieces -
Sourcegraph Cody -
JetBrains -
Warp -
Amazon Q -
Antigravity -
BoltAI -
Raycast -
Jan -
LM Studio -
AnythingLLM -
Open WebUI -
Msty -
Cherry Studio -
LibreChat -
TypingMind -
Chorus -
5ire -
n8n -
LangChain -
LlamaIndex -
CrewAI -
Vercel AI SDK
Before you connect
Questions about Azure Log Analytics Workspace.
The practical details behind the request, access and result.
Does the Azure Log Analytics Workspace MCP give my AI agent access to my whole account?
No, it's strictly locked to one specific table. This keeps your other logs and sensitive audit data safe.
Can I use my own KQL queries with this Connector?
Yes, the agent supports full Kusto Query Language syntax. You just need to describe what you want to find.
How does this Connector handle different types of logs?
It queries whichever table you configure it to use. You can point it at your application logs, web logs, or custom telemetry.
Is it safe to let an AI agent query my production logs?
Yes, because this Connector uses scoped access. It only has permission to run queries on the one table you've authorized.
Can the AI agent parse complex JSON data in my logs?
Yes, it can handle nested JSON payloads. It will extract the specific fields you're looking for to give you a clear answer.
Do I need to write the table name every time I ask a question?
No, the Connector automatically adds the table name to every query. You only need to provide the filters and logic.
Why limit the agent to a single Log Table?
To enforce zero-trust security. A Workspace often contains sensitive audit trails (like AzureActivity or SecurityEvents). By locking the agent to a specific table (e.g., 'AppExceptions'), you prevent it from reading global infrastructure access logs.
How should I format my KQL queries?
You do NOT need to include the table name. The Connector engine automatically handles the table prefix. Just pass the KQL operators starting with a pipe. Example: | where TimeGenerated > ago(1h) | limit 50.
One connection away
Give your agent a direct line to Azure Log Analytics Workspace.
Connect Azure Log Analytics Workspace once. Keep it beside 6,100+ managed Connectors when the next task needs more.
Explore every Connector No credit card required · Free tier available