Yourware MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| YOURWARE_API_KEY | No | Your API key for yourware.so |
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 |
|---|---|
| check_credentialsB | Check your yourware credentials exists and are valid. |
| create_api_keyA | Create a new yourware API key. This will automatically be stored in /root/.yourware/credentials.json. Use this tool if current credentials are invalid |
| upload_projectA | Upload a file or directory to yourware, might be a dist/out directory or a single html file. Use absolute path if possible. For multiple files, you should move them to a directory first, then use this tool to upload the directory |
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 3 tools
Each tool has a clearly distinct purpose: checking credentials, creating an API key, and uploading a project. There is no overlap or ambiguity between them.
All tool names follow a consistent verb_noun pattern in snake_case (check_credentials, create_api_key, upload_project), making them predictable and easy to understand.
With 3 tools, the server is lean but covers the essential credential and upload operations for Yourware. A slightly larger set might be expected, but the count is still reasonable and focused.
The tool surface covers credential management and uploading, but lacks operations like listing, updating, or deleting projects. This leaves notable gaps that agents may encounter.