Skip to content

fix(deploy-on-aws): shorten MCP server names for Bedrock 64-char limit #133

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
Sagargupta16 wants to merge 1 commit into
base: main
Choose a base branch
from
Open

fix(deploy-on-aws): shorten MCP server names for Bedrock 64-char limit #133

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions plugins/deploy-on-aws/.mcp.json
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,16 +1,16 @@
{
"mcpServers": {
"awsiac": {
"iac": {
"args": [
"awslabs.aws-iac-mcp-server@latest"
],
"command": "uvx"
},
"awsknowledge": {
"knowledge": {
"type": "http",
"url": "https://knowledge-mcp.global.api.aws"
},
Comment thread
Sagargupta16 marked this conversation as resolved.
"awspricing": {
"pricing": {
"args": [
"awslabs.aws-pricing-mcp-server@latest"
],
Expand Down
6 changes: 3 additions & 3 deletions plugins/deploy-on-aws/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -17,9 +17,9 @@ This plugin provides two skills: infrastructure deployment with cost estimation,

| Server | Description |
| -------------- | ------------------------------------------------- |
| `awsiac` | AWS IaC best practices and patterns |
| `awsknowledge` | Architecture guidance and service recommendations |
| `awspricing` | Real-time AWS pricing data for cost estimation |
| `iac` | AWS IaC best practices and patterns |
| `knowledge` | Architecture guidance and service recommendations |
| `pricing` | Real-time AWS pricing data for cost estimation |

## Installation

Expand Down
6 changes: 3 additions & 3 deletions plugins/deploy-on-aws/skills/deploy/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -28,7 +28,7 @@ Core principle: Default to **dev-sized** (cost-conscious: small instance sizes,

## MCP Servers

### awsknowledge
### knowledge

Consult for architecture decisions. Use when choosing between AWS services
or validating that a service fits the use case. Helps answer "what's the
Expand All @@ -37,13 +37,13 @@ right AWS service for X?"
Key topics: `general` for architecture, `amplify_docs` for static sites/SPAs,
`cdk_docs` and `cdk_constructs` for IaC patterns.

### awspricing
### pricing

Get cost estimates. **Always present costs before generating IaC** so user
can adjust before committing. See [cost-estimation.md](references/cost-estimation.md)
for query patterns.

### awsiac
### iac

Consult for IaC best practices. Use when writing CDK/CloudFormation/Terraform
to ensure patterns follow AWS recommendations.
Expand Down
2 changes: 1 addition & 1 deletion plugins/deploy-on-aws/skills/deploy/references/cost-estimation.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
# Cost Estimation Patterns

Use the **awspricing** MCP server to get accurate cost estimates before generating IaC.
Use the **pricing** MCP server to get accurate cost estimates before generating IaC.

## Workflow

Expand Down
2 changes: 1 addition & 1 deletion plugins/deploy-on-aws/skills/deploy/references/defaults.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -27,7 +27,7 @@ Less configuration than S3 + CloudFront. Git-based deployments work out of the b
Use S3 + CloudFront when user needs fine-grained control over caching, edge functions,
or has existing CloudFront infrastructure.

Use `amplify_docs` topic in awsknowledge MCP for framework-specific guidance
Use `amplify_docs` topic in knowledge MCP for framework-specific guidance
(React, Next.js, Vue, Angular, etc.).

## Database
Expand Down
8 changes: 4 additions & 4 deletions plugins/deploy-on-aws/skills/deploy/references/security.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -72,7 +72,7 @@ through NAT Gateway. ALB is the only public-facing component.
### Dev simplification

For dev, a single-AZ VPC with 1 public + 1 private subnet is sufficient.
Use `awsknowledge` topic `vpc_patterns` for multi-AZ production layouts.
Use `knowledge` topic `vpc_patterns` for multi-AZ production layouts.

## IAM

Expand All @@ -89,7 +89,7 @@ Never use `*` for resources or actions unless unavoidable (e.g., S3 bucket
contents require `s3:GetObject` on `bucket/*`). Enumerate specific ARNs.
Use conditions where possible.

Consult `awsiac` MCP for IAM policy patterns by service.
Consult `iac` MCP for IAM policy patterns by service.

## Security Groups

Expand Down Expand Up @@ -187,5 +187,5 @@ When user requests "production" or "prod", additionally enable:

## MCP References

- `awsknowledge` topics: `vpc_patterns`, `iam_best_practices`, `security`
- `awsiac` for CDK security constructs (L2 constructs apply many defaults)
- `knowledge` topics: `vpc_patterns`, `iam_best_practices`, `security`
- `iac` for CDK security constructs (L2 constructs apply many defaults)
Loading