AWS S3バケットを操作するためのツールを提供するMCPサーバー。このサーバーは、モデルコンテキストプロトコル（MCP）を介してS3バケット操作に直接アクセスすることを可能にします。
現在、サーバーは次のツールを実装しています。
list-s3-buckets : AWS アカウント内のすべての S3 バケットを一覧表示します
AWSリージョンを指定するためのオプションのregionパラメータ
バケット名のフォーマットされたリストを返します
Related MCP server: AWS S3 Control MCP Server
Python 3.13以上
AWS 認証情報が設定されている（ AWS 認証情報の設定を参照）
UVパッケージマネージャー
uvx install s3-toolsリポジトリをクローンする
uv を使用してインストールします。
uv pip install .このサーバーはS3バケットにアクセスするためにAWS認証情報を必要とします。認証情報はいくつかの方法で設定できます。
AWS CLI 設定（推奨）
aws configureこれにより~/.aws/credentialsに認証情報が作成/更新されます。
環境変数
export AWS_ACCESS_KEY_ID="your_access_key"
export AWS_SECRET_ACCESS_KEY="your_secret_key"
export AWS_DEFAULT_REGION="your_preferred_region" # optionalIAM ロール(AWS インフラストラクチャ上で実行されている場合)
AWS 認証情報の詳細については、 AWS ドキュメントを参照してください。
Claude Desktop 構成ファイルにサーバー構成を追加します。
MacOS : ~/Library/Application Support/Claude/claude_desktop_config.json
Windows : %APPDATA%/Claude/claude_desktop_config.json
{
"mcpServers": {
"s3-tools": {
"command": "uvx",
"args": ["s3-tools"]
}
}
}開発/テストの場合、ソースから直接サーバーを実行できます。
{
"mcpServers": {
"s3-tools": {
"command": "uv",
"args": [
"--directory",
"/path/to/s3-tools",
"run",
"s3-tools"
]
}
}
}同期の依存関係:
uv syncビルドパッケージ:
uv buildPyPI に公開するには:
uv publish注: PyPI 資格情報は次のように設定する必要があります。
トークン: --tokenまたはUV_PUBLISH_TOKEN
またはユーザー名/パスワード: --username / UV_PUBLISH_USERNAMEおよび--password / UV_PUBLISH_PASSWORD
MCPサーバーはstdio経由で通信するため、デバッグが困難になる場合があります。開発にはMCP Inspectorの使用をお勧めします。
npx @modelcontextprotocol/inspector uv run s3-toolsマサチューセッツ工科大学
貢献を歓迎します！お気軽にプルリクエストを送信してください。
List all S3 buckets in your AWS account
| Name | Required | Description | Default |
|---|---|---|---|
| region | No | AWS region (optional, defaults to configured region) |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries full burden for behavioral disclosure. It mentions 'all S3 buckets' which implies completeness, but doesn't address permissions needed, rate limits, pagination, error conditions, or what the output looks like. For a tool with zero annotation coverage, this is inadequate.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, efficient sentence with zero wasted words. It's appropriately sized for a simple list operation and front-loads the core functionality.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a tool with no annotations, no output schema, and minimal behavioral disclosure, the description is incomplete. It should address authentication requirements, output format, and potential limitations given this is an AWS operation that could have permission constraints.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the schema already documents the single optional 'region' parameter. The description doesn't add any parameter-specific information beyond what's in the schema. Baseline 3 is appropriate when schema does the heavy lifting.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the action ('List') and resource ('all S3 buckets in your AWS account'), providing a specific verb+resource combination. It doesn't need to distinguish from siblings since none exist, so it earns a 4 rather than 5.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides no guidance on when to use this tool versus alternatives, prerequisites, or contextual constraints. It simply states what the tool does without any usage instructions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
list-s3-bucketsScored across 1 tool
With only one tool, there is no possibility for ambiguity or overlap between tools, as there are no other tools to compare it to. The tool's purpose is clearly defined and distinct by default.
Since there is only one tool, naming consistency is inherently perfect with no deviations or mixed conventions to evaluate. The tool name 'list-s3-buckets' follows a clear verb_noun pattern.
A single tool for an S3 server is too few for the apparent scope, as S3 involves operations like uploading, downloading, deleting objects, and managing buckets beyond listing. This minimal set will likely cause agent failures due to significant functional gaps.
The tool surface is severely incomplete for an S3 domain, covering only bucket listing. There are obvious gaps for core operations such as creating/deleting buckets, managing objects (upload, get, delete), and other essential S3 functionalities, making it inadequate for typical use cases.
An MCP server that provides read access to your cloud storage providers, bank accounts and more.
Tigris MCP Server seamlessly connects AI agents to Tigris bucket and object management.
The AWS Knowledge MCP server is a fully managed remote Model Context Protocol server that provides real-time access to official AWS content in an LLM-compatible format. It offers structured access to AWS documentation, code samples, blog posts, What's New announcements, Well-Architected best practices, and regional availability information for AWS APIs and CloudFormation resources. Key capabilities include searching and reading documentation in markdown format, getting content recommendations, listing AWS regions, and checking regional availability for services and features.
MCP server for Product Management
