imageright-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| IMAGERIGHT_DRY_RUN | No | Enable dry-run mode. | false |
| IMAGERIGHT_VERSION | No | ImageRight product version (24.x, 25.x, or 7.2). | 24.x |
| IMAGERIGHT_PASSWORD | No | Password for authentication (environment only, always redacted). | |
| IMAGERIGHT_SOAP_URL | No | URL for the SOAP API. | |
| IMAGERIGHT_USERNAME | No | Username for authentication. | |
| IMAGERIGHT_AUTH_MODE | No | Authentication mode: password, jwt, or saml. | password |
| IMAGERIGHT_WRITE_MODE | No | Write mode: deny, dry-run, or allow. | dry-run |
| IMAGERIGHT_CONFIG_FILE | No | Path to a JSON configuration file. | |
| IMAGERIGHT_REST_BASE_URL | No | Base URL for the REST API. | |
| IMAGERIGHT_SURFACE_PREFERENCE | No | Comma-separated API surface preference. | rest-v2,rest-v1,soap |
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 | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| ir_get_configA | Show the configuration this server is using right now: ImageRight version and the catalog profile it maps to, REST and SOAP endpoints, auth mode, surface preference, write mode, and dry-run default. Each field reports where its value came from (env, file, or default). Secrets are always redacted. |
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 1 tool
With only one tool, there is no possibility of overlapping purposes or misselection. The tool's purpose is singular and well-defined.
The name ir_get_config follows a clear verb_noun pattern with a consistent product prefix. Even though there is only one tool, the naming convention is predictable and readable.
A single configuration-inspection tool is far too few for a server named after the ImageRight document management platform. The tool count suggests a stub rather than a functional MCP server, leaving agents with no actual operations to perform.
The server only exposes configuration details and provides zero tools for interacting with ImageRight documents, folders, or workflows. This is a severely incomplete surface for the implied domain.