Rosh MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ROSH_API_KEY | No | Your rosh.cloud API key, required for publishing operations | |
| ROSH_API_BASE | No | API base URL | https://rosh.cloud |
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 |
|---|---|
| rosh_docsA | Get the Rosh language documentation — keywords, widgets, targets, and examples. Returns the full language reference including all 25 keywords, available widgets, compile targets (web, phaser, threejs), and example programs. No API key needed. |
| rosh_compileA | Compile Rosh code into a runnable HTML page. No API key needed. Rosh is a plain-English programming language. Example: create box called player at 400 300 set player color "blue" on key "ArrowRight" then set player x to player x + 5 Args: code: Rosh source code to compile target: Target platform — "web" (HTML5 canvas), "phaser" (game engine), or "threejs" (3D) |
| rosh_publishA | Compile and publish a Rosh program to rosh.cloud. Requires API key with write scope. The published program gets a public URL at https://rosh.cloud/p/{username}/{slug} Args: title: Display title for the program slug: URL-safe identifier (lowercase, hyphens only, e.g. "space-shooter") code: Rosh source code target: Target platform — "web", "phaser", or "threejs" description: One-line description of what the program does |
| rosh_list_programsA | List all programs owned by the authenticated user. Requires API key. |
| rosh_get_programA | Get details of a specific program by ID. Requires API key. Args: program_id: The numeric program ID |
| rosh_update_programA | Update an existing program. Only provided fields are changed. Requires API key with write scope. Args: program_id: The numeric program ID title: New title (optional) description: New description (optional) code: New source code (optional) target: New target platform (optional) |
| rosh_delete_programA | Permanently delete a program. Requires API key with write scope. Args: program_id: The numeric program ID |
| rosh_hide_programA | Hide a program from public view (moderation). Requires API key with moderate scope. Args: identifier: Program ID (numeric) or slug (string) |
| rosh_show_programA | Make a hidden program visible again. Requires API key with moderate scope. Args: identifier: Program ID (numeric) or slug (string) |
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 9 tools
Each tool has a unique purpose with clear verb_noun naming. Even closely related tools like compile and publish are distinct (compile generates HTML, publish additionally deploys). Hide and show are clear opposites, and CRUD operations are well separated.
All tools follow a consistent rosh_verb_noun pattern in snake_case. The naming convention is uniform across the entire tool set, making it predictable for agents.
With 9 tools, the server covers a focused domain (Rosh language management) without bloat. Each tool serves a necessary function: compilation, documentation, CRUD, and moderation. The count feels right for the scope.
The tool set appears complete for the domain: it includes compilation, publishing, full CRUD for programs, moderation (hide/show), and documentation. There are no obvious missing operations like a search or share tool, but they are not essential for core functionality.