Skip to main content
Glama
objectlens

ObjectLens MCP Server

Official
by objectlens

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
OBJECTLENS_API_URLNoBase URL of the ObjectLens REST APIhttp://localhost:8000
OBJECTLENS_PASSWORDNoPassword for HTTP Basic Authentication
OBJECTLENS_USERNAMENoUsername for HTTP Basic Authentication

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_providersA

List S3-compatible storage providers configured in ObjectLens.

get_default_providerA

Get connection details of the default/active storage provider.

list_bucketsA

List all S3 buckets for a specific provider, or the default provider if not specified.

:param provider_id: Optional connection ID of the provider.

list_bucket_objectsA

List or search objects inside a specific bucket, with prefix filtering and pagination.

:param bucket: The bucket name to query. :param prefix: Optional prefix/folder path (e.g. 'data/'). :param search: Optional search pattern or glob string (e.g. '*.json'). :param limit: Maximum items to return (default is 50). :param offset: Offset for pagination (default is 0). :param delimiter: Path separator (default is '/'). :param provider_id: Optional provider connection ID.

get_object_metadataA

Get detailed metadata for a specific object in a bucket.

:param bucket: Name of the bucket. :param key: Unique key/path of the object. :param provider_id: Optional provider connection ID.

get_object_previewA

Read the contents or preview of an S3 object. Useful for text, JSON, CSV, or code files.

:param bucket: Name of the bucket. :param key: Unique key/path of the object. :param max_bytes: Maximum number of bytes to retrieve (default is 1MB). :param provider_id: Optional provider connection ID.

search_objectsB

Search indexed object metadata in ObjectLens using a query pattern.

:param search: Broad search query (e.g. partial file name or type). :param bucket: Optional bucket name to scope the search. :param prefix: Optional prefix to scope the search. :param limit: Maximum search results (default 100). :param offset: Offset for pagination. :param provider_id: Optional provider connection ID.

scan_bucketA

Trigger a S3 bucket metadata scan to index object records into ObjectLens database.

:param bucket: The S3 bucket to index. :param provider_id: Optional provider connection ID.

list_activitiesA

List recent S3 activities/logs indexed in ObjectLens.

:param limit: Maximum activities to list (default is 10). :param offset: Offset for pagination.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.9/5.0

Scored across 9 tools

Disambiguation4/5

Most tools have clear distinct purposes: listing providers, getting default provider, listing buckets, listing objects, getting metadata, scanning, previewing, searching, and listing activities. The only slight overlap is between list_bucket_objects and search_objects, but the descriptions clarify one is a direct S3 listing while the other searches the indexed metadata.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern with lowercase and underscores: list_providers, get_default_provider, list_buckets, list_bucket_objects, get_object_metadata, scan_bucket, get_object_preview, search_objects, list_activities. This makes the set very predictable.

Tool Count5/5

With 9 tools, the server is well-scoped for S3 provider and object metadata management. Each tool covers a distinct aspect of listing, retrieval, scanning, and searching, and the count feels appropriate for the domain.

Completeness4/5

The tool set covers the core workflows of listing providers, buckets, objects, retrieving metadata and content, triggering scans, searching the index, and viewing activities. Minor gaps exist such as provider CRUD or object deletion, but these are likely outside the server's focus on indexing and browsing.

Maintenance

ActivitySlowing
ResponsivenessNo issues