Skip to main content
Glama
eunyuljo

aws-helper MCP Server

by eunyuljo
README.md
# aws-helper MCP Server

A Model Context Protocol server

This is a TypeScript-based MCP server that implements a simple notes system. It demonstrates core MCP concepts by providing:

- Resources representing text notes with URIs and metadata
- Tools for creating new notes
- Prompts for generating summaries of notes

## Features

### Resources
- List and access notes via `note://` URIs
- Each note has a title, content and metadata
- Plain text mime type for simple content access

### Tools
- `create_note` - Create new text notes
  - Takes title and content as required parameters
  - Stores note in server state

### Prompts
- `summarize_notes` - Generate a summary of all stored notes
  - Includes all note contents as embedded resources
  - Returns structured prompt for LLM summarization

## Development

Install dependencies:
```bash
npm install
```

Build the server:
```bash
npm run build
```

For development with auto-rebuild:
```bash
npm run watch
```

## Installation

To use with Claude Desktop, add the server config:

On MacOS: `~/Library/Application Support/Claude/claude_desktop_config.json`
On Windows: `%APPDATA%/Claude/claude_desktop_config.json`

```json
{
  "mcpServers": {
    "aws-helper": {
      "command": "/path/to/aws-helper/build/index.js"
    }
  }
}
```

### Debugging

Since MCP servers communicate over stdio, debugging can be challenging. We recommend using the [MCP Inspector](https://github.com/modelcontextprotocol/inspector), which is available as a package script:

```bash
npm run inspector
```

The Inspector will provide a URL to access debugging tools in your browser.

TDQS

C2.8/5.0

Scored across 3 tools

Disambiguation2/5

Two tools (get_ec2_instances and get_ec2_summary) have overlapping purposes focused on EC2 instances, creating ambiguity about when to use each. While get_aws_identity is clearly distinct, the EC2 tools could easily be confused as they both retrieve EC2-related information without clear boundaries in their descriptions.

Naming Consistency5/5

All three tools follow a consistent verb_noun naming pattern with 'get_' prefix and snake_case formatting. The naming is predictable and follows the same convention throughout the toolset.

Tool Count2/5

With only 3 tools for an AWS helper server, the scope feels extremely thin. AWS has dozens of services, but this server only covers identity and EC2 instances, making it feel incomplete for a general AWS helper purpose.

Completeness2/5

For an AWS helper server, there are significant gaps in coverage. The server only provides read-only operations for identity and EC2, missing core AWS services like S3, Lambda, RDS, IAM management, and any write/update/delete operations. The surface is severely incomplete for assisting with AWS tasks.

Maintenance

ActivityInactive
ResponsivenessNo issues