Skip to main content
Glama
Bayway

janusmcp

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
JANUS_CONFIGNoPath to the configuration file (e.g., config.json)
JANUS_HTTP_HOSTNoHTTP host for Streamable HTTP transport (default 127.0.0.1)
JANUS_HTTP_PORTNoHTTP port for Streamable HTTP transport (default 7332)
JANUS_TRANSPORTNoTransport mode: stdio, http, both (default stdio)

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

CapabilityDetails
tools
{
  "listChanged": true
}
logging
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
janus_list_accountsA

List configured accounts/services and which is active for this session.

janus_loginA

Start an OAuth login for in your browser and store the token as . The token is captured locally and saved to the OS keychain — it never passes through this chat. Afterwards reference it from an account env as "oauth:". Built-in providers: github, google, supabase.

janus_use_accountA

Set the active account/identity. Reloads upstream tools and notifies the client. scope: 'session' or 'global' (defaults to the broker bindingMode).

janus_whoamiB

Return the active account for this session and how it was resolved.

janus_with_accountA

Run a single tool call on another account WITHOUT changing the active account. Omit 'tool' to first list that account's available tools.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.9/5.0

Scored across 5 tools

Disambiguation4/5

Each tool has a distinct action: listing, logging in, switching active account, checking identity, and one-off account-scoped execution. There is minor overlap between janus_list_accounts and janus_whoami since both can reveal the active account, but their descriptions make the distinction workable.

Naming Consistency5/5

All tools share the janus_ prefix and use consistent snake_case naming. The verb-based patterns (list_accounts, login, use_account, whoami, with_account) are predictable and readable despite whoami being a conventional special case.

Tool Count5/5

Five tools is well-scoped for an account/identity management server. Each tool earns its place, covering discovery, authentication, active-account control, identity inspection, and temporary account switching without unnecessary extras.

Completeness4/5

The core account lifecycle is covered: listing, OAuth login, setting active identity, checking identity, and running a one-off call under another account. A logout/forget-account operation is a minor gap, but agents can work around it and the essential workflows are present.

Maintenance

ActivityMaintained
ResponsivenessNo issues