Centralized steering pack and hooks management for your team
Before deploying the MCP Server, ensure you have the following installed:
Required for building Lambda functions
java --version
Build tool for Java projects
mvn --version
Configured with your AWS credentials
aws configure
Infrastructure as Code toolkit
npm install -g aws-cdk
git clone https://github.com/AdamBien/kiro-forge.git
cd kiro-forge/kiro-forge
cd cdk
cdk bootstrap
This sets up the necessary AWS resources for CDK deployments in your account.
cd ..
./buildAndDeployDontAsk.sh
This script builds the Lambda functions and deploys the entire stack.
After deployment, get your MCP server URL and User Pool Client ID from the CloudFormation outputs:
aws cloudformation describe-stacks \
--stack-name KiroForgeStack \
--query 'Stacks[0].Outputs'
Authenticate with AWS Cognito to get your access token:
export TOKEN=$(aws cognito-idp initiate-auth \
--region us-west-2 \
--auth-flow USER_PASSWORD_AUTH \
--client-id <YOUR_CLIENT_ID> \
--auth-parameters USERNAME=<email>,PASSWORD=<password> \
--query 'AuthenticationResult.AccessToken' \
--output text)
Add this configuration to .kiro/settings/mcp.json:
{
"mcpServers": {
"kiro-forge": {
"url": "<YOUR_GATEWAY_URL>/mcp",
"headers": {
"Authorization": "Bearer ${TOKEN}"
},
"disabled": false,
"autoApprove": [
"SteeringsRetriever___fetchSteerings"
]
}
}
}
Launch Kiro IDE from the same terminal where you exported the TOKEN:
kiro .
Store and share coding standards across your team
Automated validation and quality checks
Updates propagate instantly across all developers
Works with Kiro IDE, VSCode, and Q CLI
If you encounter any issues during deployment, check out our documentation or reach out on GitHub.