Is your improvement proposal related to a problem? Please describe.
Currently, debugging automated end-to-end (e2e) test failures requires manual intervention to download debug logs bundled as build artifacts. While users leverage AI assistants via the Model Context Protocol (MCP) to streamline debugging workflows, the current Semaphore MCP server and CLI do not support the programmatic retrieval of these artifacts.
There are currently no public API endpoints available to generate external download links for artifacts outside of active Semaphore jobs. This limitation prevents LLMs and other automated tools from accessing necessary log data to perform autonomous root-cause analysis.
Describe the solution you'd like
TBD
Describe alternatives you've considered
No response
Additional context
No response
Is your improvement proposal related to a problem? Please describe.
Currently, debugging automated end-to-end (e2e) test failures requires manual intervention to download debug logs bundled as build artifacts. While users leverage AI assistants via the Model Context Protocol (MCP) to streamline debugging workflows, the current Semaphore MCP server and CLI do not support the programmatic retrieval of these artifacts.
There are currently no public API endpoints available to generate external download links for artifacts outside of active Semaphore jobs. This limitation prevents LLMs and other automated tools from accessing necessary log data to perform autonomous root-cause analysis.
Describe the solution you'd like
TBD
Describe alternatives you've considered
No response
Additional context
No response