ncloud-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NCLOUD_SPEECH_SECRET | No | Secret for the CLOVA Speech domain. | |
| NCLOUD_SPEECH_ENABLED | No | Set to true to expose CLOVA Speech tools; the default is disabled. | false |
| NCLOUD_SPEECH_INVOKE_URL | No | Base Invoke URL of the CLOVA Speech domain, without /recognizer/...; must match the official https://clovaspeech-gw.ncloud.com/external/v1/<domain-id>/<invoke-key> format. | |
| NCLOUD_SPEECH_LOCAL_ROOTS | No | OS path separator-separated dedicated recording directories allowed for local file input; do not include your home, repository, or credentials directory. | |
| NCLOUD_SPEECH_ALLOW_ASYNC_OBS | No | Set to true to allow async completion with result_to_obs=true. | false |
| NCLOUD_SPEECH_ALLOW_OBJECT_STORAGE | No | Set to true to explicitly enable the object_storage source. | false |
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 |
|---|---|
| ncloud_healthC | Offline configuration flags only. No network, identifiers, paths, URLs, or secrets. |
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 confusing it with another tool. The tool's purpose is distinct by default, even though its description is narrow.
The single tool uses a consistent snake_case name with a clear prefix (ncloud_health). There are no conflicting conventions to compare against.
One tool is too few for a server named ncloud-mcp, which implies broader cloud operations. A single health/config diagnostic is far too thin for the apparent scope.
The surface contains only an offline health/config tool with no network, identifiers, or actual cloud operations. Any expected cloud management workflow (list, get, create, etc.) is completely missing.