Janus MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JANUS_OUTPUT_FORMAT | No | Sets the default output format for new sessions. Available formats: compact (default), structured, markdown, json. | compact |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| initialize_sessionC | Initialize a new session with an OpenAPI specification file or URL |
| set_output_formatC | Change the output format for a session |
| get_session_infoC | Get basic information about an OpenAPI specification session |
| list_endpointsB | List all available endpoints in the OpenAPI specification |
| get_endpoint_detailsC | Get detailed information about a specific endpoint with selective data retrieval for token optimization |
| get_tagsB | Get all available tags in the OpenAPI specification |
| get_componentsC | Get reusable components from the OpenAPI specification (schemas, responses, parameters, etc.) |
| remove_sessionC | Remove a session and free up memory |
| generate_documentationB | Generate comprehensive markdown documentation for the API and return the file path |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 9 tools
Each tool targets a clearly distinct operation: session lifecycle, spec inspection, or documentation generation. There is no meaningful overlap between listing endpoints, getting endpoint details, tags, or components.
All tools use consistent snake_case with verb_noun or verb_noun_phrase patterns such as initialize_session, list_endpoints, get_endpoint_details, and generate_documentation. The convention is predictable throughout.
Nine tools are well-scoped for an OpenAPI exploration and documentation server. Each tool has a clear role, and there are no redundant or filler tools.
The surface covers session lifecycle, endpoint/tag/component inspection, and documentation generation. Minor gaps exist around searching/filtering endpoints or retrieving raw spec content, but these are workable via existing tools.