SuperAPI AI Directory
Partner中文AI newsFavorites
Skillssetup-mcp-connector

setup-mcp-connector

Agents & models

View repository

Updated 10-15 23:23

About this skill

MCP Connector Setup Guide

Overview

Drive·Notion·Higgsfield 3 connectors + Korean public data·documents·statutes 5 MCP(kordoc·dart·korean-stats·archhub·korean-law) to Cowork. It covers the entire setup process, from the authentication flow and API key entry to one-time call verification and troubleshooting.

Setup Completion Checklist

  • Drive·Notion·Higgsfield — Authentication success + one-time call success (Drive: folder list / Notion: shared page read / Higgsfield: model list)
  • kordoc — Node.js 18+ confirmed + one-time document parsing success (no key required)
  • dart(korean-dart-mcp) — Node.js 20.19+ + OpenDART key + one-time disclosure search success
  • korean-stats — one-time natural language statistics query success (no key required, public key hosted)
  • archhub — one-time building comprehensive card query success (no key required, public key hosted)
  • korean-law — Ministry of Government Legislation OC key + one-time statute search success (free issuance at law.go.kr, key required per user)

Trigger Keywords

MCP connector connection, Drive authentication, Notion Integration Token, Higgsfield API key, 3-connector installation, computer:// link, MAX_PATH error, Korean filename error, OAuth redirect URI

Workflow

Step 1 — Prerequisites

Create the following accounts in advance before connecting the connectors:

  • Google account (Drive)
  • Notion account
  • Higgsfield account + workspace credit top-up

[HARD] API Key Security Rules: API keys are issued and stored by you personally. Do not paste the raw key into chat conversations or shared documents; enter it only in the API Key field of the connector settings screen.

Connector A — Google Drive

Purpose: Cowork folder mount + file access (drive.readonly, drive.file permissions)

Authentication Method: Cowork app → Add connector → Google Drive → OAuth login

Required Permissions

  • drive.readonly — file read
  • drive.file — access files created by Cowork

Authentication Steps

  1. Cowork app → Settings → MCP Connector → Select Google Drive
  2. Click "Connect with Google account"
  3. Select account + grant permissions on the Google OAuth screen
  4. After connection is complete, verify with a one-time Drive folder list call

One-Time Call Verification: Success if the folder list appears in the response

Connector B — Notion

Purpose: Read and write Notion pages for work deliverables

Authentication Method: Cowork app → Add connector → Notion → OAuth authentication

Authentication Steps

  1. Cowork app → Settings → MCP Connector → Select Notion
  2. Click "Connect with Notion"
  3. Select workspace + grant page access permissions on the Notion OAuth screen
  4. Verify with 1 read call to the shared page after connection is complete

Verify with 1 call: Success if the shared page content appears in the response

Connector C — Higgsfield

Purpose: Media tasks such as ad video generation (calling image/video generation models)

Authentication method: API key method (not OAuth)

Prerequisites to check

  • Check whether Higgsfield workspace credits are topped up (if the balance is insufficient, authentication may succeed but generation calls may fail)
  • Estimate expected usage: check in advance the credit consumption per video (5-10 seconds)
  • Cost limit: set a usage limit in workspace settings to prevent unexpected charges

Authentication steps

  1. Cowork app → Settings → MCP Connectors → Select Higgsfield
  2. Enter the issued key in the API Key field (issuer: higgsfield.ai → API Keys)
  3. Verify with 1 model list call after connection is complete

Verify with 1 call: Success if the list of available models appears in the response

Korean public data, documents, and legislation MCPs (5 types)

The Cowork plugin additionally supports 5 MCPs for handling Korean public data, official documents, and legislation. It covers the prior preparation and 1-call verification for each MCP. The 5 MCPs created by chrisryugj are all under the MIT license.

Connector D — kordoc (Korean official document parser)

Purpose: HWP 3.0/5.x·HWPX·HWPML·PDF·XLSX·DOCX → Markdown conversion. Perfect table reproduction, old-new comparison tables, automatic form filling, DRM distribution decryption, OCR integration. moai-officer:doc-reader Invoked by the skill.

Prerequisites: No API key required. Only Node.js 18+ is needed.

Installation steps

  1. Check Node.js 18+ installation: node --version (must be v18 or higher)
  2. .mcp.jsonAlready registered in (command: npx, args: ["-y", "kordoc", "mcp"])
  3. On the first call, npm downloads the kordoc package (about 10-30 seconds), then cache hits thereafter

Verify with 1 call: With an arbitrary HWP/PDF file, call parse_document → Success if a Markdown response is returned

On Windows environments where Hancom Office is installed, the DRM distribution HWP/HWPX COM fallback additionally works (optional).

Connector E — dart / korean-dart-mcp (OpenDART electronic disclosures)

Purpose: Compresses 83 OpenDART APIs into 15 tools. Disclosures, financials, equity, XBRL (markdown_full all accounts + calculation verification) + Buffett-grade analyst framework (insider_signal·disclosure_anomaly·buffett_quality_snapshot) + HWP/PDF attachment Markdown conversion (kordoc engine) + 90-day automatic splitting. Automatic resolution of company name/stock code/corp_code (SQLite FTS, about 5-10 seconds to dump 116,000 records on first startup).

Prerequisites

  • Node.js 20.19+ (LTS recommended) — node --versioncheck with
  • OpenDART authentication key(40 characters, free, 20,000 calls per day)

Authentication key issuance procedure

  1. https://opendart.fss.or.kr Access → Sign up
  2. After logging in, apply for an authentication key → receive the 40-character authentication key immediately by email
  3. Environment variable DART_API_KEYregistered in

Authentication steps

  1. Enter the issued 40-character key into the ${CLAUDE_PLUGIN_DATA}/moai-credentials.env의 DART_API_KEY field
  2. On first startup, wait for the corp_code dump (116,000 records, about 5-10 seconds)
  3. Verify with 1 call: resolve_corp_code("삼성전자") → confirm corp_code is returned

Verify with 1 call: success if corp_code is returned from the company name

Alternative — setup wizard: npx -y korean-dart-mcp setup When run, an interactive wizard handles everything from key entry to automatic patching of the client configuration file (shared across macOS/Linux/Windows). On Windows, cmd /c npx wrapping is applied automatically.

Caution: Since the corp_code dump download takes 5-10 seconds on first startup, allow extra timeout. MODULE_NOT_FOUND On error, retry with npm uninstall -g korean-dart-mcp 후 npx -y korean-dart-mcp@latest setup.

Connector F — korean-stats (KOSIS Statistics Korea statistics)

Purpose: Query KOSIS statistics in one natural-language line. 14 tools, 92 keywords + 100+ natural-language aliases, 17 si/do + 230+ autonomous district/si/gun routing, time-series trends/rankings, automatic citation of sources (statistical table ID), distinction between estimates/provisional figures. moai-analyst:data-publicroutes natural-language queries first.

Prerequisites: No API key required. Remote connector with a public key built in (register URL only).

Installation steps

  1. .mcp.jsonAlready registered in (type: http, url: https://mcp.gomdori.app/stats)
  2. Use immediately with only an internet connection

Verify with 1 call: quick_stats("광진구 고용률") → success if it responds with statistical figures + source (statistical table ID)

If autonomous-district-level data does not exist in KOSIS, it does not arbitrarily answer with the metropolitan si/do value as if it were the autonomous district value; instead it explicitly informs the user that "it was substituted with metropolitan si/do data." For duplicate names (Busan Jung-gu vs Seoul Jung-gu), the metropolitan city must also be stated to distinguish them accurately.

Connector G — archhub (Ministry of Land, Infrastructure and Transport Building HUB)

Purpose: Building register, building permits, housing permits + legal district codes + single-parcel comprehensive card, floor-by-floor composition, dong-level statistics, old buildings, demolition/loss (asbestos), permit pipeline, official price time series. 11 tools. moai-analyst:data-building-ledger skill is called.

Prerequisites: No API key required. Remote connector with a public key built in (register URL only).

Installation steps

  1. .mcp.jsonAlready registered in (type: http, url: https://mcp.gomdori.app/archhub)
  2. Use immediately with only an internet connection

Verify with 1 call: find_region("광진구 자양동") → after sigungu_code/bdong_code is returned, call building_profile → success if the comprehensive card responds

archhub는 [NOT_FOUND](no data)·[EXTERNAL_API_ERROR](upstream error) prefixes to block hallucination. It provides only actual measured values from the official data.go.kr API, and owner information (personal information) and violation-building lookups are out of scope.

Connector H — korean-law (Ministry of Government Legislation National Law Information)

Purpose: Original-text lookup of national law information (Ministry of Government Legislation) statutes, precedents, administrative rules, autonomous ordinances, treaties, interpretation cases (National Tax Service) + LLM hallucination-prevention citation verification (verify_citations) + precedent validity (cite_check) + law at the time of the act (applicable_law) + provision impact graph (impact_map). 42 APIs → 9 tools. moai-lawyer:legal-law-research Skill is called.

Prerequisites: Ministry of Government Legislation Open API OC key (must be issued per user, not a shared key — differs from stats/archhub). Node.js not required (hosted).

Issuance Procedure

  1. Access law.go.kr (or the Ministry of Government Legislation Open API application page) → Sign up and log in
  2. Apply for Open API use → Fill out the application form
  3. OC key issued immediately (free)

Authentication: Environment variable KOREAN_LAW_OC registration (.mcp.json의 url: https://mcp.gomdori.app/law?oc=${KOREAN_LAW_OC}interpolated). Or enter in the ${CLAUDE_PLUGIN_DATA}/moai-credentials.env의 KOREAN_LAW_OC item.

Single-call verification: search_law(query="근로기준법") → Success if a statute search response is returned

Caution: Not a shared-key model (OC key per user). If there is a certificate verification issue with the Ministry of Government Legislation API on a corporate or closed network, use the LAW_API_PROTOCOL=http fallback. Live skill: moai-lawyer:legal-law-research.

Troubleshooting

T1 — Windows MAX_PATH 260-character limit exceeded error

Symptom: Cowork folder mount fails, path-related error message

Cause: Windows default MAX_PATH 260-character limit. Frequently occurs with long paths containing Korean filenames.

Resolution

  1. Move the folder to a location close to the drive root (e.g., C:\cowork\ or D:\cw\)
  2. 30-character rule for Korean filenames: Keep folder and file names within 30 characters
  3. If necessary, disable the MAX_PATH limit via the Windows Registry (administrator privileges required)

If resolution is difficult (alternative path): If the above methods do not resolve it, you can use a temporary path that accesses files via the Google Drive connector (Connector A) instead of mounting a local folder.

T2 — computer:// link does not open

Symptom: Clicking the computer:// link provided by Cowork does not open it

Resolution

  1. Retry in Chrome incognito mode
  2. Check the browser's default protocol handler (Settings → Default apps → Link handling)
  3. Restart the Cowork app and retry

T3 — OAuth authentication failure (Drive·Notion)

Symptom: "Access denied" or redirect error on the OAuth screen

Resolution

  1. Retry in Chrome incognito mode (prevents cached session conflicts)
  2. If the Google account is a workspace account: administrator approval may be required
  3. OAuth redirect URI issue: Retry after updating the Cowork app version
  4. Check that pop-up blocking is disabled (Browser settings → Allow pop-ups)

T4 — API key authentication failure (Higgsfield)

Symptom: "Invalid API key" or "Unauthorized" error

Resolution

  1. Check that the API key is copied and pasted exactly without leading or trailing spaces
  2. Higgsfield: Check whether the workspace has sufficient credits (authentication fails when balance is insufficient)
  3. Reissue the key and retry

Slash command registration guide

After completing the connector setup, if you register the slash command below in the project CLAUDE.md, you can quickly invoke frequently used skills:

## 슬래시 커맨드

- `/morning-brief` — 아침 브리핑 (commerce-morning-brief)
- `/detail-copy` — 상세페이지 카피 (commerce-detail-page-copy)
- `/channel-msg` — 채널 메시지 (cs-channel-message)

In the project folder, CLAUDE.mdpaste the block above into and register it.

Pre-check Checklist (--check option)

This option checks the sign-up, authentication, and pre-preparation status of 3 connectors + 5 MCPs based on the pre-preparation requirements.

/setup-mcp-connector --check

Output example:

[✅] Google Drive — 계정 확인 완료
[✅] Notion — 계정 확인 완료
[⚠️] Higgsfield — 워크스페이스 크레딧 충전 미확인 (충전 후 재시도)
[✅] kordoc — Node.js 18+ 확인 (키 불필요)
[⚠️] dart — OpenDART 키 미등록 (opendart.fss.or.kr 발급 필요)
[⚠️] dart — Node.js 20.19+ 미충족 (현재 v18.x)
[✅] korean-stats — 공용키 hosted (키 불필요)
[✅] archhub — 공용키 hosted (키 불필요)
[⚠️] korean-law — 법제처 OC 키 미등록 (law.go.kr 무료 발급, 사용자마다 키 필요)

Usage examples

Example 1

"Tell me how to connect Drive MCP"

→ Provide Connector A (Google Drive) authentication steps + guidance for one-time invocation verification

Example 2

"Cowork mount doesn't work on Windows"

→ Provide resolution for T1 (MAX_PATH error) + guidance on alternative paths

Output format

  • Step-by-step authentication guide (Markdown)
  • Troubleshooting resolutions (numbered list)
  • --check option: 3-connector status checklist (.md file can be saved)

Setup completion checklist

Connector / MCP Authentication method One-time invocation verification
Google Drive OAuth (drive.readonly, drive.file) Folder list response
Notion OAuth (workspace connection) Shared page read response
Higgsfield API Key Model list response
kordoc No key required (Node.js 18+) parse_document markdown response
dart (korean-dart-mcp) OpenDART key (40 characters, free/20,000 requests per day) resolve_corp_code response
korean-stats Public key hosted (no key required) quick_stats statistical figure response
archhub Public key hosted (no key required) find_region + building_profile response
korean-law Korean Law Information Center OC key (free, issued per user) search_law legal search response

If all 3 connectors + 5 MCPs authenticate successfully + one-time invocation succeeds, the setup is complete.

Related skills

  • moai-seller:commerce-morning-brief — After authentication is complete, store data morning briefing + new order integrated summary (order summary mode)
  • moai-media:media-higgsfield-image / moai-media:media-higgsfield-video — After Higgsfield connector authentication is complete, image/video generation
  • moai-officer:doc-reader — After kordoc MCP authentication is complete, HWP/HWPX/PDF/XLSX/DOCX parsing
  • moai-analyst:data-public — korean-stats MCP natural-language KOSIS statistics priority routing + dart MCP integration
  • moai-analyst:data-building-ledger — archhub MCP building register/permit actual data lookup
  • moai-lawyer:legal-law-research — korean-law MCP statutes/precedents/citation verification/law-at-the-time lookup

When not to use this skill

  • If all 3 connectors are already connected → moai-seller:commerce-morning-brief direct invocation (full briefing or order summary mode)
  • If the purpose is to generate MCP invocation outputs (morning briefing/order summary) → moai-seller use skill
  • If the Cowork app itself cannot be installed → contact the official Cowork support channel (outside the scope of this skill)
  • Ad platform connector (Meta Ads, etc.) connection → moai-marketer:marketing-meta-ads-manager skill reference