Amazon VPC Lattice MCP Server
The Amazon VPC Lattice MCP Server allows you to discover documentation and manage VPC Lattice resources through several key functions:
List available documentation sources with their URLs and sample prompts
Retrieve sample prompts for specific sources
Access predefined VPC Lattice prompt templates and their details
Execute AWS CLI commands to manage VPC Lattice resources including Service Networks, Services, Listeners, Rules, Target Groups, Targets, and resource tags
Handle complex AWS configurations including boolean flags, arrays, and AWS profiles/region settings
Provides access to the AWS Gateway API Controller for VPC Lattice repository on GitHub, allowing users to retrieve source information and prompts related to this project.
Enables access to Kubernetes Gateway API documentation and resources, providing source information and sample prompts for working with VPC Lattice in Kubernetes environments.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Amazon VPC Lattice MCP Server list my service networks in us-west-2"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Amazon VPC Lattice MCP Server
A Model Context Protocol (MCP) server for source listing, providing tools for accessing and managing AWS VPC Lattice resources and related documentation.
Features
The server provides five main tools:
list_sources: Lists all available sources with their URLs and sample promptsget_source_prompts: Gets sample prompts for a specific sourcelist_amazon_vpc_lattice_prompts: Lists all available prompt templatesget_amazon_vpc_lattice_prompts: Gets details of a specific prompt templatevpc_lattice_cli: Execute AWS CLI VPC Lattice commands for managing VPC Lattice resources
Related MCP server: Log Analyzer with MCP
Installation
This project is built with TypeScript and uses ES modules. Note that installing github-mcp-server is also strongly recommended to assist with development prompts.
Clone the repository:
git clone https://github.com/awslabs/amazon-vpc-lattice-mcp-server.git
cd amazon-vpc-lattice-mcp-serverInstall dependencies:
npm installBuild the server:
npm run buildThe build script will compile the TypeScript code and set the appropriate executable permissions.
Configuration
Add the server to your MCP settings file (located at ~/Library/Application Support/Code/User/globalStorage/asbx.amzn-cline/settings/cline_mcp_settings.json):
{
"mcpServers": {
"amazon-vpc-lattice": {
"command": "node",
"args": ["/path/to/amazon-vpc-lattice-mcp-server/build/index.js"],
"disabled": false,
"autoApprove": [],
"env": {}
}
}
}Usage
Once configured, you can use the MCP tools in your conversations. Note that you should use list_amazon_vpc_lattice_prompts to discover available prompts as these are not automatically discoverable like tools.
List Sources
use_mcp_tool({
server_name: "amazon-vpc-lattice",
tool_name: "list_sources",
arguments: {}
})Get Source Prompts
use_mcp_tool({
server_name: "amazon-vpc-lattice",
tool_name: "get_source_prompts",
arguments: {
source_name: "AWS Documentation"
}
})List Amazon VPC Lattice Prompts
use_mcp_tool({
server_name: "amazon-vpc-lattice",
tool_name: "list_amazon_vpc_lattice_prompts",
arguments: {}
})Get Amazon VPC Lattice Prompt Details
use_mcp_tool({
server_name: "amazon-vpc-lattice",
tool_name: "get_amazon_vpc_lattice_prompts",
arguments: {
prompt_name: "setup_eks_controller"
}
})VPC Lattice CLI
The vpc_lattice_cli tool provides a programmatic interface to AWS VPC Lattice operations through the AWS CLI.
Features
Supports all major VPC Lattice CLI operations
Accepts command arguments as JavaScript objects
Automatically converts camelCase parameters to CLI-style kebab-case
Handles boolean flags, arrays, and complex values
Supports AWS profiles and region configuration
Returns parsed JSON responses
Available Commands
Service Network: create-service-network, delete-service-network, get-service-network, list-service-networks, update-service-network
Service: create-service, delete-service, get-service, list-services, update-service
Listener: create-listener, delete-listener, get-listener, list-listeners, update-listener
Rule: create-rule, delete-rule, get-rule, list-rules, update-rule
Target Group: create-target-group, delete-target-group, get-target-group, list-target-groups, update-target-group
Target Management: register-targets, deregister-targets, list-targets
Resource Tags: list-tags-for-resource, tag-resource, untag-resource
Examples
List service networks:
use_mcp_tool({
server_name: "amazon-vpc-lattice",
tool_name: "vpc_lattice_cli",
arguments: {
command: "list-service-networks",
region: "us-west-2"
}
})Create a service network:
use_mcp_tool({
server_name: "amazon-vpc-lattice",
tool_name: "vpc_lattice_cli",
arguments: {
command: "create-service-network",
args: {
name: "my-network",
authType: "NONE"
}
}
})Create a service with tags:
use_mcp_tool({
server_name: "amazon-vpc-lattice",
tool_name: "vpc_lattice_cli",
arguments: {
command: "create-service",
args: {
name: "my-service",
serviceNetworkIdentifier: "sn-12345",
tags: [
{ key: "Environment", value: "Production" }
]
}
}
})Create a target group:
use_mcp_tool({
server_name: "amazon-vpc-lattice",
tool_name: "vpc_lattice_cli",
arguments: {
command: "create-target-group",
args: {
name: "my-target-group",
type: "INSTANCE",
config: {
port: 80,
protocol: "HTTP",
healthCheck: {
enabled: true,
protocol: "HTTP",
path: "/health"
}
}
}
}
})Available Sources
The server includes these sources:
AWS Documentation (docs.aws.amazon.com)
Key features queries
Configuration guidance
Best practices
AWS Gateway API Controller for VPC Lattice (aws/aws-application-networking-k8s)
Feature support queries
Issue tracking
Kubernetes Gateway API (gateway-api.sigs.k8s.io)
Error resolution
Best practices guidance
Development
Project Structure
The project is organized as follows:
src/index.ts: Main server setup and initializationsrc/tools.ts: Tool definitions and handlerssrc/data/: Data filesprompts.ts: Prompt templates and parameterssources.ts: Source definitions and their prompts
package.json: Project configuration and dependenciestsconfig.json: TypeScript configuration.gitignore: Git ignore rulesbuild/: Compiled JavaScript output
Adding New Sources
To add new sources, modify the sources array in src/data/sources.ts:
export const sources = [
{
name: 'Your Source',
url: 'https://your-source-url.com',
prompts: [
'Sample prompt 1 {placeholder}',
'Sample prompt 2 {placeholder}'
]
}
// ... existing sources
];Adding New Prompts
To add new prompt templates, modify the prompts array in src/data/prompts.ts:
export const prompts = [
{
name: 'Your Prompt Template',
description: 'Description of what the prompt does',
template: 'Your prompt template with {parameter} placeholders',
parameters: ['parameter']
}
// ... existing prompts
];Scripts
npm run build: Build the server and set executable permissionsnpm run watch: Watch mode for developmentnpm test: Run tests (currently not implemented)
Available Tools
5 toolsget_amazon_vpc_lattice_promptsC
Get details of a specific prompt template
Inputs: prompt_name (required).
get_source_promptsB
Get sample prompts for a specific source
Inputs: source_name (required).
list_amazon_vpc_lattice_promptsB
List all available prompt templates
Inputs: no named parameters.
list_sourcesB
List all available sources with their URLs and sample prompts
Inputs: no named parameters.
vpc_lattice_cliC
Execute AWS CLI VPC Lattice commands
Inputs: command (required), args, profile, region.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 5 tools
The tools have some overlap but descriptions help clarify distinctions. 'get_amazon_vpc_lattice_prompts' and 'get_source_prompts' both retrieve prompts but target different entities (templates vs. sources), while 'list_amazon_vpc_lattice_prompts' and 'list_sources' similarly list different items. The 'vpc_lattice_cli' tool stands apart for CLI execution, but the prompt-related tools could cause mild confusion without careful reading.
The naming is mostly consistent with a verb_noun pattern, using 'get_' and 'list_' prefixes clearly. However, 'vpc_lattice_cli' deviates by omitting a verb and using a compound noun, breaking the pattern. The other four tools follow a predictable convention, making this a minor inconsistency.
With 5 tools, the count is borderline for the server's purpose of managing Amazon VPC Lattice prompts and sources. It feels slightly thin, as it covers listing and getting prompts/sources and CLI execution, but might lack operations like creating, updating, or deleting prompts, which could limit functionality. The scope is reasonable but not fully fleshed out.
There are significant gaps in the tool surface for managing Amazon VPC Lattice prompts. The server only provides read operations (get and list) for prompts and sources, along with CLI execution, but lacks create, update, or delete tools. This incomplete CRUD coverage will likely cause agent failures when full lifecycle management is needed, as agents cannot modify or add new prompts or sources.
Related MCP Connectors
The AWS Knowledge MCP server is a fully managed remote Model Context Protocol server that provides real-time access to official AWS content in an LLM-compatible format. It offers structured access to AWS documentation, code samples, blog posts, What's New announcements, Well-Architected best practices, and regional availability information for AWS APIs and CloudFormation resources. Key capabilities include searching and reading documentation in markdown format, getting content recommendations, listing AWS regions, and checking regional availability for services and features.
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yo…
A Model Context Protocol server for Wix AI tools
Enable secure connectivity between Sentry issues and debugging data, and LLM clients, using a Model Context Protocol (MCP) server.
Related MCP Servers
- FlicenseNot gradedqualityNot gradedmaintenanceProvides a scalable, containerized infrastructure for deploying and managing Model Context Protocol servers with monitoring, high availability, and secure configurations.-

Log Analyzer with MCPofficial
AlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that provides AI assistants access to AWS CloudWatch Logs, enabling browsing, searching, summarizing, and correlating logs across multiple AWS services.170Apache 2.0- AlicenseNot gradedqualityNot gradedmaintenanceServes as a Model Context Protocol server that provides tools to look up Amazon Leadership Principles and access video transcripts for integration with Amazon Q CLI.MIT
- AlicenseDqualityDmaintenanceA Model Context Protocol server that enables LLMs to explore and interact with API specifications by providing tools for loading, browsing, and getting detailed information about API endpoints.415 npm14ISC