mcpjungle/MCPJungle

cli: allow validating a configuration file

Open

#247 opened on May 4, 2026

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

Repository metrics

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

Description

Direct user feedback.

The cli should allow validating a configuration file the user intends to feed to mcpjungle server.

examples:

mcpjungle validate ./my_server.json

mcpjungle validate ./my_tool_group.json

mcpjungle validate ./new_mcp_client.json

Maybe the user also needs to specify the type of configuration they're validating (mcp server, client, etc) or maybe mcpjungle can infer the type based on certain rules (eg- if url is present, this is probably a http mcp server). Needs to be determined.

The validation logic should be implemented server-side so that the validation feature can be consumed by any client (CLI for now, frontend in future).

This validation logic can also be used by backend during POST / PUT requests.

This should also be mentioned in the docs. Originally, a user was trying to search for this functionality in the docs. So it should be discoverable from there.

Contributor guide

Research direction
Examine the existing CLI structure and server side validation logic. Determine how to add a new 'validate' subcommand that reads a configuration file and validates it using existing server logic. Consider whether to infer config type or require explicit flag.
Tech stack
go
Domain
clibackend
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
GoCLI development
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60