Skip to main content
Once an MCP server is registered, Mcpjungle tracks what it exposes and lets you manage that surface area without removing the server itself. This page covers:
  • listing tools and prompts
  • checking tool usage (input schema)
  • invoking tools
  • retrieving prompts
  • enabling and disabling tools, prompts, and entire servers

​
Tools

Every tool is identified by a canonical name:
See core concepts for more details on names.

​
List available tools

To scope the list to a specific server:
To scope the list to a Tool Group:

​
Inspect tool usage

This shows the tool schema and expected input shape.

​
Invoke a tool

Ideally, tools will be invoked by your MCP clients through the gateway. The CLI allows you to invoke tools directly for testing and debugging.
You can also invoke through a Tool Group context:

​
Prompts

Mcpjungle supports MCP Prompts. If a registered server exposes prompts, Mcpjungle registers them alongside that server’s tools. Prompt names follow the same canonical pattern:

​
List prompts

​
Retrieve a prompt with arguments

As with tools, prompts will also be read by your MCP clients. Use the CLI to retrieve prompts directly for testing and debugging:
Pass one --arg key=value flag per prompt argument.

​
Enable and disable exposure

Mcpjungle lets you hide tools and prompts from clients without deleting the underlying server registration. When you disable something:
  • it disappears from gateway discovery
  • MCP clients cannot call it through Mcpjungle
  • you can still manage it through the CLI and API
All tools and prompts are enabled by default when a server is first registered.

​
Disable or re-enable a single tool

​
Disable or re-enable all tools from one server

​
Disable or re-enable an entire server

Disabling a server disables all of its tools, prompts and resources in one step:

​
Disable or re-enable prompts

​
How disabled entities behave

​
Operational notes

  • Disabling a server or tool does not remove its registration.
  • Deregister a server if you want to remove it permanently.

Tool groups

Expose subsets of tools through dedicated MCP endpoints.

Register servers

Add new streamable HTTP MCP servers to the gateway.

STDIO servers

Register local process-based MCP servers.

Limitations

Review the current gaps, including prompt support in Tool Groups.