mcpjungle/MCPJungle

Provide configurations for popular MCP Servers

Open

#79 opened on Aug 27, 2025

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

Repository metrics

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

Description

# user manually writes configuration in my-mcp-server.json

# then registers the mcp in mcpjungle
mcpjungle register -c my-mcp-server.json

The documentation should already provide configurations for popular mcp servers. The user shouldn't have to write a configuration for it themselves. They can just pick it up from docs or something like an examples directory and use it to register the mcp server.

This saves them time & effort in writing server configs to register servers and improves UX.

Popular mcp servers:

  • time
  • context7
  • huggingface
  • stripe
  • deepwiki
  • github
  • ?

An evolution of this would be to introduce the install command in mcpjungle CLI, which automatically registers a popular mcp server without the user having to provide any config at all. eg-

mcpjungle install time

This doesn't work if the user needs to provide some custom configuration to an mcp server, like auth tokens, env vars, etc.

Contributor guide

Research direction
Explore the existing codebase to understand how server configurations are currently handled. Create a set of predefined configuration files for popular MCP servers like time, context7, huggingface, stripe, deepwiki, github, etc. Place them in an 'examples' directory or similar. Then, implement a new 'install' CLI command that allows users to automatically register a server from these predefined configs without needing to write a config file. For servers requiring custom input (e.g., auth tokens), provide a mechanism for the user to supply those values interactively or via flags. Ensure the new command follows the existing CLI patterns and passes tests.
Tech stack
go
Domain
backendcli
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
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.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitGo
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70