Is this an official AWS CloudWatch MCP server?

No. It is Memtro's MCP server with Memtro's AWS CloudWatch connector behind it: the connector reads AWS CloudWatch through its API with the credentials you connect on Dashboard → Connections, and AWS CloudWatch publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.

Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.

Can it change anything in AWS CloudWatch?

Not yet. Today every AWS CloudWatch tool reads, searches or lists; when it gains actions, each is marked, granted by name and used only when you ask, so nothing is created, sent, updated or deleted until you say so.

Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.

MCP server · Engineering and operations

AWS CloudWatch MCP server

AWS CloudWatch in any MCP client, through Memtro: AWS CloudWatch does not publish this server. Memtro's AWS CloudWatch connector reads AWS CloudWatch through its API with the credentials you connect, and one endpoint hands those tools, every other system you connect and Memtro's memory tools to Claude Code, Cursor, Claude Desktop or anything else that speaks Streamable HTTP, as you.

What the model can do

Read-only AWS observability: list log groups, search logs with Logs Insights or filter patterns, list metrics, pull metric time series and read alarm states.

Reads

cloudwatch_log_groupsList CloudWatch log groups in the connected region, optionally by name prefix (e.g. /aws/lambda/).
cloudwatch_logs_insightsRun a CloudWatch Logs Insights query over one or more log groups and wait up to ~20s for results.
cloudwatch_filter_logsFetch raw log events from one log group matching a CloudWatch filter pattern (e.g. "ERROR", "{ $.level = \"error\" }"…
cloudwatch_metricsList available CloudWatch metrics, filtered by namespace (AWS/EC2, AWS/Lambda, AWS/RDS, AWS/ApplicationELB…), metric name and/or dimensions.
cloudwatch_metric_dataTime series for one CloudWatch metric over a window (default last 3 hours) using GetMetricData: namespace, metric name, exact dimensions, statistic…
cloudwatch_alarmsDescribe CloudWatch alarms (metric and composite) with their current state, reason and the metric/threshold they watch.

Connect it

First connect AWS CloudWatch on Dashboard → Connections, then add Memtro to your client once. The AWS CloudWatch tools appear alongside the tools of everything else you have connected; nothing is configured per connector.

Claude Code

One command registers the server; the tools are then available in every session.

claude mcp add --transport http memtro https://platform.memtro.com/api/mcp \
  --header "Authorization: Bearer sk-memtro-..."

Cursor

Add the server to .cursor/mcp.json in the project, or to the global file under ~/.cursor/.

{
  "mcpServers": {
    "memtro": {
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Claude Desktop

Create a personal API key on Dashboard → Profile → API keys. In Claude Desktop add an MCP server of type HTTP with URL https://platform.memtro.com/api/mcp and the header Authorization: Bearer sk-memtro-…

OpenCode

A remote server in opencode.json.

{
  "mcp": {
    "memtro": {
      "type": "remote",
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Any other client

Add an MCP server of type HTTP (Streamable HTTP, stateless) at https://platform.memtro.com/api/mcp with the header Authorization: Bearer sk-memtro-.... Codex, Zed, Windsurf, Cline and the SDKs all take a remote server this way.

Who may use it

The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared AWS CloudWatch connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.

Ask it like this

› What errors did the checkout Lambda log in the last hour?
› Show Lambda error counts for payments-api over the last 7 days
› Which alarms are in ALARM state right now and why?

Questions

Is this an official AWS CloudWatch MCP server?: No. It is Memtro's MCP server with Memtro's AWS CloudWatch connector behind it: the connector reads AWS CloudWatch through its API with the credentials you connect on Dashboard → Connections, and AWS CloudWatch publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.
What does it cost?: Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.
Can it change anything in AWS CloudWatch?: Not yet. Today every AWS CloudWatch tool reads, searches or lists; when it gains actions, each is marked, granted by name and used only when you ask, so nothing is created, sent, updated or deleted until you say so.
Which clients work?: Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.