Serverless Web MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | HTTP server port (only used with http transport) | 3000 |
| MCP_TRANSPORT | No | Transport method (stdio or http) | stdio |
| TEMPLATES_PATH | No | Path to templates directory |
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": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| deployC | Deploy web applications to AWS, including database resources like DynamoDB tables. |
| get_logsC | Retrieve application logs from CloudWatch |
| get_metricsB | Fetch performance metrics for deployed applications |
| deployment_helpB | Get help with deployment requirements and troubleshooting |
| update_frontendB | Update frontend assets without redeploying the entire infrastructure |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| template-list | |
| deployment-list |
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose: deploying, getting help, retrieving logs, fetching metrics, and updating frontend assets. No ambiguity between them.
Most tools follow a verb_noun pattern (get_logs, get_metrics, update_frontend), but 'deploy' is a lone verb without an object, and 'deployment_help' is a noun+verb compound. This inconsistency could be confusing.
Five tools is well-scoped for a server focused on deployment and management of web apps on AWS. It covers essential operations without being excessive.
Core deployment, updates, logs, and metrics are covered, but missing operations like rollback, undeploy, or database updates create notable gaps for full lifecycle management.