Ncloud MCP Server

Created By
sjk442517 days ago
MCP server for managing Naver Cloud Platform (Ncloud) infrastructure. Provides 1,000+ API tools across 60+ services including Compute, Networking, Database, Storage, Containers, Monitoring, and more.
Overview

Ncloud MCP Server

MCP server for managing Naver Cloud Platform (Ncloud) infrastructure directly from AI assistants.

Features

  • 1,000+ API tools across 60+ Ncloud services
  • Compute (Server, Block Storage, Public IP, Placement Group)
  • Networking (VPC, Subnet, ACG, Load Balancer, NAT Gateway, Global DNS)
  • Database (MySQL, PostgreSQL, MSSQL, MongoDB, Redis)
  • Storage (Object Storage S3-compatible, NAS, Archive Storage)
  • Containers (NKS, Container Registry)
  • Monitoring (Cloud Insight - Dashboard, Event, Rule, Plugin, Data)
  • DevTools (SourceCommit, SourceBuild, SourceDeploy, SourcePipeline)
  • Security (Certificate Manager, Private CA, KMS)
  • Analytics (Search Engine, Hadoop, Data Streaming, Data Catalog)
  • And more: Cloud Functions, API Gateway, SENS, Auto Scaling, Billing...

Notes

  • Built for Ncloud Public (민간존) environment
  • Based on Ncloud Official API Documentation
  • Primarily tested in Korea (KR) region
  • Requires Node.js 20+ and Ncloud API credentials

Server Config

{
  "mcpServers": {
    "ncloud": {
      "command": "npx",
      "args": [
        "-y",
        "ncloud-mcp-server"
      ],
      "env": {
        "NCLOUD_ACCESS_KEY": "your-access-key",
        "NCLOUD_SECRET_KEY": "your-secret-key",
        "NCLOUD_REGION": "KR"
      }
    }
  }
}
Project Info
Created At
17 days ago
Updated At
16 days ago
Author Name
sjk4425
Star
-
Language
-
License
-
Category

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

9 hours ago
Alloy

2 days ago