simplify dockerfile, add agents test suite, nginx can now take a hostname, other cleanup

Author: aarora79

.gitignore

@@ -182,3 +182,4 @@ cookies.txt
 registry/server_state.json
 registry/nginx_mcp_revproxy.conf
 logs/
+agents/test_results/

Dockerfile

@@ -21,37 +21,7 @@ RUN apt-get update && apt-get install -y --no-install-recommends \
 # Set the working directory in the container
 WORKDIR /app
 
-# Copy dependency files first to leverage Docker cache
-COPY pyproject.toml uv.lock /app/
-
-# Create the shared virtual environment that start_all_servers.sh will use
-RUN pip install uv
-RUN uv venv /app/.venv --python 3.12
-
-# Install dependencies directly from pyproject.toml
-# This installs all dependencies without requiring the actual package code
-RUN . /app/.venv/bin/activate && uv pip install \
-    "fastapi>=0.115.12" \
-    "itsdangerous>=2.2.0" \
-    "jinja2>=3.1.6" \
-    "mcp>=1.6.0" \
-    "pydantic>=2.11.3" \
-    "httpx>=0.27.0" \
-    "python-dotenv>=1.1.0" \
-    "python-multipart>=0.0.20" \
-    "uvicorn[standard]>=0.34.2" \
-    "faiss-cpu>=1.7.4" \
-    "sentence-transformers>=2.2.2" \
-    "websockets>=15.0.1" \
-    "scikit-learn>=1.3.0" \
-    "torch>=1.6.0" \
-    "huggingface-hub[cli]>=0.31.1" \
-    "pyjwt[crypto]>=2.8.0" \
-    "pycognito>=2024.3.1" \
-    "boto3>=1.28.0" \
-    "requests>=2.32.3"
-
-# Copy the rest of the application
+# Copy the application code
 COPY . /app/
 
 # Copy the custom Nginx configuration (will be moved by entrypoint)

README.md

@@ -182,12 +182,14 @@ The Gateway and the Registry are available as a Docker container. The package in
     export ADMIN_USER=admin
     export ADMIN_PASSWORD=your-admin-password
     export POLYGON_API_KEY=your-polygon-api-key
+    export GATEWAY_HOSTNAME=your-ec2-hostname
     # stop any previous instance
     docker stop mcp-gateway-container && docker rm mcp-gateway-container 
     docker run -p 80:80 -p 443:443 -p 7860:7860 \
     -e ADMIN_USER=$ADMIN_USER \
     -e ADMIN_PASSWORD=$ADMIN_PASSWORD \
     -e POLYGON_API_KEY=$POLYGON_API_KEY \
+    -e GATEWAY_HOSTNAME=$GATEWAY_HOSTNAME \
     -e SECRET_KEY=$(python3 -c 'import secrets; print(secrets.token_hex(32))') \
     -v /var/log/mcp-gateway:/app/logs \
     -v /opt/mcp-gateway/servers:/app/registry/servers \
@@ -231,6 +233,19 @@ The Gateway and the Registry are available as a Docker container. The package in
 1. **View MCP server metadata:**
    Metadata about all MCP servers connected to the Registry is available in `/opt/mcp-gateway/servers` directory. The metadata includes information gathered from `ListTools` as well as information provided while registering the server.
 
+   ```{.python}
+   python agents\agent.py --mcp-registry-url http://localhost/mcpgw/sse --message "what is the current time in clarksburg, md"
+   ```
+
+   You can also run the full test suite and get a handy agent evaluation report. This test suite exercises the Registry functionality as well as tests the multiple built-in MCP servers provided by the Gateway.
+   ```{python}
+   python agents\test_suite.py
+   ```
+   The result of the tests suites are available in the `agents/test_results` folder. It contains an `accuracy.json`, a `summary.json`, a `logs` folder and a `raw_data` folder that contains the verbose output from the agent. The test suite uses an LLM as a judge to evaluate the results for accuracy and tool usage quality.
+
+1. **Test the Gateway and Registry with the sample Agent and test suite**
+   The repo includes a test agent that can connect to the Registry to discover tools and invoke them to do interesting tasks. This functionality can be invoked either standalone or as part of a test suite.
+
 #### Running the Gateway over HTTPS
 
 1. Enable access to TCP port 443 from the IP address of your MCP client (your laptop, or anywhere) in the inbound rules in the security group associated with your EC2 instance.
@@ -246,6 +261,7 @@ The Gateway and the Registry are available as a Docker container. The package in
       -e ADMIN_USER=$ADMIN_USER \
       -e ADMIN_PASSWORD=$ADMIN_PASSWORD \
       -e POLYGON_API_KEY=$POLYGON_API_KEY \
+      -e GATEWAY_HOSTNAME=$GATEWAY_HOSTNAME \
       -e SECRET_KEY=$(python3 -c 'import secrets; print(secrets.token_hex(32))') \
       -v /path/to/certs:/etc/ssl/certs \
       -v /path/to/private:/etc/ssl/private \

agents/agent.py

@@ -172,7 +172,7 @@ async def invoke_mcp_tool(mcp_registry_url: str, server_name: str, tool_name: st
 
 How to use intelligent_tool_finder:
 1. When you identify that a task requires a specialized tool (e.g., image generation, specialized API access, etc.)
-2. Call the tool with a description of what you need: `intelligent_tool_finder("description of needed capability")`, Use admin/password for authentication.
+2. Call the tool with a description of what you need: `intelligent_tool_finder("description of needed capability")`
 3. The tool will return the most appropriate specialized tool along with usage instructions
 4. You can then use the invoke_mcp_tool to invoke this discovered tool by providing the MCP Registry URL, server name, tool name, and required arguments