Skip to main content
This page summarizes the current support level across the major Mcpjungle capability areas. Use it as a quick product-readiness view:
  • Stable: supported and appropriate for normal use
  • Beta: usable, but still maturing
  • Limited: supported only partially or with important constraints

Transports

AreaCapabilitySupport levelNotes
Upstream MCP serversStreamable HTTPStablePrimary remote transport for registering MCP servers in Mcpjungle.
Upstream MCP serversSTDIOStableSupported through config-file registration and local child-process execution.
Upstream MCP serversSSELimitedSSE is supported but no longer recommended as it is a deprecated transport.
Client connection to McpjungleStreamable HTTP endpointStableMain gateway endpoint exposed at /mcp.

MCP surface area

AreaCapabilitySupport levelNotes
MCP entitiesToolsStableCore Mcpjungle workflow. Tools can be listed, invoked, enabled, disabled, and grouped.
MCP entitiesPromptsStablePrompts are supported and can be listed, retrieved, enabled, and disabled.
MCP entitiesResourcesBetaSome features such as tool groups may not fully support Resources yet.
Group endpointsTool GroupsStableMain mechanism for exposing curated subsets of tools to specific clients.

Authentication and access control

AreaCapabilitySupport levelNotes
Upstream HTTP serversStatic bearer-token authStableSupported via --bearer-token or JSON config.
Upstream HTTP serversCustom headersStableSupported through the headers field in config files.
Upstream HTTP serversOAuth flowNot supportedThis is currently being worked on and will be available soon.
Mcpjungle gatewayEnterprise-mode client authenticationStableMCP clients authenticate with bearer tokens in enterprise mode.
Mcpjungle gatewayPer-client server allow-listsStableSupported through MCP client creation in enterprise mode.
Mcpjungle gatewayUser accountsStableSupported for human operators in enterprise mode.

Deployment and runtime

AreaCapabilitySupport levelNotes
Local deploymentDevelopment modeStableIntended for individuals using Mcpjungle locally.
Shared deploymentEnterprise modeStableIntended for teams and shared infrastructure.
DatabaseSQLiteStableGood default for local testing and single-user workflows.
DatabasePostgreSQLStableRecommended for serious and shared deployments.
Session lifecycleStateless sessionsStableDefault and preferred mode.
Session lifecycleStateful sessionsStableSupported for cold-start-sensitive or sessionful upstream servers.

Observability and operations

AreaCapabilitySupport levelNotes
MetricsPrometheus-compatible OpenTelemetry metricsStableEnabled by default in enterprise mode and available at /metrics.
MetricsOTLP exportNot supportedMcpjungle does not currently export metrics through OTLP.
Audit LogsDetailed audit logs for mcp interactionsLimitedThis will be improved in future.

Clients

AreaCapabilitySupport levelNotes
Mcpjungle clientCLIStablePrimary management interface for registering servers, managing groups, and operating Mcpjungle today.
Mcpjungle clientWeb-based GUINot supportedIn active development and planned for release soon.

Core concepts

Understand the Mcpjungle operating model behind the matrix.

Limitations

Review the current gaps and constraints in more detail.

Governance overview

Understand the enterprise operating model for shared deployments.

Reference

Dive into exact commands, config files, and environment variables.