upscayl-docker-worker
by yellowcooln
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| UPSCAYL_OUTPUT_DIR | Yes | Directory where upscaled images will be written, e.g. /home/user/Pictures/upscayl | |
| UPSCAYL_WORKER_URL | Yes | URL of the upscayl worker API, e.g. http://private-gpu-host:8788 | |
| UPSCAYL_WORKER_TOKEN | Yes | Secret token for authenticating with the worker API | |
| UPSCAYL_ALLOWED_INPUT_ROOTS | Yes | Colon-separated list of directories the bridge is allowed to read input images from, e.g. /home/user/.hermes:/home/user/Pictures |
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 | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/yellowcooln/upscayl-docker-worker'
If you have feedback or need assistance with the MCP directory API, please join our Discord server