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

{awslabs_valkey_mcp_server-0.1.1 → awslabs_valkey_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_valkey_mcp_server-0.1.1 → awslabs_valkey_mcp_server-1.0.0}/ELASTICACHECONNECT.md

@@ -1,5 +1,9 @@
 # How to connect to an Amazon ElastiCache Valkey datastore
 
+Your Amazon ElastiCache for Valkey datastores are designed to be accessed through an Amazon EC2 instance. You can access your ElastiCache for Valkey datastores from an Amazon EC2 instance in the same Amazon VPC, or by using VPC peering, you can access your ElastiCache for Valkey datastores 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 ElastiCache for Valkey datastore, 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:

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

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: awslabs.valkey-mcp-server
-Version: 0.1.1
+Version: 1.0.0
 Summary: An AWS Labs Model Context Protocol (MCP) server for valkey
 Project-URL: homepage, https://awslabs.github.io/mcp/
 Project-URL: docs, https://awslabs.github.io/mcp/servers/valkey-mcp-server/
@@ -55,7 +55,8 @@ This MCP server provides tools to operate on Valkey data types. For example, it
 
 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 Valkey datastore instance. For instructions to connect to an Amazon ElastiCache/MemoryDB Valkey cache [click here](ELASTICACHECONNECT.md).
+3. Access to a Valkey datastore.
+4. For instructions to connect to an Amazon ElastiCache/MemoryDB Valkey datastore [click here](https://github.com/awslabs/mcp/blob/main/src/valkey-mcp-server/ELASTICACHECONNECT.md).
 
 
 ## Installation

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

@@ -24,7 +24,8 @@ This MCP server provides tools to operate on Valkey data types. For example, it
 
 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 Valkey datastore instance. For instructions to connect to an Amazon ElastiCache/MemoryDB Valkey cache [click here](ELASTICACHECONNECT.md).
+3. Access to a Valkey datastore.
+4. For instructions to connect to an Amazon ElastiCache/MemoryDB Valkey datastore [click here](https://github.com/awslabs/mcp/blob/main/src/valkey-mcp-server/ELASTICACHECONNECT.md).
 
 
 ## Installation

{awslabs_valkey_mcp_server-0.1.1 → awslabs_valkey_mcp_server-1.0.0}/awslabs/valkey_mcp_server/main.py

@@ -11,7 +11,6 @@
 
 """awslabs valkey MCP Server implementation."""
 
-import argparse
 from awslabs.valkey_mcp_server.common.server import mcp
 from awslabs.valkey_mcp_server.tools import (
     bitmap,  # noqa: F401
@@ -44,39 +43,19 @@ async def health_check(request):
 class ValkeyMCPServer:
     """Valkey MCP Server wrapper."""
 
-    def __init__(self, sse=False, port=8888):
-        """Initialize MCP Server wrapper.
-
-        Args:
-            sse: Whether to use SSE transport
-            port: Port to run the server on (default: 8888)
-        """
-        self.sse = sse
-        self.port = port
+    def __init__(self):
+        """Initialize MCP Server wrapper."""
 
     def run(self):
         """Run server with appropriate transport."""
-        if self.sse:
-            if self.port is not None:
-                mcp.settings.port = self.port
-            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 valkey'
-    )
-    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/MemoryDB Valkey MCP Server Started...')
 
-    server = ValkeyMCPServer(args.sse, args.port)
+    server = ValkeyMCPServer()
     server.run()
 
 

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

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

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

@@ -19,7 +19,6 @@ class TestMain:
     """Tests for the main function."""
 
     @patch('awslabs.valkey_mcp_server.common.server.mcp.run')
-    @patch('sys.argv', ['awslabs.valkey-mcp-server'])
     def test_main_default(self, mock_run):
         """Test main function with default arguments."""
         # Call the main function
@@ -28,23 +27,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.valkey_mcp_server.common.server.mcp.run')
-    @patch('sys.argv', ['awslabs.valkey-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.valkey_mcp_server.common.server import mcp
-
-        assert mcp.settings.port == 9999
 
     def test_module_execution(self):
         """Test the module execution when run as __main__."""