awslabs.memcached-mcp-server 0.1.1__tar.gz → 1.0.0__tar.gz

{awslabs_memcached_mcp_server-0.1.1 → awslabs_memcached_mcp_server-1.0.0}/Dockerfile

@@ -10,7 +10,7 @@
 # and limitations under the License.
 
 #FROM public.ecr.aws/sam/build-python3.10:1.137.1-20250411084548
-FROM public.ecr.aws/sam/build-python3.10@sha256:04cdbe84bec08d17d621192bc3f0a9e4a85a83f2ac99aa9241659dfac0d845ea AS uv
+FROM public.ecr.aws/sam/build-python3.10@sha256:e78695db10ca8cb129e59e30f7dc9789b0dbd0181dba195d68419c72bac51ac1 AS uv
 
 # Install the project into `/app`
 WORKDIR /app
@@ -44,7 +44,7 @@ RUN --mount=type=cache,target=/root/.cache/uv \
 # Make the directory just in case it doesn't exist
 RUN mkdir -p /root/.local
 
-FROM public.ecr.aws/sam/build-python3.10@sha256:04cdbe84bec08d17d621192bc3f0a9e4a85a83f2ac99aa9241659dfac0d845ea
+FROM public.ecr.aws/sam/build-python3.10@sha256:e78695db10ca8cb129e59e30f7dc9789b0dbd0181dba195d68419c72bac51ac1
 
 # Place executables in the environment at the front of the path and include other binaries
 ENV PATH="/app/.venv/bin:$PATH:/usr/sbin"

awslabs_memcached_mcp_server-1.0.0/ELASTICACHECONNECT.md

@@ -0,0 +1,97 @@
+# How to connect to an Amazon ElastiCache Memcached cache
+
+Your Amazon ElastiCache instances are designed to be accessed through an Amazon EC2 instance. You can access your ElastiCache instance from an Amazon EC2 instance in the same Amazon VPC, or by using VPC peering, you can access your ElastiCache instance from an Amazon EC2 in a different Amazon VPC.
+
+The following instructions will help you create an EC2 instance in the same VPC as your cache instance, and will guide you to configure the security groups required to access the cache from your desktop through an SSH tunnel.
+
+## Launch and configure the EC2 instance
+
+Complete the following steps:
+
+1. Open the Amazon EC2 console, and then choose Launch instance.
+2. Select an Amazon Machine Image (AMI).
+3. Choose an instance type, and then choose Next: Configure Instance Details.
+4. For Network, choose the VPC that the Amazon ElastiCache Valkey cache uses.
+5. For Subnet, select the private subnet in the VPC
+6. Choose Next: Add Storage, and then modify the storage as needed.
+7. Choose Next: Add Tags, and then add tags as needed.
+8. Choose Next: Configure Security Group.
+9. Choose Add Rule, and then enter the following:
+    * For Type, enter Custom TCP Rule
+    * For Protocol, enter TCP
+    * For Port Range, enter 22
+    * For Source, enter the security group used by your Amazon EC2 connect endpoint.
+10. Choose Review and Launch, and then choose Launch.
+
+## Configure the Amazon ElastiCache Memcached Cache’s security groups
+
+Complete the following steps:
+
+1. Open the Amazon ElastiCache console.
+2. In the navigation pane, choose Resources → Memcached caches.
+3. Choose the name of the Amazon Memcached Cache. If you don't already have one, then create it.
+4. Choose Connectivity & security.
+5. From the Security section, choose the link under VPC security groups.
+6. Select the security group, choose Actions, and then choose Edit inbound rules.
+7. Choose Add rule, and then enter the following:
+   - For Type, enter Custom TCP Rule
+   - For Protocol, enter TCP
+   - For Port Range, enter the port of your Amazon ElastiCache Memcached cache (11211).
+   - For Source, enter the private IP address of your EC2 instance.
+8. Choose Save.
+
+This configuration for the security group allows traffic from the EC2 instance's private IP address. If the EC2 instance and the Amazon ElastiCache Memcached cache use the same VPC, then you don't need to modify the Amazon ElastiCache Memcached cache route table. If the VPC is different, then create a VPC peering connection to allow connections between those VPCs.
+Note: If you use a more scalable solution, then review your configuration. For example, if you use the security group ID in a security group rule, then make sure that it doesn't restrict access to one instance. Instead, configure the rule to restrict access to any resource that uses the specific security group ID.
+
+## Create an EC2 instance connect endpoint
+
+1. Open the Amazon VPC console.
+2. In the navigation pane, choose Endpoints.
+3. Choose Create endpoint, and then specify the endpoint settings.
+    * (Optional) For Name tag, enter a name for the endpoint.
+    * For Service category, choose EC2 Instance Connect Endpoint.
+    * For VPC, select the VPC that has the target instances.
+    * (Optional) To preserve client IP addresses, expand Additional settings and select the check box. Otherwise, the default is to use the endpoint network interface as the client IP address.
+    * For Security groups, select the security group you want to associate with the endpoint. Otherwise, the default is to use the default security group for the VPC.
+    * For Subnet, select the subnet in which to create the endpoint.
+    * (Optional) To add a tag, choose Add new tag and enter the tag key and the tag value.
+4. Review your settings and then choose Create endpoint.
+5. The initial status of the endpoint is Pending. To connect to an instance, you must wait until the endpoint status is Available. This can take up to a few minutes.
+
+## Connect to the ElastiCache Memcached cache from your local machine
+
+**Note**: You must have access to the AWS CLI.
+
+To connect from your local MCP Server to a private Amazon ElastiCache Memcached cache through an SSH tunnel, complete the following steps:
+Linux or macOS
+Run the following command to open a tunnel from local machine to the EC2 instance:
+
+```
+aws ec2-instance-connect open-tunnel --instance-id ec2-instance-ID --local-port 11211
+```
+
+**Note**: Replace ec2-instance-ID with your EC2 instance ID.
+
+Open a second connection and run the following command to create an SSH tunnel from your local host to your ElastiCache Valkey Cache through an EC2 instance:
+
+```
+ssh -i YOUR_EC2_KEY EC2_USER@EC2_HOST -p EC2_TUNNEL_PORT -L LOCAL_PORT:ELASTICACHE_ENDPOINT:REMOTE_PORT -N -f
+```
+
+**Note**: Replace the following values:
+* **YOUR_EC2_KEY** with the path to your EC2 private key file
+* **EC2_USER** with your EC2 instance username
+* **EC2_HOST** with the hostname of your EC2 instance
+* **EC2_TUNNEL_PORT** with the port you configured
+* **LOCAL_PORT** with an unused port on your local machine (11211)
+* **ELASTICACHE_ENDPOINT** with the endpoint of your ElastiCache Memcached cache
+* **REMOTE_PORT** with the port that your Amazon ElastiCache Memcached cache uses (11211)
+
+Use a third connection and run the following command to verify connection to your Amazon ElastiCache Memcached cache from your local machine:
+
+```
+telnet 127.0.0.1 LOCAL_PORT
+```
+
+**Note**: Replace the following values:
+* **LOCAL_PORT** with the number of your local port (11211)

{awslabs_memcached_mcp_server-0.1.1 → awslabs_memcached_mcp_server-1.0.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: awslabs.memcached-mcp-server
-Version: 0.1.1
+Version: 1.0.0
 Summary: An AWS Labs Model Context Protocol (MCP) server for Amazon ElastiCache Memcached
 Project-URL: homepage, https://awslabs.github.io/mcp/
 Project-URL: docs, https://awslabs.github.io/mcp/servers/memcached-mcp-server/
@@ -28,7 +28,7 @@ Requires-Dist: pymemcache>=4.0.0
 Requires-Dist: python-dotenv>=0.9.9
 Description-Content-Type: text/markdown
 
-# Memcached MCP Server
+# Amazon ElastiCache Memcached MCP Server
 
 MCP server for interacting with Amazon ElastiCache Memcached through a secure and reliable connection
 
@@ -41,27 +41,13 @@ MCP server for interacting with Amazon ElastiCache Memcached through a secure an
 - Automatic connection management and pooling
 - Built-in retry mechanism for failed operations
 
-### Robust Connection Management
-
-- Configurable connection settings and timeouts
-- Automatic connection retrying with customizable parameters
-- Connection pooling for improved performance
-- Comprehensive error handling and recovery
-
-### Security and Reliability
-
-- SSL/TLS support for encrypted communication
-- Certificate-based authentication
-- Configurable verification settings
-- Automatic handling of connection failures
-
 ## Prerequisites
 
 1. Install `uv` from [Astral](https://docs.astral.sh/uv/getting-started/installation/) or the [GitHub README](https://github.com/astral-sh/uv#installation)
 2. Install Python using `uv python install 3.10`
-3. Access to a Memcached server (local or Amazon ElastiCache)
-   - For Amazon ElastiCache, you need appropriate AWS credentials and permissions
-   - For local development, ensure Memcached is installed and running
+3. Access to a Memcached server.
+4. For instructions to connect to an Amazon ElastiCache Memcached cache [click here](https://github.com/awslabs/mcp/blob/main/src/memcached-mcp-server/ELASTICACHECONNECT.md)
+
 
 ## Installation
 
@@ -146,3 +132,26 @@ The server automatically handles:
 - SSL/TLS encryption when enabled
 - Automatic retrying of failed operations
 - Timeout enforcement and error handling
+
+## Development
+
+### Running Tests
+```bash
+uv venv
+source .venv/bin/activate
+uv sync
+uv run --frozen pytest
+```
+
+### Building Docker Image
+```bash
+docker build -t awslabs/memcached-mcp-server .
+```
+
+### Running Docker Container
+```bash
+docker run -p 8080:8080 \
+  -e MEMCACHED_HOST=host.docker.internal \
+  -e MEMCACHED_PORT=11211 \
+  awslabs/memcached-mcp-server
+```

{awslabs_memcached_mcp_server-0.1.1 → awslabs_memcached_mcp_server-1.0.0}/README.md

@@ -1,4 +1,4 @@
-# Memcached MCP Server
+# Amazon ElastiCache Memcached MCP Server
 
 MCP server for interacting with Amazon ElastiCache Memcached through a secure and reliable connection
 
@@ -11,27 +11,13 @@ MCP server for interacting with Amazon ElastiCache Memcached through a secure an
 - Automatic connection management and pooling
 - Built-in retry mechanism for failed operations
 
-### Robust Connection Management
-
-- Configurable connection settings and timeouts
-- Automatic connection retrying with customizable parameters
-- Connection pooling for improved performance
-- Comprehensive error handling and recovery
-
-### Security and Reliability
-
-- SSL/TLS support for encrypted communication
-- Certificate-based authentication
-- Configurable verification settings
-- Automatic handling of connection failures
-
 ## Prerequisites
 
 1. Install `uv` from [Astral](https://docs.astral.sh/uv/getting-started/installation/) or the [GitHub README](https://github.com/astral-sh/uv#installation)
 2. Install Python using `uv python install 3.10`
-3. Access to a Memcached server (local or Amazon ElastiCache)
-   - For Amazon ElastiCache, you need appropriate AWS credentials and permissions
-   - For local development, ensure Memcached is installed and running
+3. Access to a Memcached server.
+4. For instructions to connect to an Amazon ElastiCache Memcached cache [click here](https://github.com/awslabs/mcp/blob/main/src/memcached-mcp-server/ELASTICACHECONNECT.md)
+
 
 ## Installation
 
@@ -116,3 +102,26 @@ The server automatically handles:
 - SSL/TLS encryption when enabled
 - Automatic retrying of failed operations
 - Timeout enforcement and error handling
+
+## Development
+
+### Running Tests
+```bash
+uv venv
+source .venv/bin/activate
+uv sync
+uv run --frozen pytest
+```
+
+### Building Docker Image
+```bash
+docker build -t awslabs/memcached-mcp-server .
+```
+
+### Running Docker Container
+```bash
+docker run -p 8080:8080 \
+  -e MEMCACHED_HOST=host.docker.internal \
+  -e MEMCACHED_PORT=11211 \
+  awslabs/memcached-mcp-server
+```

{awslabs_memcached_mcp_server-0.1.1 → awslabs_memcached_mcp_server-1.0.0}/awslabs/memcached_mcp_server/main.py

@@ -11,7 +11,6 @@
 
 """awslabs memcached MCP Server implementation."""
 
-import argparse
 from awslabs.memcached_mcp_server.common.server import mcp
 from awslabs.memcached_mcp_server.tools import cache  # noqa: F401
 from loguru import logger
@@ -32,35 +31,15 @@ async def health_check(request):
 class MemcachedMCPServer:
     """Memcached MCP Server wrapper."""
 
-    def __init__(self, sse=False, port=None):
-        """Initialize MCP Server wrapper."""
-        self.sse = sse
-        self.port = port
-
     def run(self):
         """Run server with appropriate transport."""
-        if self.sse:
-            mcp.settings.port = int(self.port) if self.port is not None else 8888
-            mcp.run(transport='sse')
-        else:
-            mcp.run()
+        mcp.run()
 
 
 def main():
     """Run the MCP server with CLI argument support."""
-    parser = argparse.ArgumentParser(
-        description='An AWS Labs Model Context Protocol (MCP) server for Amazon ElastiCache Memcached'
-    )
-    parser.add_argument('--sse', action='store_true', help='Use SSE transport')
-    parser.add_argument('--port', type=int, default=8888, help='Port to run the server on')
-
-    args = parser.parse_args()
-
     logger.info('Amazon ElastiCache Memcached MCP Server Started...')
-
-    # Run server with appropriate transport
-    server = MemcachedMCPServer(args.sse, args.port)
-    server.run()
+    MemcachedMCPServer().run()
 
 
 if __name__ == '__main__':

{awslabs_memcached_mcp_server-0.1.1 → awslabs_memcached_mcp_server-1.0.0}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "awslabs.memcached-mcp-server"
-version = "0.1.1"
+version = "1.0.0"
 description = "An AWS Labs Model Context Protocol (MCP) server for Amazon ElastiCache Memcached"
 readme = "README.md"
 requires-python = ">=3.10"
@@ -37,7 +37,7 @@ repository = "https://github.com/awslabs/mcp.git"
 changelog = "https://github.com/awslabs/mcp/blob/main/src/memcached-mcp-server/CHANGELOG.md"
 
 [project.scripts]
-"awslabs.memcached-mcp-server" = "awslabs.memcached_mcp_server.server:main"
+"awslabs.memcached-mcp-server" = "awslabs.memcached_mcp_server.main:main"
 
 [dependency-groups]
 dev = [

{awslabs_memcached_mcp_server-0.1.1 → awslabs_memcached_mcp_server-1.0.0}/tests/test_main.py

@@ -26,23 +26,6 @@ class TestMain:
 
         # Check that mcp.run was called with the correct arguments
         mock_run.assert_called_once()
-        assert mock_run.call_args[1].get('transport') is None
-
-    @patch('awslabs.memcached_mcp_server.common.server.mcp.run')
-    @patch('sys.argv', ['awslabs.memcached-mcp-server', '--sse', '--port', '9999'])
-    def test_main_sse(self, mock_run):
-        """Test main function with SSE transport."""
-        # Call the main function
-        main()
-
-        # Check that mcp.run was called with the correct arguments
-        mock_run.assert_called_once()
-        assert mock_run.call_args[1].get('transport') == 'sse'
-
-        # Check that the port was set correctly
-        from awslabs.memcached_mcp_server.main import mcp
-
-        assert mcp.settings.port == 9999
 
     def test_module_execution(self):
         """Test the module execution when run as __main__."""