Akave MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AKAVE_ENDPOINT_URL | Yes | Your Akave Endpoint URL | |
| AKAVE_ACCESS_KEY_ID | Yes | Your Akave Access Key ID | |
| AKAVE_SECRET_ACCESS_KEY | Yes | Your Akave Secret Access Key |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_bucketsB | List all buckets in Akave storage |
| list_objectsC | List objects in a bucket |
| get_objectC | Get object content from a bucket |
| put_objectC | Put object into a bucket |
| get_signed_urlC | Get a signed URL for an object |
| update_objectC | Update (overwrite) an object in a bucket |
| fetch_headersC | Fetch headers/metadata for an object |
| delete_objectC | Delete an object from a bucket |
| copy_objectC | Copy an object to another bucket/key |
| create_bucketC | Create a new bucket |
| delete_bucketC | Delete a bucket |
| get_bucket_locationC | Get the region/location of a bucket |
| list_object_versionsC | List all versions of objects in a bucket (if versioning enabled) |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 13 tools
Every tool has a clearly distinct purpose targeting specific resources and actions in the Akave storage domain. For example, copy_object, put_object, and update_object handle different write operations, while get_object and fetch_headers serve separate read purposes. No tools appear to overlap in functionality, making selection straightforward for an agent.
All tools follow a consistent verb_noun naming pattern with snake_case throughout, such as create_bucket, delete_object, and list_objects. This uniformity enhances readability and predictability, allowing agents to easily infer tool functions from their names without confusion from mixed conventions.
With 13 tools, the server is well-scoped for managing Akave storage operations, covering essential CRUD and lifecycle tasks for buckets and objects. Each tool earns its place by addressing specific needs like versioning, signed URLs, and metadata, without being overly sparse or bloated.
The tool set provides complete CRUD and lifecycle coverage for the Akave storage domain, including bucket management (create, delete, list, location) and object handling (get, put, update, delete, copy, signed URLs, headers, versions). There are no obvious gaps, ensuring agents can perform all core workflows without dead ends.