ncp-mcp
A lightweight MCP server for NAVER Cloud Platform (Ncloud) that exposes a few generic, signed API-call tools instead of one tool per API.
List credential profiles (
ncp_profiles): shows usable profiles and zones, disabled profiles with reasons, and whether writes are enabled; withverify=trueit checks keys against NCP STS to reveal the owning account ID, login alias and user type. Secrets are never returned.Make a single read-only API call (
ncp_call): call any read action (get*,list*,describe*, or REST GET) on services likevserver,vpc,vloadbalancer,vpostgresql,billing,subaccount, with automatic request signing, list/dict parameter expansion, optional paging, andfieldsto trim results to the keys you need.Run many calls at once (
ncp_batch): execute several read-only calls concurrently, results kept in input order, with per-item failures isolated and per-item profile overrides.Read-only by design: all three tools are annotated
readOnlyHint: true/destructiveHint: false; no write/create/delete tool is exposed in this schema.Multi-account support: select a credential profile per call (required when more than one profile exists).
Integrates with NAVER Cloud Platform (Ncloud), providing generic signed API tools for read-only queries, batched calls, profile and credential verification, and opt-in write operations across Ncloud services.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@ncp-mcp list my KR servers with names, status, and private IPs"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
ncloud-mcp-server
한국어 | English
A lightweight MCP server for NAVER Cloud Platform (Ncloud).
Instead of one tool per API, a few signed, generic call tools reach every Ncloud API. The tool definitions are small, so connecting the server costs almost no conversation context.
This is not an official NAVER Cloud project.
Tools
Tool | Description |
| Usable profiles and zones, profiles disabled by the rules (with the reason), and whether writes are enabled. With |
| 1 to 50 read-only API calls, run 5 at a time. Handles signing, |
| Calls APIs that create, change or delete resources. Registered only when the server runs with |
// Server list (only the fields you need)
ncp_read(calls=[{"service": "vserver", "action": "getServerInstanceList", "params": {"regionCode": "KR"},
"fields": ["serverName", "serverInstanceStatus.code", "privateIp"]}])
// Sub accounts (REST-style service)
ncp_read(calls=[{"service": "subaccount", "action": "/sub-accounts"}])
// Several regions at once
ncp_read(calls=[
{"service": "vserver", "action": "getServerInstanceList", "params": {"regionCode": "KR"}},
{"service": "vserver", "action": "getServerInstanceList", "params": {"regionCode": "JPN"}}
])Related MCP server: production-grade-mcp-agentic-system
Safety
Reads and writes are separate tools.
ncp_readaccepts only read actions such asget*,list*anddescribe*, plus REST-style GETs. Ncloud's shared API gateway accepts even delete actions over GET, so operations are classified by action name, not by HTTP method.Only actions proven read-only are allowed. On shared-gateway services an action counts as a read only if it is a single path segment in camelCase starting with a read verb (
getServerInstanceList). Anything else, such asterminateserverinstances,TerminateServerInstancesorterminateServerInstances/x, is treated as a write and blocked.Read actions that return secrets (
getRootPassword,getRootPasswordServerInstanceList, the NKSkubeconfig) are blocked inncp_read. If you really need one, add it toNCP_WRITE_ALLOWLISTand call it withncp_write.Writes are possible only through
ncp_write, which appears only when the server runs withNCP_ALLOW_WRITE=true. Each action must also be listed inNCP_WRITE_ALLOWLIST(comma separated). Write requests are never retried.For shared-gateway services, write
vserver:stopServerInstances. The shared gateway takes GET and POST as the same call, so both are allowed.For REST-style services, put the method first:
POST subaccount:/sub-accounts,DELETE subaccount:/sub-accounts/123. An entry without a method allows GET only, and allowing POST on a path does not allow DELETE on it.If you used an entry like
subaccount:/sub-accountsfor POST with 0.5.x or earlier, add the method.
Callable services are limited to a per-zone allowlist (
src/ncp_mcp/endpoints.py, based on the official NCP API docs). To use a service that is not listed, add it explicitly, e.g.NCP_MCP_EXTRA_SERVICES="gov:cdn".Read requests are retried up to 2 times on 429, 5xx and timeouts (
NCP_MCP_RETRIES), and concurrent requests are limited to 5 (NCP_MCP_CONCURRENCY).A single result is capped at 100,000 characters of JSON, about 25,000 tokens (
NCP_MCP_MAX_RESULT_CHARS). Beyond that, only the first list items are kept andtruncatedexplains why. With several calls,ncp_readsplits this budget across them. If a result was cut, usefieldsto keep only the columns you need, or narrow the query.Every tool carries the standard MCP hints (
readOnlyHint/destructiveHint). In your client's permission settings we recommend allowingncp_read, and asking every time forncp_write. (Claude Code example:mcp__ncloud__ncp_readinpermissions.allow,mcp__ncloud__ncp_writeinpermissions.ask)Signed requests are sent only to the selected zone's API gateway domains (
*.apigw.ntruss.cometc.).Keys never appear in error messages or results. The final permission boundary is the sub-account permissions of the access key, so we recommend a sub-account key with read-only permissions.
Installation
Requires Python 3.10+ and uv.
Claude Code: register it with one command.
claude mcp add ncloud --scope user -- uvx --from git+https://github.com/revert12/ncloud-mcp-server@v0.7.0 ncloud-mcp-server--scope picks where it is registered.
local(default): only you, only in the current project (stored in~/.claude.json)user: only you, in every projectproject: stored in.mcp.jsonat the project root and shared with your team
Check with claude mcp list; remove with claude mcp remove ncloud.
Other MCP clients: add it to the config file directly.
// .mcp.json
{
"mcpServers": {
"ncloud": {
"command": "uvx",
"args": ["--from", "git+https://github.com/revert12/ncloud-mcp-server@v0.7.0", "ncloud-mcp-server"]
}
}
}Pinning a version with a tag is recommended.
Credentials
The server reads ~/.ncloud/configure (INI), the same file the Ncloud CLI uses. Each section is one profile.
[mycompany-pub]
ncloud_access_key_id = <access key>
ncloud_secret_access_key = <secret key>
ncloud_zone = pub
[customer-a-gov]
ncloud_access_key_id = <gov access key>
ncloud_secret_access_key = <gov secret key>
ncloud_zone = govProfile rules (a profile that breaks one is not used; ncp_profiles lists it under disabled with the reason)
ncloud_zone(pub,govorfin) is required.Profile names use lowercase letters, digits and hyphens, and must end with the zone (
-pub,-gov,-fin), so the zone is visible from the name alone. For the same reason[DEFAULT]cannot be used.With two or more profiles, every call must name its
profile. There is no default profile.Usable profile names are written into the tool definitions as choices when the server starts. Restart the MCP server after changing profiles.
ncp_profiles(verify=true)asks STS (caller-identity) which NCP account and user each key really belongs to.
The Ncloud CLI can use the same profiles with --profile <name>.
Setting the environment variables
NCLOUD_ACCESS_KEY,NCLOUD_SECRET_KEYandNCLOUD_ZONEadds anenv-<zone>profile.NCP_MCP_CONFIGchanges the location of the config file.
Service endpoints
Service | Endpoint |
Default (shared gateway) |
|
|
|
|
|
|
|
| See |
<zone> is ntruss.com (public), gov-ntruss.com (government) or fin-ntruss.com (financial).
Development
uv sync
uv run pytestSee CONTRIBUTING.md for setup, the pre-commit secret scan, and how the read-only guard is verified.
License
MIT
Available Tools
3 toolsncp_batchARead-only
Run several read-only ncp_call requests concurrently; results keep the input order.
Each item takes the ncp_call keys: service, action, and optionally params, fields, profile, paginate. A per-item 'profile' overrides the batch profile. Failures are reported per item and do not stop the others.
Inputs: calls (required), profile. Returns: object
ncp_callARead-only
Call one read-only Ncloud API (get*/list*/describe*/... or REST GET) with request signing.
Args: service: Ncloud service key, e.g. 'vserver', 'vpc', 'vloadbalancer', 'vpostgresql', 'billing', 'subaccount'. Unknown names map to the shared gateway //v2. action: Path under the service base, e.g. 'getServerInstanceList' or '/sub-accounts'. params: Query parameters. Lists become name.1, name.2; dicts become name.key. fields: Keep only these keys in each list item (dot paths allowed, e.g. ['serverName', 'serverInstanceStatus.code']). profile: Credential profile. Required when more than one profile exists. paginate: Follow pageNo until totalRows is reached for list actions.
Inputs: action (required), service (required), fields, params, +2 more. Returns: object
ncp_profilesARead-only
List usable credential profiles, disabled profiles with the reason, and whether writes are enabled.
Secrets are never returned. With verify=true, each usable profile is checked against NCP STS (GET /api/v1/caller-identity) and the key owner's account id, login alias and user type (Customer = main account, Sub = sub account, Role) are shown.
Inputs: verify. Returns: object
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 3 tools
Each tool targets a distinct layer: ncp_profiles for credential/config inspection, ncp_call for a single API request, and ncp_batch for concurrent multi-request execution. The only mild overlap is that ncp_batch is effectively a fan-out wrapper over ncp_call, but the descriptions make the boundary clear (order-preserving, per-item failure isolation, per-item profile override).
All names share a consistent ncp_ prefix and snake_case form, which reads well as a family. The only minor deviation is that ncp_profiles is a noun while ncp_call and ncp_batch are verbs, but the intent of each is still immediately clear.
Three tools is lean but appropriate for a generic gateway design, where the breadth lives inside ncp_call's service/action arguments rather than in separate tools. Nothing feels redundant or missing at the tool level, though the surface is on the thin side.
The read-only call/batch pair covers querying well, including pagination, field filtering, and credential selection. However, there is no discovery/introspection tool to enumerate available services and actions (or their schemas), so an agent must already know Ncloud API paths, and no write operations are exposed despite the mention of a writes-enabled flag.
Maintenance
Related MCP Connectors
MCP server for your apps' tools and custom tools, plus hosted AI agents and approval-gated workflows
Nifty's MCP server — exposes tasks, projects, messages, and files as tools for AI agents.
The Remote MCP server acts as a standardized bridge between LLM applications (like Claude, ChatGPT, and Cursor) and external services, enabling AI agents to access external tools and resources. Its primary capability is providing a centralized search tool to discover other MCP servers and their respective tools. Unlike local implementations, it runs remotely with OAuth authentication and permission controls for security.
MCP server connecting AI agents to 100+ apps (Gmail, Slack, Notion, GitHub) via one-click OAuth.
Related MCP Servers
- AlicenseAqualityDmaintenanceMCP server that exposes 300+ AI agents as tools via a single API key. Supports listing agents, invoking any agent with chat-completion style messages, checking agent health, and retrieving platform statistics.54MIT
- AlicenseNot gradedqualityDmaintenanceA production-grade MCP server designed for multi-tenant, authenticated, and observable AI agent systems, enabling secure tool execution across heterogeneous data sources.68MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to discover and execute tools via a secure MCP server with JWT authentication, RBAC, rate limiting, and audit logging.1MIT
- FlicenseNot gradedqualityCmaintenanceMulti-cloud MCP server that exposes cloud AI models as tools for AI CLI agents, supporting streaming, conversation history, parallel multi-model queries, and dynamic model discovery.2-