watsonx Orchestrate Lambda Deployer - MCP Server
This project contains MCP server implementations for automating AWS Lambda API Gateway deployment.
Available Implementations
1. TypeScript/Node.js Implementation (Recommended - Currently Active)
Location: /Users/amandawinkles/Documents/IBM Bob/MCP/wxo-lambda-deployer/
Status: ✅ Fully functional and configured
Requirements:
- Node.js 18+ or 20+
- npm
- AWS CLI configured
- Terraform 1.0+
Features:
- 6 automation tools for Lambda deployment
- Complete test suite (22 passing tests)
- Full documentation
- Currently configured in Bob MCP settings
Tools Available:
init_lambda_project- Initialize Lambda projectsdeploy_lambda- Deploy with Terraformupdate_lambda_code- Update and redeploy codeget_deployment_status- Check deployment statusdestroy_lambda- Clean up resourcestest_lambda_endpoint- Test API endpoints
2. Python Implementation
Location: /Users/amandawinkles/bob/wxO-nit/server.py
Status: ⚠️ Requires Python 3.10+ (current system has Python 3.9.6)
Requirements:
- Python 3.10 or higher
- fastmcp package
- AWS CLI configured
- Terraform 1.0+
Note: The Python implementation is provided but cannot run on the current system due to Python version constraints. FastMCP requires Python 3.10+, but the system has Python 3.9.6.
Current Configuration
The TypeScript implementation is currently active and configured in:
~/.bob/settings/mcp_settings.json
{
"mcpServers": {
"wxo-lambda-deployer": {
"command": "node",
"args": [
"/Users/amandawinkles/Documents/IBM Bob/MCP/wxo-lambda-deployer/build/index.js"
],
"env": {
"AWS_PROFILE": "default"
}
}
}
}
Usage
After restarting Bob, you can use commands like:
"Initialize a new Lambda project called my-api with Node.js 20"
"Deploy the Lambda project"
"Test the Lambda endpoint"
"Get deployment status"
"Destroy the Lambda deployment"
Terraform Deployment Example
The MCP server was used to deploy the existing Terraform configuration in this directory:
# The terraform/ directory contains:
- terraform.tf # Provider configuration
- main.tf # Lambda, API Gateway, S3, IAM resources
- outputs.tf # API endpoint and resource outputs
- variables.tf # Configuration variables
# Deployment was completed with:
terraform init
terraform validate
terraform plan
terraform apply
Upgrading to Python Implementation
If you upgrade to Python 3.10+, you can use the Python implementation:
-
Install Python 3.10+:
brew install python@3.10 # macOS
-
Install dependencies:
pip3 install -r requirements.txt
-
Update MCP settings:
{ "mcpServers": { "wxo-lambda-deployer": { "command": "python3", "args": [ "/Users/amandawinkles/bob/wxO-nit/server.py" ], "env": { "AWS_PROFILE": "default" } } } }
-
Make server executable:
chmod +x server.py
Documentation
- TypeScript Implementation:
/Users/amandawinkles/Documents/IBM Bob/MCP/wxo-lambda-deployer/README.md - Contributing Guide:
/Users/amandawinkles/Documents/IBM Bob/MCP/wxo-lambda-deployer/CONTRIBUTING.md - Test Suite:
/Users/amandawinkles/Documents/IBM Bob/MCP/wxo-lambda-deployer/src/__tests__/tools.test.ts
Architecture
User Request
↓
Bob/Claude (MCP Client)
↓
MCP Protocol
↓
wxo-lambda-deployer (TypeScript)
↓
Terraform CLI
↓
AWS API
↓
Lambda + API Gateway + S3 + IAM + CloudWatch
Support
For issues or questions about the MCP server:
- Check the main README in the TypeScript implementation directory
- Review test cases for usage examples
- Consult Terraform documentation for infrastructure details
Metadata
Release files for wxo-nit 1.0.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| wxo_nit-1.0.0.tar.gz | 8.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| wxo_nit-1.0.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 26.6 kB
Release files / wxo_nit-1.0.0.tar.gz
| Download URL | wxo_nit-1.0.0.tar.gz |
|---|---|
| Size | 8.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0b33bdf78fc06b9a0581134167de08c9c80268ed8547938bbf871eea81047388
|
|
BLAKE2b-256 checksum How to use checksums |
154ce4f260cc1bef40a44a99172d1382017128543f8865e3c19fa4cafff1f480
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.12
|
Release files / wxo_nit-1.0.0-py3-none-any.whl
| Download URL | wxo_nit-1.0.0-py3-none-any.whl |
|---|---|
| Size | 17.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f826e0712e1b127a6d2bbec3a45596c7b839c3afbb7c37ba559534a164788b2f
|
|
BLAKE2b-256 checksum How to use checksums |
69ba49760e0343cd305ba920661d1bfc1a1b4715e47a1d997e3457fcb074c379
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.12
|
Security for wxo-nit 1.0.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.