mcpjungle/MCPJungle

Add separate smoke tests for containerized MCPJungle deployments

Open

#240 opened on May 2, 2026

View on GitHub
 (0 comments) (0 reactions) (0 assignees)Go (146 forks)auto 404
good first issue

Repository metrics

Stars
 (1,162 stars)
PR merge metrics
 (PR metrics pending)

Description

scripts/test-mcpjungle.sh now runs the server from the freshly built local binary so it exercises both the latest client code and the latest server code in the workspace.

Before this, the CLI under test was local but the server under test came from the published GHCR image via docker-compose.yaml, so unpublished server-side changes were not actually covered.

We should add a separate smoke test for the containerized path instead of mixing that concern into the main script.

Future smoke test scope:

  • start MCPJungle from a container image, not the local binary
  • validate the compose/container deployment path
  • cover container-specific behavior such as packaging, env wiring, and filesystem mount assumptions

Contributor guide

Research direction
Tech stack
Domain
Issue type
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Prerequisites
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.