Skip to main content
This roadmap explains where mcpjungle is heading over the next few months. In short, our focus is to:
  1. Keep mcpjungle extremely simple & useful for developers
  2. Remove the biggest blockers to real MCP usage
  3. Add collaborative capabilities for teams

​
Here’s what’s coming next

​
1. OAuth Support

This is the highest-priority area. MCP servers requiring OAuth authentication are now supported. This is a beta feature right now. We are still working on:
  • downstream client OAuth, SSO, and OIDC
  • smoother handling of stored credentials and token refresh flows

​
2. Better configuration-driven workflows, Infrastructure as Code, and GitOps support

We want mcpjungle to be easier to operate repeatedly, not just easy to try once. We are working on:
  • declarative configuration for managed entities
  • config-driven reconciliation at startup
  • live reload for supported config changes
  • a more GitOps-friendly workflow for operators managing shared setups

​
3. Dashboard UI expansion

The Dashboard UI is now available in Beta for local/dev visibility and common management tasks. We are continuing to expand it as a practical companion to the mcpjungle CLI.

​
4. Better access control in enterprise mode

Once core usability is stronger, we plan to add more targeted control features for team scenarios. Near-term areas include:
  • per-client credentials
  • more fine-grained ACLs

​
How we make roadmap decisions

We use a simple prioritization model:
  1. Unblock real usage
  2. Reduce setup and operational friction
  3. Improve visibility
  4. Add focused control where teams actually need it

​
Have feedback?

If you are using mcpjungle and want to influence the roadmap, come Talk to us. The roadmap will continue to evolve based on real usage and direct user feedback.