NoLang MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NOLANG_API_KEY | Yes | Your NoLang API key (Get it from the NoLang dashboard: NoLang API > API Key) |
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 |
|---|---|
| generate_video_with_settingC | Consumes paid credits. Start video generation using your VideoSetting ID. Provide text, pdf_path, pptx_path, audio_path, video_path, or image_paths as required. |
| generate_video_with_templateC | Consumes paid credits. Start video generation using an official template Video ID. Provide text, pdf_path, pptx_path, audio_path, video_path, or image_paths as required. |
| wait_video_generation_and_get_download_urlB | Polls until video generation completes and returns the download URL. |
| list_generated_videosB | Return a paginated list of videos you have generated. |
| list_video_settingsC | Return a paginated list of your VideoSettings. |
| recommend_templatesB | Recommend official templates based on video mode and optional query. |
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 6 tools
The tools have clear distinctions in purpose, but there is some overlap between 'generate_video_with_setting' and 'generate_video_with_template' as both handle video generation with similar parameters, which could cause confusion. The other tools (list_generated_videos, list_video_settings, recommend_templates, wait_video_generation_and_get_download_url) are distinct and well-defined.
All tool names follow a consistent snake_case pattern with clear verb_noun structures (e.g., generate_video_with_setting, list_generated_videos). The naming is predictable and readable throughout the set, with no deviations in style.
With 6 tools, the count is well-scoped for a video generation server, covering key operations like generation, listing, and monitoring. Each tool appears to earn its place without being overly sparse or bloated.
The tool set covers core video generation workflows, including creation (with settings/templates), listing, and status monitoring. A minor gap exists in lacking explicit update or delete operations for videos or settings, but agents can likely work around this for basic usage.