What features does Standard Korean Dictionary MCP server provide?

Q: What features does Standard Korean Dictionary MCP server provide?

Flexible search endpoint: Supports a broad set of search parameters (key, q, start, num, req_type, advanced, target, method, type1, type2, pos, cat, multimedia, letter_s, letter_e, update_s, update_e) for versatile dictionary querying.. Advanced search mode: Enables detailed searching when advanced=y, allowing finer control over result sets and matching behavior.. Detail retrieval endpoint: Provides detailed entry information via word_info or target_code for a given query, with required key and q.. Rich filtering options: Includes pos, cat, type1/type2 and other metadata filters to tailor results to linguistic categories and domains.. Pagination and result customization: Supports start and num to control offset and page size of search results.. XML/JSON response formats: Allows responses in either XML or JSON via req_type for interoperability.. API key authentication: Requires a 32-hexadecimal-character key to authenticate requests.. Claude Desktop integration sample: Includes a sample configuration snippet for integrating the API with Claude Desktop workflows.

Standard Korean Dictionary MCP Server 2025: Features & Setup Guide

Overview

The MCP server exposes two tools for accessing the Standard Korean Dictionary: search and detail. The search tool lets clients query the dictionary using a required API key and a UTF-8 encoded query string (q), with optional pagination (start, num) and format (req_type: xml or json). A comprehensive set of filters is available, including target fields (1–11), parts of speech (pos), semantic categories (cat), and multiple flags like type1/type2, multimedia, and date ranges (update_s/e). An advanced mode (advanced=y) enables more fine-grained searches and uses parameters like method (exact, include, start, end, wildcard). The detail tool retrieves detailed information about a dictionary entry using the word_info or target_code method, again requiring key and q, and supports xml/json outputs. All requests require the 32-digit hexadecimal API key, and responses can be XML or JSON. The server provides a sample setup for Claude Desktop integration and is licensed under MIT for code, with dictionary content governed by official licensing terms.

Features

Flexible search endpoint

Supports a broad set of search parameters (key, q, start, num, req_type, advanced, target, method, type1, type2, pos, cat, multimedia, letter_s, letter_e, update_s, update_e) for versatile dictionary querying.

Advanced search mode

Enables detailed searching when advanced=y, allowing finer control over result sets and matching behavior.

Detail retrieval endpoint

Provides detailed entry information via word_info or target_code for a given query, with required key and q.

Rich filtering options

Includes pos, cat, type1/type2 and other metadata filters to tailor results to linguistic categories and domains.

Pagination and result customization

Supports start and num to control offset and page size of search results.

XML/JSON response formats

Allows responses in either XML or JSON via req_type for interoperability.

API key authentication

Requires a 32-hexadecimal-character key to authenticate requests.

Claude Desktop integration sample

Includes a sample configuration snippet for integrating the API with Claude Desktop workflows.