Amazon CloudWatch Log Group Connector for AI agents.
1 live capability
Query specific AWS logs to troubleshoot production errors and infrastructure spikes.
Waiting for input…
Why people use Amazon CloudWatch Log Group
Amazon CloudWatch Log Group for Production Log Analysis
This Connector lets your agent do the digging for you. You just ask it to find the errors, and it handles the filtering and aggregation. You get the answer in seconds without ever leaving your workspace.
What Vinkius changes
You give your agent a secure window into one specific part of your logs so it can debug issues for you.
Use it from Claude, ChatGPT, Cursor or another AI client you already have.
One account · 6,100+ Connectors
- Real-world use case 01
Outage Triage
An SRE asks the agent to find the last 50 error messages to see if a new release broke the API.
- Real-world use case 02
Traffic Analysis
A developer wants to see if a specific user ID is hitting the system too frequently.
- Real-world use case 03
Deployment Check
A DevOps lead asks the agent to check for Started or Failed events in a container log group.
Complete set · 1capability
The complete Amazon CloudWatch Log Group capability set.
These are the exact actions your AI can choose when you ask it to work with Amazon CloudWatch Log Group.
01
1 capability in this set.
Part of 1 available through Amazon CloudWatch Log Group.
- 01 Capability
Filter log events
Search and filter log events in the configured CloudWatch Log Group. This lets the AI find specific errors or patterns instantly.
Set up in minutes
One URL. Then ask Amazon CloudWatch Log Group to work.
Claude and ChatGPT only need the Connector URL. Copy it once, add it in settings, and use Amazon CloudWatch Log Group 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_BfV9nj0spaNXUtgeLPe1LJiwTfYsjgKtxLFUXKh7/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 Amazon CloudWatch Log Group, and paste the URL above.
- Step 03
Turn it on in chat
Select +, open Connectors, and enable Amazon CloudWatch Log Group for the conversation.
ChatGPT · Web + desktop
Connector URL · ready to paste
Streamable HTTPhttps://edge.vinkius.com/vk_preview_BfV9nj0spaNXUtgeLPe1LJiwTfYsjgKtxLFUXKh7/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 Amazon CloudWatch Log Group URL.
- Step 03
Save and start
Save the connection and enable Amazon CloudWatch Log Group in your conversation. Desktop may ask you to restart once.
Cursor · IDE configuration
Advanced setup
{
"mcpServers": {
"amazon-cloudwatch-log-group": {
"url": "https://edge.vinkius.com/vk_preview_BfV9nj0spaNXUtgeLPe1LJiwTfYsjgKtxLFUXKh7/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 Amazon CloudWatch Log Group
Open Agent mode in chat and ask: "Using Amazon CloudWatch Log Group, help me...". 1 tools available
VS Code Copilot · IDE configuration
Advanced setup
{
"mcpServers": {
"amazon-cloudwatch-log-group": {
"url": "https://edge.vinkius.com/vk_preview_BfV9nj0spaNXUtgeLPe1LJiwTfYsjgKtxLFUXKh7/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 Amazon CloudWatch Log Group
Ask Copilot: "Using Amazon CloudWatch Log Group, help me...". 1 tools available
Windsurf · IDE configuration
Advanced setup
{
"mcpServers": {
"amazon-cloudwatch-log-group": {
"url": "https://edge.vinkius.com/vk_preview_BfV9nj0spaNXUtgeLPe1LJiwTfYsjgKtxLFUXKh7/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 Amazon CloudWatch Log Group
Open Cascade and ask: "Using Amazon CloudWatch Log Group, help me...". 1 tools available
Cline · IDE configuration
Advanced setup
{
"mcpServers": {
"amazon-cloudwatch-log-group": {
"url": "https://edge.vinkius.com/vk_preview_BfV9nj0spaNXUtgeLPe1LJiwTfYsjgKtxLFUXKh7/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 Amazon CloudWatch Log Group
Ask Cline: "Using Amazon CloudWatch Log Group, help me...". 1 tools available
Claude Code · Terminal command
Advanced setup
claude mcp add amazon-cloudwatch-log-group --transport http "https://edge.vinkius.com/vk_preview_BfV9nj0spaNXUtgeLPe1LJiwTfYsjgKtxLFUXKh7/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 Amazon CloudWatch Log Group
Ask Claude: "Using Amazon CloudWatch Log Group, show me...". 1 tools are ready
Where the request belongs
Work Amazon CloudWatch Log Group can move forward.
This is for the DevOps engineer who's tired of digging through thousands of lines of logs manually during an incident. It's for SREs who need fast, automated answers to why a service is failing without the risk of over-privileging an AI.
SRE (Site Reliability Engineer)
Debugging production outages by asking the agent to find specific error codes.
DevOps Engineer
Monitoring deployment health by checking for failed container starts.
Security Analyst
Searching for specific IP addresses or failed login attempts in a dedicated security log group.
Build the capability set
Add more capabilities.
Each Connector adds new actions and data without changing how you work.
Browse ConnectorsPapertrail (Real-time Cloud Log Manager)
Manage and analyze cloud logs in real-time via Papertrail. search events, list systems, and organize log groups directly from your 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.
Loggly (Cloud Log Management API)
Manage cloud logs via Loggly. send events, execute Lucene searches, and analyze infrastructure metrics directly from your AI agent.
Logflare (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.
Logz.io
Query logs, manage alerts, and monitor triggered events in Logz.io directly from your AI agent using Elasticsearch DSL.
HyperDX (Open Source Observability)
Monitor logs, events, and alerts via HyperDX. search logs, manage alert rules, and inspect dashboards directly from your AI agent.
Bring your own AI
Change the model, client or framework. Keep Amazon CloudWatch Log Group 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 Amazon CloudWatch Log Group.
The practical details behind the request, access and result.
What can the Amazon CloudWatch Log Group MCP do?
It lets your AI agent query a specific log group for errors, traffic spikes, and other events. This helps you quickly identify issues without manual searching.
Is it safe to give my AI agent access to logs?
Yes, because it's scoped to only one specific log group. It won't see your sensitive audit trails or other logs.
Can it handle JSON logs?
Yes, it supports CloudWatch Insights syntax, which means your agent can parse and aggregate structured JSON data.
How do I use the Amazon CloudWatch Log Group MCP for debugging?
You can ask your agent to find specific error codes or summarize the last hour of logs to see if a deployment was successful.
Does it work with my existing AWS setup?
Yes, it connects to your existing CloudWatch Log Groups using the permissions you provide.
Can the AI agent search across multiple log groups?
No, this specific MCP is designed to be a surgical capability for one log group at a time.
Why limit the agent to a single Log Group?
To enforce zero-trust architecture. An autonomous agent debugging a specific lambda function shouldn't have access to your organization's central VPC Flow Logs or RDS audit logs.
Can the agent delete logs?
No. This capability provides strict read-only access using only the FilterLogEvents API.
What is a filter pattern?
It's a syntax provided by AWS CloudWatch to search for specific terms or JSON properties. For example, 'ERROR' will return only lines containing the word ERROR.
One connection away
Give your agent a direct line to Amazon CloudWatch Log Group.
Connect Amazon CloudWatch Log Group once. Keep it beside 6,100+ managed Connectors when the next task needs more.
Explore every Connector No credit card required · Free tier available