Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
S3_MCP_ALLOWED_PATHSYesList of absolute local transfer directories, separated by the operating system's path separator (':' on macOS/Linux, ';' on Windows). Transfers are disabled unless at least one directory is listed.
S3_MCP_ALLOWED_BUCKETSNoOptional comma-separated list of bucket names to restrict bucket operations to.
S3_MCP_MAX_TRANSFER_BYTESNoOptional maximum upload/download size in bytes. Default is 104857600 bytes (100 MiB).104857600

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
list_bucketsB

List one bounded page of buckets visible to the configured AWS identity.

list_objectsC

List one bounded page of objects in a bucket.

inspect_bucketC

Inspect bucket configuration and include per-check collection coverage.

bucket_coverage_reportC

Report which supported configuration checks were collected, absent, denied or unsupported.

permission_reportB

Report observed bucket ACLs, policy, public-access controls and ownership without inferring effective access.

download_objectB

Download an object to a new file under S3_MCP_ALLOWED_PATHS.

upload_objectC

Upload a local file without overwriting an existing object.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.2/5.0

Scored across 7 tools

Disambiguation4/5

Most tools target clearly distinct S3 resources or operations: list, download, upload, and permission reporting are easy to separate. There is some potential overlap between inspect_bucket and bucket_coverage_report because inspect_bucket mentions collection coverage, but the descriptions make their intended roles mostly distinguishable.

Naming Consistency4/5

Five of the seven tools follow a clear verb_noun pattern: inspect_bucket, list_buckets, list_objects, download_object, upload_object. The two noun_report names are readable and domain-specific, but they introduce a minor convention deviation.

Tool Count5/5

Seven tools is well-scoped for an S3 inspection and transfer agent. Each tool covers a meaningful capability without obvious redundancy or bloat.

Completeness4/5

The surface covers core safe workflows: listing buckets and objects, inspecting bucket configuration, permission and coverage reporting, downloading, and uploading. It lacks destructive/admin operations such as delete_object or create/delete bucket, but those may be intentionally excluded for a safety-oriented S3 agent.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues