Skip to main content
MCP servers using the Streamable HTTP transport can be added to Mcpjungle. Once registered, a server’s tools, prompts, and resources are available to any MCP client that connects to mcpjungle mcp endpoint.

​
Register a server with CLI flags

The quickest way to register a Streamable HTTP server is with the register command and inline flags: 
mcpjungle register --name context7 --url https://mcp.context7.com/mcp
Here’s an example of adding a custom MCP server running on your local machine 
mcpjungle register --name calculator --description "Provides some basic math tools" --url http://127.0.0.1:5000/mcp
If Mcpjungle is running inside Docker on macOS or Windows, the container cannot reach 127.0.0.1 on your host. Use host.docker.internal instead:
mcpjungle register --name calculator --description "Provides some basic math tools" --url http://host.docker.internal:5000/mcp

​
Register a server from a config file

For servers that need authentication or custom headers — or when you want to keep registration configs in version control — use a JSON config file: 
mcpjungle register -c ./deepwiki.json
The full config file format for a Streamable HTTP server is: 
{
  "name": "deepwiki",
  "transport": "streamable_http",
  "description": "Deepwiki MCP Server",
  "url": "https://mcp.deepwiki.com/mcp",
  "bearer_token": "<optional bearer token>",
  "session_mode": "stateless",
  "headers": {
    "<custom-header>": "<value>"
  }
}
FieldRequiredDescription
nameYesUnique identifier for this server. No spaces, special characters, or consecutive underscores.
transportYesMust be "streamable_http". Other possible values are "sse" and "stdio".
descriptionNoHuman-readable description surfaced in the CLI and API.
urlYesThe full URL of the MCP server’s endpoint (e.g., https://example.com/mcp). Required when transport is streamable http.
bearer_tokenNoIf set, Mcpjungle adds Authorization: Bearer <token> to every request to this server.
session_modeNostateless (default) creates a new connection per tool call. stateful reuses a persistent session across tool calls.
headersNoMap of additional HTTP headers to forward. If Authorization is set here, it overrides bearer_token.

​
Authenticating with a bearer token

Many SaaS-hosted MCP servers require a static API token. Pass it with the --bearer-token flag: 
mcpjungle register \
  --name huggingface \
  --description "HuggingFace MCP Server" \
  --url https://huggingface.co/mcp \
  --bearer-token <your-hf-api-token>
Or include it in the config file: 
{
  "name": "huggingface",
  "transport": "streamable_http",
  "description": "HuggingFace MCP Server",
  "url": "https://huggingface.co/mcp",
  "bearer_token": "<your-hf-api-token>"
}
For servers that need a custom Authorization format or additional headers, use the headers field directly: 
{
  "name": "sourcegraph",
  "transport": "streamable_http",
  "url": "https://sourcegraph.mycompany.com/.api/mcp",
  "headers": {
    "Authorization": "token <your-sourcegraph-token>",
    "X-Custom-Header": "custom-value"
  }
}

​
Environment variable substitution

JSON config files support ${VAR_NAME} placeholders in string fields, including URLs, bearer tokens, and header values. See the configuration file reference for the exact substitution rules and examples.

​
Verify the registration

After registering a server, inspect what Mcpjungle discovered: 
mcpjungle list tools

# get the usage schema of a tool
mcpjungle usage deepwiki__read_wiki_structure

# call a tool from cli
mcpjungle invoke deepwiki__read_wiki_structure --input '{"repoName": "facebook/react"}'
That is the quickest way to confirm both the upstream server and Mcpjungle routing are working as expected.

​
Deregister a server

To remove a server from Mcpjungle: 
mcpjungle deregister deepwiki
Deregistering removes the server and all the tools, prompts, and resources it provided. They are no longer accessible by clients using mcpjungle.

STDIO servers

Register local process-based MCP servers using JSON config files.

Connect Claude Desktop

Connect Claude Desktop to Mcpjungle and start using your registered tools through one MCP endpoint.

Tools and prompts

List, invoke, enable, disable, and retrieve what registered servers expose.

Config file reference

See the full JSON schema details for server registration files.