Wardrowbe MCP Server
by mjrealm
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_PORT | No | Port for HTTP transport. | 8080 |
| MCP_API_KEY | No | Bearer key that clients send to /mcp. Required when using HTTP transport. | |
| MCP_BIND_HOST | No | Address for HTTP transport. Use 0.0.0.0 in containers. | 127.0.0.1 |
| MCP_TRANSPORT | No | Transport to use: stdio or http. | stdio |
| WARDROWBE_URL | Yes | Base URL of your Wardrowbe instance. | |
| OIDC_CLIENT_ID | No | OIDC client ID. Required when using OIDC. | |
| OIDC_ISSUER_URL | No | OIDC issuer, e.g. https://pocket.example.com. Use this instead of WARDROWBE_TOKEN. | |
| WARDROWBE_TOKEN | No | A Wardrowbe access token (JWT). Use this instead of the OIDC_* variables. | |
| OIDC_CLIENT_SECRET | No | Only for confidential OIDC clients. | |
| OIDC_REFRESH_TOKEN | No | Use this refresh token instead of the saved one. Useful for headless hosts. | |
| WARDROWBE_TOKEN_FILE | No | Where the refresh token is saved. | ~/.config/wardrowbe-mcp/refresh-token.json |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
No tools | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
This server cannot be deployed
Maintenance
ActivityMaintained
ResponsivenessNo recent community issues