From f9e9851fc94568900df40d5baaa6d1914104dcb6 Mon Sep 17 00:00:00 2001 From: Rudy Celekli Date: Mon, 19 Oct 2026 15:22:56 -0400 Subject: [PATCH] docs(detection): use a workspace-relative path in the local server example main_benchmark.py writes each task's .mcp.json into benchmark/adr_bench_*/task_XXX/workspace/ and runs claude from there, so a server script path relative to Detection/ does not exist from the server's working directory. The README example registered "context_providers/source_codes/..." and the server would fail to start. Use the "../../../../" prefix that every local entry in mcp_servers_registry.json uses, and say why. Co-Authored-By: Claude Opus 5.5 --- Detection/README.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/Detection/README.md b/Detection/README.md index f8a57970..dbdbb260 100644 --- a/Detection/README.md +++ b/Detection/README.md @@ -470,7 +470,7 @@ if __name__ == "__main__": "command": "uv", "args_template": [ "run", "fastmcp", "run", - "context_providers/source_codes/mcp_servers_0/your_server/your_server.py" + "../../../../context_providers/source_codes/mcp_servers_0/your_server/your_server.py" ], "capabilities": ["your_function"], "verified": true @@ -478,6 +478,10 @@ if __name__ == "__main__": } ``` + The benchmark starts each server from the task workspace + (`benchmark/adr_bench_*/task_XXX/workspace/`), so the script path must be + relative to that directory, as in the existing registry entries. + 1. **Test your server**: ```bash