floci-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AWS_ACCESS_KEY_ID | No | Credential; a 12-digit value selects a Floci account (multi-account isolation) | test |
| AWS_DEFAULT_REGION | No | Region passed to every boto3 client | us-east-1 |
| FLOCI_ENDPOINT_URL | No | Floci's HTTP endpoint | http://localhost:4566 |
| AWS_SECRET_ACCESS_KEY | No | Credential (any non-empty value works against Floci) | test |
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
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| aws_callA | Call any AWS API operation against the local Floci instance. service: boto3 service name (e.g. 'ec2', 's3', 'lambda', 'rds'). action: the AWS API operation name, e.g. 'RunInstances' or 'run_instances'. params: a JSON object of API parameters exactly as AWS documents them, e.g. {"Bucket": "my-bucket"}. |
| floci_statusA | Check whether the configured Floci instance is reachable. |
| floci_inventoryA | Summarize resources currently deployed on Floci across common services: S3, DynamoDB, Lambda, EC2, SQS, SNS, ECS, RDS. |
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 3 tools
The three tools have clearly distinct purposes: aws_call for arbitrary AWS operations, floci_status for connectivity checks, and floci_inventory for resource summaries. There is no overlap or ambiguity between them.
Two tools follow a `floci_` snake_case prefix pattern, but `aws_call` uses camelCase and doesn't follow the same convention. The mixed naming style is noticeable but still readable.
With only 3 tools, the set is tightly scoped and every tool earns its place. The number is appropriate for a server that provides a generic AWS API pass-through plus convenience utilities.
The `aws_call` tool covers the full AWS API surface, so any operation can be performed. `floci_status` and `floci_inventory` fill specific monitoring and overview gaps, providing a complete workflow without dead ends.