ncp-mcp
A lightweight MCP server for calling NAVER Cloud Platform (Ncloud) APIs with just a few generic, signed tools — read-only by default.
List credential profiles (
ncp_profiles): see usable and disabled profiles with reasons, whether writes are enabled, and optionally verify each key's owner (account ID, login alias, main/sub type) via STS — secrets never returned.Call any read-only Ncloud API (
ncp_call): one call per request with request signing, JSON responses, automatic list-param expansion, paging, andfieldsto trim results (e.g.vserver/getServerInstanceList, REST-stylesubaccount//sub-accounts).Batch read queries (
ncp_batch): run many read-only calls concurrently in one shot, results in input order, per-item failures isolated.Write operations (
ncp_write): only available when the server runs withNCP_ALLOW_WRITE=trueand actions are individually listed inNCP_WRITE_ALLOWLIST— not present in this schema.Built-in safety: read vs. write split by action name, service allowlist per zone, retries on 429/5xx/timeouts, concurrency cap, keys excluded from errors, and MCP annotations (
readOnlyHint/destructiveHint) for client permissions.Multi-zone support:
pub,gov,finzones via~/.ncloud/configureprofiles (or env vars), with profile selection when more than one 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.
ncp-mcp
NAVER Cloud Platform(Ncloud)용 가벼운 MCP 서버입니다. A lightweight MCP server for NAVER Cloud Platform: a few generic tools instead of one tool per API.
API마다 도구를 하나씩 만들지 않고, 서명된 범용 호출 도구 몇 개로 모든 Ncloud API를 부릅니다. 도구 정의가 작아서 MCP 연결만으로 대화 컨텍스트를 거의 차지하지 않습니다.
네이버클라우드 공식 프로젝트가 아닙니다.
도구
도구 | 설명 |
| 사용 가능한 프로필·존, 규칙에 어긋나 꺼진 프로필과 이유, 쓰기 허용 여부. |
| 조회 전용 API 1건 호출. 서명, |
| 조회 여러 건을 동시에 실행(최대 50건, 동시 5건). 항목별 실패는 다른 항목에 영향 없음 |
| 생성·변경·삭제 API 호출. |
// 서버 목록 (필요한 필드만)
ncp_call(service="vserver", action="getServerInstanceList", params={"regionCode": "KR"},
fields=["serverName", "serverInstanceStatus.code", "privateIp"])
// 서브계정 목록 (REST 형식 서비스)
ncp_call(service="subaccount", action="/sub-accounts")
// 여러 리전 한 번에
ncp_batch(calls=[
{"service": "vserver", "action": "getServerInstanceList", "params": {"regionCode": "KR"}},
{"service": "vserver", "action": "getServerInstanceList", "params": {"regionCode": "JPN"}}
])Related MCP server: production-grade-mcp-agentic-system
안전장치
조회와 변경을 도구 단위로 나눴습니다.
ncp_call·ncp_batch는get*·list*·describe*같은 조회 동작과 REST 형식의 GET만 허용합니다. Ncloud의 공용 게이트웨이 API는 삭제 동작도 GET으로 받기 때문에 HTTP 메서드가 아니라 동작 이름으로 판정합니다.변경은
ncp_write로만 할 수 있고, 이 도구는 서버를NCP_ALLOW_WRITE=true로 실행했을 때만 나타납니다. 그리고 호출할 동작을NCP_WRITE_ALLOWLIST에 하나씩 적어야 합니다(예:vserver:stopServerInstances). 변경 요청은 재시도하지 않습니다.호출할 수 있는 서비스는 존별 허용 목록(
src/ncp_mcp/endpoints.py, NCP 공식 API 문서 기준)으로 제한합니다. 목록에 없는 서비스는NCP_MCP_EXTRA_SERVICES="gov:cdn"처럼 직접 추가해야 합니다.조회 요청은 429·5xx·시간 초과 때 최대 2번 다시 시도하고(
NCP_MCP_RETRIES), 동시 요청은 5개로 제한합니다(NCP_MCP_CONCURRENCY).도구마다 MCP 표준 표시(
readOnlyHint/destructiveHint)를 붙였습니다. 클라이언트 권한 설정에서ncp_call·ncp_batch는 허용,ncp_write는 매번 확인으로 나눠 두는 것을 권장합니다. (Claude Code 예:permissions.allow에mcp__ncp__ncp_call,permissions.ask에mcp__ncp__ncp_write)서명된 요청은 선택한 존의 API 게이트웨이 도메인(
*.apigw.ntruss.com등)으로만 보냅니다.키는 오류 메시지와 결과에 포함하지 않습니다. 최종 권한 경계는 Access Key의 서브계정 권한이므로 조회 권한만 준 서브계정 키 사용을 권장합니다.
설치
Python 3.10 이상, uv 필요.
// .mcp.json
{
"mcpServers": {
"ncp": {
"command": "uvx",
"args": ["--from", "git+https://github.com/<owner>/ncp-mcp@v0.2.0", "ncp-mcp"]
}
}
}태그로 버전을 고정해 쓰는 것을 권장합니다.
자격증명
Ncloud CLI와 같은 파일 ~/.ncloud/configure(INI)를 읽습니다. 섹션 하나가 프로필 하나입니다.
[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 = gov프로필 규칙(어긴 프로필은 사용하지 않고 ncp_profiles의 disabled에 이유를 보여 줍니다)
ncloud_zone(pub·gov·fin)을 반드시 적습니다.프로필 이름은 소문자·숫자·하이픈이고 끝이 존과 같아야 합니다(
-pub,-gov,-fin). 이름만 봐도 존을 알 수 있게 하기 위해서입니다. 그래서[DEFAULT]는 쓸 수 없습니다.프로필이 2개 이상이면 호출할 때마다
profile을 지정해야 합니다. 기본 프로필은 없습니다.사용 가능한 프로필 이름은 서버 시작 시 도구 정의에 선택 목록으로 들어갑니다. 프로필을 바꾸면 MCP 서버를 다시 시작하세요.
ncp_profiles(verify=true)는 각 키가 실제로 어느 NCP 계정·사용자의 키인지 STS(caller-identity)로 확인해 보여 줍니다.
Ncloud CLI는 --profile <이름>으로 같은 프로필을 쓸 수 있습니다.
환경변수
NCLOUD_ACCESS_KEY·NCLOUD_SECRET_KEY·NCLOUD_ZONE을 주면env-<zone>프로필이 추가됩니다.NCP_MCP_CONFIG로 설정 파일 위치를 바꿀 수 있습니다.
서비스 주소
서비스 | 주소 |
기본(공용 게이트웨이) |
|
|
|
|
|
|
|
|
|
<zone>은 ntruss.com(민간) · gov-ntruss.com(공공) · fin-ntruss.com(금융)입니다.
개발
uv sync
uv run pytest
git config core.hooksPath .githooks # 커밋 전 gitleaks 비밀값 검사라이선스
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-