MCP Tool Directory

Create a new or update an existing issue in a GitHub repository.

Article to legal term linkage (조문→법령용어 연계 조회). This tool searches the linkage from specific law articles to the legal terms defined or used within those articles. Useful for finding all technical terms in a given article. Args: query: Search keyword (default "*") display: Number of results per page (max 100, default 20) page: Page number (1-based, default 1) oc: Optional OC override (defaults to env var) type: Response format - "JSON" (default), "XML", or "HTML" ctx: MCP context (injected automatically) Returns: Search results or error

Retrieves keyword ideas and their associated SEO metrics by matching input terms or phrases in a specified country, with extensive support for filtering, sorting, and metric selection. Use doc tool first to get the real input schema.

Provides an overview of keyword metrics—including search volume, CPC, ranking difficulty, traffic potential, and intent—for specified keywords, domains, or URLs within a given country. Use doc tool first to get the real input schema.

Returns keyword metrics and related terms—such as "also rank for" keywords and "also talk about" keywords—for a given keyword or keyword list, with filtering and sorting options. Use doc tool first to get the real input schema.

Provides keyword search suggestions and related keyword metrics (e.g., search volume, difficulty, CPC) for specified queries or keyword lists, with options to filter, sort, and customize returned fields by country. Use doc tool first to get the real input schema.

Retrieves search volume metrics for a specified keyword broken down by country. Use doc tool first to get the real input schema.

Retrieves historical search volume data for a specified keyword within a given country and date range. Use doc tool first to get the real input schema.

Perform write operations on repository labels. To set labels on issues, use the 'update_issue' tool.

Convert latitude/longitude coordinates to map tile coordinates (x, y) for a given zoom level. Uses the same web mercator projection as MapKit.

List all revisions of a law within a date range (법령 개정 이력 조회). Shows when and how a law was amended over time. Use the MST values from the results with article_amendment_diff to see specific article changes. Args: law_name: Law name (e.g., "근로기준법") date_from: Start date YYYYMMDD (default "20100101") date_to: End date YYYYMMDD (default "20261231") oc: Optional OC override type: Response format - "JSON" (default), "XML", or "HTML" Returns: List of revisions with dates, types, and MST identifiers Examples: >>> law_amendment_summary(law_name="근로기준법", date_from="20200101") >>> law_amendment_summary(law_name="민법", date_from="20150101", date_to="20251231")

Query specific article/paragraph by announcement date (공포일 기준 조·항·호·목 조회). **BEST TOOL for querying specific articles like "제174조", "제3조" etc.** This returns only the requested article/paragraph, avoiding large full-law responses. Args: id: Law ID (either id or mst is required) mst: Law serial number (MST) jo: Article number in XXXXXX format. Format: first 4 digits = article number (zero-padded), last 2 digits = branch suffix (00=main). Examples: "017400" (제174조), "017200" (제172조), "000300" (제3조), "001502" (제15조의2) hang: Paragraph number (6 digits, e.g., "000100" for 제1항) ho: Item number (6 digits, e.g., "000200" for 제2호) mok: Subitem (UTF-8 encoded, e.g., "다" for 다목) oc: Optional OC override (defaults to env var) type: Response format - "JSON" (default), "XML", or "HTML" Returns: Specific law section content Examples: Query 자본시장법 제174조: >>> law_josub(mst="279823", jo="017400", type="XML") Query 건축법 제3조 제1항: >>> law_josub(mst="276925", jo="000300", hang="000100", type="XML")

Search current laws by announcement date (공포일 기준 현행법령 검색). This tool searches Korean laws organized by announcement (publication) date. Args: query: Search keyword (law name or content) display: Number of results per page (max 100, default 20). **Recommend 50-100 for law searches (법령 검색) to ensure exact matches are found.** page: Page number (1-based, default 1) oc: Optional OC override (defaults to env var) type: Response format - "JSON" (default), "XML", or "HTML" sort: Sort order date: Announcement date (YYYYMMDD) org: Ministry/department code filter knd: Law type filter Returns: Search results with law list or error

Retrieve full law content by announcement date (공포일 기준 법령 본문 조회). Retrieves the complete text of a law organized by announcement (publication) date. **IMPORTANT: For specific article queries (e.g., "제174조"), ALWAYS use the `jo` parameter. Some laws (e.g., 자본시장법) have 400+ articles and the full response can exceed 1MB. Using `jo` returns only the requested article, which is much faster and cleaner.** Args: id: Law ID (either id or mst is required) mst: Law serial number (MST) lm: Law modification parameter ld: Law date parameter (YYYYMMDD) ln: Law number parameter jo: **REQUIRED for specific articles.** Article number in XXXXXX format. Format: first 4 digits = article number (zero-padded), last 2 digits = branch suffix (00=main). Examples: "017400" (제174조), "017200" (제172조), "000300" (제3조), "001502" (제15조의2) lang: Language - "KO" (Korean) or "ORI" (Original) oc: Optional OC override (defaults to env var) type: Response format - "JSON" (default), "XML", or "HTML" Returns: Full law content or specific article content Examples: Retrieve specific article (RECOMMENDED): >>> law_service(mst="279823", jo="017400", type="XML") # 자본시장법 제174조 Retrieve full law (WARNING: large response for some laws): >>> law_service(id="009682", type="XML")

Find all applicable laws, precedents, and interpretations for a situation (법률 종합 분석). Given a plain language description of a legal situation, this tool searches across multiple legal databases in one call: law articles, court precedents, legal interpretations, and citation networks. Args: situation: Plain language description (e.g., "직원이 고객 데이터를 USB에 담아갔다") display: Results per sub-query (default 5) oc: Optional OC override type: Response format - "JSON" (default), "XML", or "HTML" Returns: Comprehensive legal analysis with applicable laws, precedents, interpretations, and citations Examples: >>> legal_resolver(situation="집주인이 보증금을 안 돌려줘요") >>> legal_resolver(situation="회사에서 갑자기 해고당했어요", display=3)

Fetch a URL and return the content of the page. If you are unable to fetch the page content, might be worth trying to render the JavaScript content.

Search the web in real time using Linkup to retrieve current information, facts, and news from trusted sources. Use this tool for: real-time data (weather, stocks, sports scores, events), breaking news, current events, recent research, product information, up-to-date prices, schedules, and any information not available in your knowledge base. Returns comprehensive content from the most relevant sources.

Get a list of all available voice archetypes with their names and descriptions

Get a list of available copywriting frameworks and their descriptions for a specific social media network

List your StacksFinder API keys.

List your tech debt audit reports. Shows name, status, health score, and creation date.

List your saved blueprints. Returns up to 50 most recent blueprints with their IDs, project names, and creation dates.

Lists all development branches of a Supabase project. This will return branch details including status which you can use to check when operations like merge/rebase/reset complete.

Lists all brands accessible to the current tenant with their relationship type.

List brands tracked in a project — includes the user's own brand and competitors. Use this tool to resolve brand names to IDs before filtering reports (brand_id filter), and to label brand IDs from report output with their human-readable names before presenting results. Returns columnar JSON: {columns, rows, rowCount}. Columns: id, name, domains, is_own. is_own indicates which brand belongs to the user.

List campaigns for a client (active/inactive, product mapping, budget, and warning signals).

List all 28 available Catalyst UI components organized by category. Categories include: forms (button, checkbox, fieldset, input, radio, select, switch, textarea), navigation (navbar, sidebar, dropdown, link), layout (divider, heading, stacked-layout, auth-layout), feedback (alert, badge, dialog), data-display (avatar, description-list, listbox, pagination, table, text), and advanced (combobox).

Lists content categories for a brand. Categories are used to organize published articles.

Lists all product categories in the directory. Use category slugs to filter product searches in search_products / find_products_with_capability. Response: array of { slug, name, description }. Note: this is a thin call — for a full directory briefing (subcategories, capability slugs per category, product counts), prefer the get_directory_overview entry-point once it ships (W8.2).

List chats (individual AI responses) for a project over a date range. Each chat is produced by running one prompt against one AI engine on a given date. Filters: - brand_id: only chats that mentioned the given brand - prompt_id: only chats produced by the given prompt - model_id: only chats from the given AI engine (chatgpt-scraper, gpt-4o, gpt-4o-search, gpt-3.5-turbo, llama-sonar, perplexity-scraper, sonar, gemini-2.5-flash, gemini-scraper, google-ai-overview-scraper, google-ai-mode-scraper, llama-3.3-70b-instruct, deepseek-r1, claude-3.5-haiku, claude-haiku-4.5, claude-sonnet-4, grok-scraper, microsoft-copilot-scraper, grok-4) Use the returned chat IDs with get_chat to retrieve full message content, sources, and brand mentions. Returns columnar JSON: {columns, rows, rowCount}. Columns: id, prompt_id, model_id, date.