ALECS - MCP server for Akamai
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AKAMAI_EDGERC_PATH | No | Path to the Akamai .edgerc file containing API credentials | ~/.edgerc |
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 |
|---|---|
| property.listC | List Akamai CDN properties |
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 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool 'property.list' has a clearly distinct purpose of listing Akamai CDN properties, and no other tools exist to cause confusion.
The naming pattern is perfectly consistent as there is only one tool. It follows a clear verb_noun structure ('property.list'), and with no other tools to compare against, there is no inconsistency in naming conventions.
A single tool is too few for a server intended to interact with Akamai's CDN properties, which typically involve operations like create, update, delete, or get details. This minimal set severely limits functionality and suggests an incomplete implementation for the domain.
The tool set is severely incomplete for managing Akamai CDN properties. It only provides listing functionality, missing essential CRUD operations such as create, read (get details), update, and delete, as well as other domain-specific actions like activating or deactivating properties, which are critical for a comprehensive CDN management surface.