국립국어원 표준국어대사전 MCP 서버

Created By
tenacla year ago
Overview

What is Koreandict MCP Server?

Koreandict MCP Server is a TypeScript package that provides the National Institute of Korean Language's standard Korean dictionary API as an MCP (Model Context Protocol) server, enabling large language models like Claude and ChatGPT to access and utilize Korean dictionary information.

How to use Koreandict MCP Server?

To use the Koreandict MCP Server, install it via NPM and set up your API key either through an environment variable or a configuration file. You can run the server directly from the command line or programmatically in your code.

Key features of Koreandict MCP Server?

  • Provides access to Korean dictionary data via MCP protocol.
  • Supports word search and part-of-speech specific searches.
  • Easy integration with MCP clients like Cursor.

Use cases of Koreandict MCP Server?

  1. Integrating Korean language support into applications using large language models.
  2. Enabling dictionary lookups in educational tools for Korean language learners.
  3. Providing a backend service for Korean language processing applications.

FAQ from Koreandict MCP Server?

  • How do I install the Koreandict MCP Server?

You can install it globally or locally using NPM with the command npm install -g koreandict-mcp-server or npm install koreandict-mcp-server.

  • What do I need to run the server?

You need to set up an API key from the National Institute of Korean Language and configure it in your environment or a JSON file.

  • Can I contribute to the project?

Yes! Contributions are welcome via issues and pull requests on the GitHub repository.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
tenacl
Star
0
Language
TypeScript
License
-

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)

a day ago