MCP 8048a81b

MCPAI代理

提供方 未标注

AI代理 HTTP · 远程 未标注 社区 / 第三方
查看接入方式

全面解析MCP Amazon Cloudwatch LogsMCP Server的核心功能、安装配置和实用案例。作为顶级Model Context Protocol服务器,MCP Amazon Cloudwatch Logs能让AI助手访问实时数据、执行操作,为您提供更智能的工作体验和自动化解决方案。

一句话选型结论

按资料字段整理

MCP 8048a81b 属于AI代理类 MCP 服务器,HTTP · 远程,鉴权方式未标注,有可直接复制的远程端点配置。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类AI代理 传输方式HTTP · 远程 鉴权未标注 部署方式远程部署
GitHub 星标 未标注 仓库热度,无公开仓库时显示未标注
工具数 未标注 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

AI代理
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量未标注暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

安装与配置

HTTP · 远程 未标注
连远程 HTTPS 端点,通常为 Streamable HTTP
npm install amazon-cloudwatch-logs-mcp-server

这条命令只是入口,具体启动参数请按官方文档补齐,不要直接照搬到别的服务器。

  1. 1
    准备运行环境

    确认你的客户端支持远程端点,并拿到服务地址。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后随便调一个只读工具,确认能返回结果,再接入正式流程。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
给代理接外部能力

让代理在任务中途调用搜索、数据库等真实工具。

多步任务编排

把一串操作拆成步骤,由代理按顺序执行。

自动化重复流程

把固定流程交给代理跑,减少手工操作。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 有现成的安装命令,不用自己找入口,照着跑就能起服务。

先想清楚的地方

  • 远程端点依赖网络与服务方可用性,注意密钥与调用额度。
  • 资料没标注工具数量,实际能力要装好后确认。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在AI代理场景里让模型直接调用外部能力的人。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
MCP 8048a81b当前 未标注 HTTP · 远程 远程部署 有 2026-05-17
Filesystem 560c4363 13 未标注 本地部署 无 2026-05-17
Server Everything (everything) 11 stdio · 本地进程 本地部署 有 2026-05-17
Time 7365cb6d 2 SSE · 服务端推送 远程部署 有 2026-05-18
Everything Claude Code 未标注 stdio · 本地进程 本地部署 有 2026-05-17
Openmemory 557e1585 未标注 stdio · 本地进程 本地部署 有 2026-05-17

服务器档案

AI代理
字段来自项目仓库与公开索引,中文说明由本站标注
提供方未标注上游标注的维护方 未标注
分类AI代理本站按上游分类展示
连接方式HTTP · 远程连远程 HTTPS 端点,通常为 Streamable HTTP
鉴权方式未标注远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时未标注 · Node.js本地安装时用到的包标识与运行时
部署类型远程部署上游给出的部署形态
最近核验2026-05-17上游最后核验时间

详细介绍

9.8 KB
来自项目仓库与上游目录的原文,未做删改

Amazon CloudWatch Logs MCP Server

A Model Context Protocol (MCP) server that provides tools for interacting with Amazon CloudWatch Logs services. This server enables AI assistants to manage CloudWatch logs through a standardized interface using AWS SDK.

> Note: This project is currently under active development and not yet ready for production use. Features and APIs may change significantly before the first stable release.

Overview

This MCP server allows AI assistants to interact with Amazon CloudWatch Logs through the Model Context Protocol. It provides a standardized interface for performing various CloudWatch Logs operations, enabling comprehensive management and monitoring of log data.

Quick Start

Prerequisites

  • AWS account with CloudWatch Logs access
  • AWS access key and secret key with appropriate permissions
  • Node.js (for npm installation) or Docker

Installation

Choose one of the following installation methods:

Option 1: npm Package```bash

Install the package

npm install -g @hyorimitsu/amazon-cloudwatch-logs-mcp-server

Configure in your AI assistant's configuration

See Configuration section below


#### Option 2: Docker Image```bash
# Pull the Docker image
docker pull ghcr.io/hyorimitsu/mcp-amazon-cloudwatch-logs:latest

# Configure in your AI assistant's configuration
# See Configuration section below

Option 3: Local Development Build```bash

Clone the repository

git clone https://github.com/hyorimitsu/mcp-amazon-cloudwatch-logs.git
cd mcp-amazon-cloudwatch-logs

Install dependencies

pnpm install

Build the project

pnpm run build

Configure in your AI assistant's configuration

See Configuration section below


### Configuration

Add the server to your AI assistant's configuration:

#### For npm Installation```json
{
  "mcpServers": {
    "amazon-cloudwatch-logs": {
      "command": "amazon-cloudwatch-logs-mcp-server",
      "env": {
        "AWS_REGION": "us-east-1",
        "AWS_ACCESS_KEY_ID": "<YOUR_ACCESS_KEY>",
        "AWS_SECRET_ACCESS_KEY": "<YOUR_SECRET_KEY>"
      }
    }
  }
}

For Docker Installation```json

{
"mcpServers": {
"amazon-cloudwatch-logs": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"AWS_REGION",
"-e",
"AWS_ACCESS_KEY_ID",
"-e",
"AWS_SECRET_ACCESS_KEY",
"ghcr.io/hyorimitsu/mcp-amazon-cloudwatch-logs"
],
"env": {
"AWS_REGION": "us-east-1",
"AWS_ACCESS_KEY_ID": "<YOUR_ACCESS_KEY>",
"AWS_SECRET_ACCESS_KEY": "<YOUR_SECRET_KEY>"
}
}
}
}


#### For Local Development Build```json
{
  &quot;mcpServers&quot;: {
    &quot;amazon-cloudwatch-logs&quot;: {
      &quot;command&quot;: &quot;node&quot;,
      &quot;args&quot;: [&quot;/path/to/mcp-amazon-cloudwatch-logs/build/index.js&quot;],
      &quot;env&quot;: {
        &quot;AWS_REGION&quot;: &quot;us-east-1&quot;,
        &quot;AWS_ACCESS_KEY_ID&quot;: &quot;&lt;YOUR_ACCESS_KEY&gt;&quot;,
        &quot;AWS_SECRET_ACCESS_KEY&quot;: &quot;&lt;YOUR_SECRET_KEY&gt;&quot;
      }
    }
  }
}

Environment Variables

Variable Required Description Default
AWS_REGION No The AWS region where your CloudWatch Logs resources are located us-east-1
AWS_ACCESS_KEY_ID Yes Your AWS access key ID for authentication -
AWS_SECRET_ACCESS_KEY Yes Your AWS secret access key for authentication -
READONLY No When set to "true", only read operations are allowed false

Read-Only Mode

Enable read-only mode by setting the READONLY environment variable to &quot;true&quot;:json &quot;env&quot;: { &quot;AWS_REGION&quot;: &quot;us-east-1&quot;, &quot;AWS_ACCESS_KEY_ID&quot;: &quot;&lt;YOUR_ACCESS_KEY&gt;&quot;, &quot;AWS_SECRET_ACCESS_KEY&quot;: &quot;&lt;YOUR_SECRET_KEY&gt;&quot;, &quot;READONLY&quot;: &quot;true&quot; }

In read-only mode:

  • Only READ operations (tools that retrieve or query information) are available
  • WRITE operations (tools that create, modify, or delete resources) are disabled

This is useful for scenarios where you want to allow log viewing but prevent any modifications to your CloudWatch Logs resources.

Available Tools

Log Group Operations

Tool Name Operation Type Description
create_log_group WRITE Creates a log group with the specified name. You can create up to 1,000,000 log groups per Region per account.
describe_log_groups READ Lists the specified log groups. You can list all your log groups or filter the results by prefix. The results are ASCII-sorted by log group name.
delete_log_group WRITE Deletes the specified log group and permanently deletes all the archived log events associated with the log group.

Log Stream Operations

Tool Name Operation Type Description
create_log_stream WRITE Creates a log stream for the specified log group. A log stream is a sequence of log events that originate from a single source, such as an application instance or a resource that is being monitored.
describe_log_streams READ Lists the log streams for the specified log group. You can list all the log streams or filter the results by prefix. You can also control how the results are ordered.
delete_log_stream WRITE Deletes the specified log stream and permanently deletes all the archived log events associated with the log stream.

Log Event Operations

Tool Name Operation Type Description
put_log_events WRITE Uploads a batch of log events to the specified log stream.
get_log_events READ Lists log events from the specified log stream. You can list all of the log events or filter using a time range.
filter_log_events READ Lists log events from the specified log group. You can list all log events, or filter the results by one or more of the following: a filter pattern, a time range, or the log stream name (or a log stream name prefix that matches multiple log streams).

Insights Operations

Tool Name Operation Type Description
start_query READ Starts a query of one or more log groups using CloudWatch Logs Insights. You specify the log groups and time range to query and the query string to use.
stop_query READ Stops a CloudWatch Logs Insights query that is in progress. If the query has already ended, the operation returns an error indicating that the specified query is not running.
get_query_results READ Returns the results from the specified query.
describe_queries READ Returns a list of CloudWatch Logs Insights queries that are scheduled, running, or have been run recently in this account. You can request all queries or limit it to queries of a specific log group or queries with a certain status.

For detailed documentation on each tool, including parameters and examples, see TOOLS.md.

Development

For information on developing and extending this project, please see CONTRIBUTING.md.

License

This project is licensed under the MIT License - see the LICENSE file for details.

常见问题

7 问
答案由本站依据条目字段整理,不引用上游原文
MCP 8048a81b 怎么安装?

在客户端按下面的安装命令接入:npm install amazon-cloudwatch-logs-mcp-server。装完在客户端配置里引用同一个包或端点。

MCP 8048a81b 怎么在客户端里配置?

它的传输方式未标注,在客户端 MCP 配置里按官方文档填写启动命令和参数,保存后重启客户端生效。

MCP 8048a81b 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

MCP 8048a81b 需要 API Key 吗?

资料没有标注鉴权方式,是否需要密钥取决于服务本身,接入前按官方文档确认。

MCP 8048a81b 能提供哪些能力?

资料显示能力标签包括 日志管理、JavaScript、HTTP。具体工具清单以官方文档为准。

MCP 8048a81b 需要什么运行环境?

运行时为 Node.js;属于远程端点,不需要在本地装运行时。

MCP 8048a81b 是本地还是远程?

它是远程端点,连服务地址即可。传输方式为HTTP · 远程。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 2026-05-17。