[{"_1":2,"_338":-5,"_339":-5},"loaderData",{"_3":4,"_22":23,"_24":25,"_238":239},"root",{"_5":6,"_7":8},"toasts",[],"visitor",{"_9":10,"_11":12},"viewportWidth",1280,"visitorSession",{"_13":14,"_16":17,"_18":-5,"_19":20,"_21":-5},"attributes",[15],"BOT","id",8780354,"membership","referenceId","0197c85f-34b4-7020-804a-1f56d7353f19","userAccount","routes/_public/_layout",{},"routes/_public/mcp/servers/~namespace/~slug/_pages/_layout",{"_26":27,"_68":-5,"_69":28,"_29":70,"_156":157,"_237":120},"availableLocales",[28,40,47,54,61],{"_29":30,"_33":37,"_38":39},"mcpServer",{"_31":32,"_33":34,"_35":36},"description","Enables MCP-capable applications to access, manage, and analyze system core dumps through integration with systemd-coredump functionality.","name","systemd-coredump MCP Server","readme","# systemd-coredump MCP Server\n\nA Model Context Protocol (MCP) server for interacting with systemd-coredump functionality. This enables MCP-capable applications to access, manage, and analyze system core dumps.\n\n[![npm version](https://img.shields.io/npm/v/@taskjp/server-systemd-coredump.svg?v=0.1.1)](https://www.npmjs.com/package/@taskjp/server-systemd-coredump)\n[![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT)\n\n## Features\n\n- List all available coredumps in the system\n- Get detailed information about specific coredumps\n- Extract coredump files to a specified location\n- Remove coredumps from the system\n\n## Prerequisites\n\n- Node.js 18+ and npm\n- systemd-coredump must be installed and configured on the system\n- `coredumpctl` command-line utility must be available\n\n## Installation\n\n### From npm (recommended)\n\n#### Global Installation\n\n```bash\nnpm install -g @taskjp/server-systemd-coredump\n```\n\n#### Local Installation\n\n```bash\nnpm install @taskjp/server-systemd-coredump\n```\n\n### From Source\n\n1. Clone the repository or download the source code\n2. Install dependencies:\n\n```bash\ncd systemd-coredump-server\nnpm install\n```\n\n3. Build the server:\n\n```bash\nnpm run build\n```\n\n## Configuration\n\nAdd the server to your MCP settings configuration file:\n\n### If installed from npm globally:\n\n```json\n\"systemd-coredump\": {\n \"command\": \"systemd-coredump-server\",\n \"args\": [],\n \"disabled\": false,\n \"autoApprove\": []\n}\n```\n\n### If installed from npm locally:\n\n```json\n\"systemd-coredump\": {\n \"command\": \"node\",\n \"args\": [\"node_modules/@taskjp/server-systemd-coredump/build/index.js\"],\n \"disabled\": false,\n \"autoApprove\": []\n}\n```\n\n### If installed from source:\n\n```json\n\"systemd-coredump\": {\n \"command\": \"node\",\n \"args\": [\"/path/to/systemd-coredump-server/build/index.js\"],\n \"disabled\": false,\n \"autoApprove\": []\n}\n```\n\n## Usage\n\n### Available Tools\n\nThe server provides the following tools:\n\n1. **list_coredumps**: List all available coredumps in the system\n\n ```json\n {\n \"name\": \"list_coredumps\"\n }\n ```\n\n2. **get_coredump_info**: Get detailed information about a specific coredump\n\n ```json\n {\n \"name\": \"get_coredump_info\",\n \"arguments\": {\n \"id\": \"2023-04-20 12:34:56-12345\"\n }\n }\n ```\n\n3. **extract_coredump**: Extract a coredump to a file\n\n ```json\n {\n \"name\": \"extract_coredump\",\n \"arguments\": {\n \"id\": \"2023-04-20 12:34:56-12345\",\n \"outputPath\": \"/path/to/output/core.dump\"\n }\n }\n ```\n\n4. **remove_coredump**: Remove a coredump from the system\n\n ```json\n {\n \"name\": \"remove_coredump\",\n \"arguments\": {\n \"id\": \"2023-04-20 12:34:56-12345\"\n }\n }\n ```\n\n5. **get_coredump_config**: Get the current core dump configuration of the system\n\n ```json\n {\n \"name\": \"get_coredump_config\"\n }\n ```\n\n This tool returns information about the current core dump configuration, including:\n - Whether core dumps are enabled\n - The current core pattern\n - The core size limit\n - Whether systemd is handling the core dumps\n\n6. **set_coredump_enabled**: Enable or disable core dump generation\n\n ```json\n {\n \"name\": \"set_coredump_enabled\",\n \"arguments\": {\n \"enabled\": true\n }\n }\n ```\n\n Setting `enabled` to `true` will enable core dumps, while `false` will disable them.\n Note: This changes the ulimit settings for the current shell. For permanent system-wide\n changes, root privileges and modification of system configuration files would be required.\n\n7. **get_stacktrace**: Get stack trace from a coredump using GDB\n\n ```json\n {\n \"name\": \"get_stacktrace\",\n \"arguments\": {\n \"id\": \"2023-04-20 12:34:56-12345\"\n }\n }\n ```\n\n This tool uses GDB to extract a formatted stack trace from the coredump.\n Note: Requires the GDB debugger to be installed on the system.\n\n### Available Resources\n\nThe server exposes two types of resources:\n\n1. **Coredump Information**\n - URI format: `coredump:///`\n - Returns JSON with detailed coredump information\n\n2. **Stack Traces**\n - URI format: `stacktrace:///`\n - Returns a formatted stack trace from the coredump\n\nWhere `` is the unique identifier for a coredump in the format: `-`.\n\nFor example:\n\n```\ncoredump:///2023-04-20 12:34:56-12345\nstacktrace:///2023-04-20 12:34:56-12345\n```\n\n## Note on Permissions\n\nSome operations may require elevated privileges, especially when extracting or removing coredumps. Ensure the user running the MCP server has appropriate permissions to access system coredumps.\n\n## License\n\nMIT\n","English","tag","en-US",{"_29":41,"_33":45,"_38":46},{"_31":42,"_33":43,"_35":44},"Permite que las aplicaciones compatibles con MCP accedan, administren y analicen volcados de núcleo del sistema a través de la integración con la funcionalidad systemd-coredump.","Servidor MCP systemd-coredump","# Servidor MCP systemd-coredump\n\nUn servidor de Protocolo de Contexto de Modelo (MCP) para interactuar con la funcionalidad systemd-coredump. Esto permite que las aplicaciones compatibles con MCP accedan, administren y analicen los volcados de memoria del sistema.\n\n[![versión npm](https://img.shields.io/npm/v/@taskjp/server-systemd-coredump.svg?v=0.1.1)](https://www.npmjs.com/package/@taskjp/server-systemd-coredump) [![Licencia: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT)\n\n## Características\n\n* Enumere todos los volcados de núcleo disponibles en el sistema\n* Obtenga información detallada sobre volcados de núcleo específicos\n* Extraer archivos de volcado de núcleo a una ubicación específica\n* Eliminar volcados de núcleo del sistema\n\n## Prerrequisitos\n\n* Node.js 18+ y npm\n* systemd-coredump debe estar instalado y configurado en el sistema\n* La utilidad de línea de comandos `coredumpctl` debe estar disponible\n\n## Instalación\n\n### De npm (recomendado)\n\n#### Instalación global\n\n```bash\nnpm install -g @taskjp/server-systemd-coredump\n```\n\n#### Instalación local\n\n```bash\nnpm install @taskjp/server-systemd-coredump\n```\n\n### De la fuente\n\n1. Clonar el repositorio o descargar el código fuente\n2. Instalar dependencias:\n\n```bash\ncd systemd-coredump-server\nnpm install\n```\n\n3. Construir el servidor:\n\n```bash\nnpm run build\n```\n\n## Configuración\n\nAgregue el servidor a su archivo de configuración de MCP:\n\n### Si se instala desde npm globalmente:\n\n```json\n\"systemd-coredump\": {\n \"command\": \"systemd-coredump-server\",\n \"args\": [],\n \"disabled\": false,\n \"autoApprove\": []\n}\n```\n\n### Si se instala desde npm localmente:\n\n```json\n\"systemd-coredump\": {\n \"command\": \"node\",\n \"args\": [\"node_modules/@taskjp/server-systemd-coredump/build/index.js\"],\n \"disabled\": false,\n \"autoApprove\": []\n}\n```\n\n### Si se instala desde la fuente:\n\n```json\n\"systemd-coredump\": {\n \"command\": \"node\",\n \"args\": [\"/path/to/systemd-coredump-server/build/index.js\"],\n \"disabled\": false,\n \"autoApprove\": []\n}\n```\n\n## Uso\n\n### Herramientas disponibles\n\nEl servidor proporciona las siguientes herramientas:\n\n1. **list\\_coredumps** : enumera todos los volcados de núcleo disponibles en el sistema\n\n ```json\n {\n \"name\": \"list_coredumps\"\n }\n ```\n\n2. **get\\_coredump\\_info** : Obtenga información detallada sobre un volcado de núcleo específico\n\n ```json\n {\n \"name\": \"get_coredump_info\",\n \"arguments\": {\n \"id\": \"2023-04-20 12:34:56-12345\"\n }\n }\n ```\n\n3. **extract\\_coredump** : Extrae un volcado de núcleo a un archivo\n\n ```json\n {\n \"name\": \"extract_coredump\",\n \"arguments\": {\n \"id\": \"2023-04-20 12:34:56-12345\",\n \"outputPath\": \"/path/to/output/core.dump\"\n }\n }\n ```\n\n4. **remove\\_coredump** : elimina un volcado de núcleo del sistema\n\n ```json\n {\n \"name\": \"remove_coredump\",\n \"arguments\": {\n \"id\": \"2023-04-20 12:34:56-12345\"\n }\n }\n ```\n\n5. **get\\_coredump\\_config** : obtiene la configuración actual del volcado de núcleo del sistema\n\n ```json\n {\n \"name\": \"get_coredump_config\"\n }\n ```\n\n Esta herramienta devuelve información sobre la configuración actual del volcado de núcleo, incluyendo:\n\n * Si los volcados de memoria están habilitados\n * El patrón central actual\n * El límite del tamaño del núcleo\n * Si systemd está manejando los volcados de núcleo\n\n6. **set\\_coredump\\_enabled** : Habilitar o deshabilitar la generación de volcado de núcleo\n\n ```json\n {\n \"name\": \"set_coredump_enabled\",\n \"arguments\": {\n \"enabled\": true\n }\n }\n ```\n\n Si se configura como `enabled` \" ( `true` , se habilitarán los volcados de memoria, mientras que `false` los deshabilitará. Nota: Esto cambia la configuración de ulimit para el shell actual. Para realizar cambios permanentes en todo el sistema, se requieren privilegios de root y la modificación de los archivos de configuración del sistema.\n\n7. **get\\_stacktrace** : Obtener el seguimiento de la pila de un volcado de núcleo usando GDB\n\n ```json\n {\n \"name\": \"get_stacktrace\",\n \"arguments\": {\n \"id\": \"2023-04-20 12:34:56-12345\"\n }\n }\n ```\n\n Esta herramienta utiliza GDB para extraer un seguimiento de pila formateado del volcado de núcleo. Nota: Requiere que el depurador de GDB esté instalado en el sistema.\n\n### Recursos disponibles\n\nEl servidor expone dos tipos de recursos:\n\n1. **Información del volcado de núcleo**\n\n * Formato de URI: `coredump:///`\n * Devuelve JSON con información detallada del volcado de núcleo\n\n2. **Rastreos de pila**\n\n * Formato de URI: `stacktrace:///`\n * Devuelve un seguimiento de pila formateado del volcado de núcleo\n\nDonde `` es el identificador único para un volcado de núcleo en el formato: `-` .\n\nPor ejemplo:\n\n```\ncoredump:///2023-04-20 12:34:56-12345\nstacktrace:///2023-04-20 12:34:56-12345\n```\n\n## Nota sobre los permisos\n\nAlgunas operaciones pueden requerir privilegios elevados, especialmente al extraer o eliminar volcados de memoria. Asegúrese de que el usuario que ejecuta el servidor MCP tenga los permisos adecuados para acceder a los volcados de memoria del sistema.\n\n## Licencia\n\nInstituto Tecnológico de Massachusetts (MIT)","Spanish","es-ES",{"_29":48,"_33":52,"_38":53},{"_31":49,"_33":50,"_35":51},"MCP 対応アプリケーションが systemd-coredump 機能との統合を通じてシステムコアダンプにアクセスし、管理および分析できるようにします。","systemd-coredump MCP サーバー","# systemd-coredump MCP サーバー\n\nsystemd-coredump 機能と連携するための Model Context Protocol (MCP) サーバー。これにより、MCP 対応アプリケーションはシステムコアダンプにアクセスし、管理および分析できるようになります。\n\n[![npmバージョン](https://img.shields.io/npm/v/@taskjp/server-systemd-coredump.svg?v=0.1.1)](https://www.npmjs.com/package/@taskjp/server-systemd-coredump) [![ライセンス: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT)\n\n## 特徴\n\n* システムで利用可能なすべてのコアダンプを一覧表示します\n* 特定のコアダンプに関する詳細情報を取得する\n* コアダンプファイルを指定された場所に抽出する\n* システムからコアダンプを削除する\n\n## 前提条件\n\n* Node.js 18+ および npm\n* systemd-coredumpがシステムにインストールされ設定されている必要があります\n* `coredumpctl`コマンドラインユーティリティが利用可能である必要があります\n\n## インストール\n\n### npmから（推奨）\n\n#### グローバルインストール\n\n```bash\nnpm install -g @taskjp/server-systemd-coredump\n```\n\n#### ローカルインストール\n\n```bash\nnpm install @taskjp/server-systemd-coredump\n```\n\n### ソースから\n\n1. リポジトリをクローンするか、ソースコードをダウンロードする\n2. 依存関係をインストールします:\n\n```bash\ncd systemd-coredump-server\nnpm install\n```\n\n3. サーバーを構築します。\n\n```bash\nnpm run build\n```\n\n## 構成\n\nMCP 設定構成ファイルにサーバーを追加します。\n\n### npm からグローバルにインストールした場合:\n\n```json\n\"systemd-coredump\": {\n \"command\": \"systemd-coredump-server\",\n \"args\": [],\n \"disabled\": false,\n \"autoApprove\": []\n}\n```\n\n### npm からローカルにインストールした場合:\n\n```json\n\"systemd-coredump\": {\n \"command\": \"node\",\n \"args\": [\"node_modules/@taskjp/server-systemd-coredump/build/index.js\"],\n \"disabled\": false,\n \"autoApprove\": []\n}\n```\n\n### ソースからインストールした場合:\n\n```json\n\"systemd-coredump\": {\n \"command\": \"node\",\n \"args\": [\"/path/to/systemd-coredump-server/build/index.js\"],\n \"disabled\": false,\n \"autoApprove\": []\n}\n```\n\n## 使用法\n\n### 利用可能なツール\n\nサーバーは次のツールを提供します。\n\n1. **list\\_coredumps** : システムで利用可能なすべてのコアダンプを一覧表示します\n\n ```json\n {\n \"name\": \"list_coredumps\"\n }\n ```\n\n2. **get\\_coredump\\_info** : 特定のコアダンプの詳細情報を取得する\n\n ```json\n {\n \"name\": \"get_coredump_info\",\n \"arguments\": {\n \"id\": \"2023-04-20 12:34:56-12345\"\n }\n }\n ```\n\n3. **extract\\_coredump** : コアダンプをファイルに抽出する\n\n ```json\n {\n \"name\": \"extract_coredump\",\n \"arguments\": {\n \"id\": \"2023-04-20 12:34:56-12345\",\n \"outputPath\": \"/path/to/output/core.dump\"\n }\n }\n ```\n\n4. **Remove\\_coredump** : システムからコアダンプを削除する\n\n ```json\n {\n \"name\": \"remove_coredump\",\n \"arguments\": {\n \"id\": \"2023-04-20 12:34:56-12345\"\n }\n }\n ```\n\n5. **get\\_coredump\\_config** : システムの現在のコアダンプ設定を取得します。\n\n ```json\n {\n \"name\": \"get_coredump_config\"\n }\n ```\n\n このツールは、次のような現在のコアダンプ構成に関する情報を返します。\n\n * コアダンプが有効かどうか\n * 現在のコアパターン\n * コアサイズの制限\n * systemdがコアダンプを処理しているかどうか\n\n6. **set\\_coredump\\_enabled** : コアダンプの生成を有効または無効にする\n\n ```json\n {\n \"name\": \"set_coredump_enabled\",\n \"arguments\": {\n \"enabled\": true\n }\n }\n ```\n\n `enabled`を`true`に設定するとコアダンプが有効になり、 `false`に設定すると無効になります。注: これにより、現在のシェルの ulimit 設定が変更されます。システム全体に永続的な変更を加えるには、root 権限とシステム設定ファイルの変更が必要になります。\n\n7. **get\\_stacktrace** : GDB を使用してコアダンプからスタックトレースを取得する\n\n ```json\n {\n \"name\": \"get_stacktrace\",\n \"arguments\": {\n \"id\": \"2023-04-20 12:34:56-12345\"\n }\n }\n ```\n\n このツールはGDBを使用して、コアダンプからフォーマットされたスタックトレースを抽出します。注: システムにGDBデバッガーがインストールされている必要があります。\n\n### 利用可能なリソース\n\nサーバーは次の 2 種類のリソースを公開します。\n\n1. **コアダンプ情報**\n\n * URI 形式: `coredump:///`\n * 詳細なコアダンプ情報を含むJSONを返します\n\n2. **スタックトレース**\n\n * URI 形式: `stacktrace:///`\n * コアダンプからフォーマットされたスタックトレースを返します\n\nここで、 ``は、 `-`という形式のコアダンプの一意の識別子です。\n\n例えば：\n\n```\ncoredump:///2023-04-20 12:34:56-12345\nstacktrace:///2023-04-20 12:34:56-12345\n```\n\n## 権限に関する注意\n\n一部の操作、特にコアダンプの抽出や削除には、昇格した権限が必要になる場合があります。MCPサーバーを実行しているユーザーが、システムコアダンプにアクセスするための適切な権限を持っていることを確認してください。\n\n## ライセンス\n\nマサチューセッツ工科大学","Japanese","ja-JP",{"_29":55,"_33":59,"_38":60},{"_31":56,"_33":57,"_35":58},"systemd-coredump 기능과 통합하여 MCP 지원 애플리케이션이 시스템 코어 덤프에 액세스하고 이를 관리하고 분석할 수 있도록 합니다.","systemd-coredump MCP 서버","# systemd-coredump MCP 서버\n\nsystemd-coredump 기능과 상호 작용하는 모델 컨텍스트 프로토콜(MCP) 서버입니다. 이를 통해 MCP 지원 애플리케이션은 시스템 코어 덤프에 접근, 관리 및 분석할 수 있습니다.\n\n[![npm 버전](https://img.shields.io/npm/v/@taskjp/server-systemd-coredump.svg?v=0.1.1)](https://www.npmjs.com/package/@taskjp/server-systemd-coredump) [![라이센스: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT)\n\n## 특징\n\n* 시스템에서 사용 가능한 모든 코어덤프를 나열합니다.\n* 특정 코어덤프에 대한 자세한 정보를 얻으세요\n* 지정된 위치에 코어덤프 파일 추출\n* 시스템에서 코어덤프 제거\n\n## 필수 조건\n\n* Node.js 18+ 및 npm\n* systemd-coredump는 시스템에 설치 및 구성되어야 합니다.\n* `coredumpctl` 명령줄 유틸리티를 사용할 수 있어야 합니다.\n\n## 설치\n\n### npm에서 (권장)\n\n#### 글로벌 설치\n\n지엑스피1\n\n#### 로컬 설치\n\n```bash\nnpm install @taskjp/server-systemd-coredump\n```\n\n### 출처에서\n\n1. 저장소를 복제하거나 소스 코드를 다운로드하세요\n2. 종속성 설치:\n\n```bash\ncd systemd-coredump-server\nnpm install\n```\n\n3. 서버를 빌드하세요:\n\n```bash\nnpm run build\n```\n\n## 구성\n\nMCP 설정 구성 파일에 서버를 추가합니다.\n\n### npm에서 전역적으로 설치하는 경우:\n\n```json\n\"systemd-coredump\": {\n \"command\": \"systemd-coredump-server\",\n \"args\": [],\n \"disabled\": false,\n \"autoApprove\": []\n}\n```\n\n### 로컬로 npm에서 설치한 경우:\n\n```json\n\"systemd-coredump\": {\n \"command\": \"node\",\n \"args\": [\"node_modules/@taskjp/server-systemd-coredump/build/index.js\"],\n \"disabled\": false,\n \"autoApprove\": []\n}\n```\n\n### 소스에서 설치한 경우:\n\n```json\n\"systemd-coredump\": {\n \"command\": \"node\",\n \"args\": [\"/path/to/systemd-coredump-server/build/index.js\"],\n \"disabled\": false,\n \"autoApprove\": []\n}\n```\n\n## 용법\n\n### 사용 가능한 도구\n\n서버는 다음과 같은 도구를 제공합니다.\n\n1. **list\\_coredumps** : 시스템에서 사용 가능한 모든 코어덤프를 나열합니다.\n\n ```json\n {\n \"name\": \"list_coredumps\"\n }\n ```\n\n2. **get\\_coredump\\_info** : 특정 코어덤프에 대한 자세한 정보를 가져옵니다.\n\n ```json\n {\n \"name\": \"get_coredump_info\",\n \"arguments\": {\n \"id\": \"2023-04-20 12:34:56-12345\"\n }\n }\n ```\n\n3. **extract\\_coredump** : 코어덤프를 파일로 추출합니다.\n\n ```json\n {\n \"name\": \"extract_coredump\",\n \"arguments\": {\n \"id\": \"2023-04-20 12:34:56-12345\",\n \"outputPath\": \"/path/to/output/core.dump\"\n }\n }\n ```\n\n4. **remove\\_coredump** : 시스템에서 코어덤프를 제거합니다.\n\n ```json\n {\n \"name\": \"remove_coredump\",\n \"arguments\": {\n \"id\": \"2023-04-20 12:34:56-12345\"\n }\n }\n ```\n\n5. **get\\_coredump\\_config** : 시스템의 현재 코어 덤프 구성을 가져옵니다.\n\n ```json\n {\n \"name\": \"get_coredump_config\"\n }\n ```\n\n 이 도구는 다음을 포함하여 현재 코어 덤프 구성에 대한 정보를 반환합니다.\n\n * 코어 덤프가 활성화되어 있는지 여부\n * 현재 핵심 패턴\n * 코어 크기 제한\n * systemd가 코어 덤프를 처리하는지 여부\n\n6. **set\\_coredump\\_enabled** : 코어 덤프 생성을 활성화하거나 비활성화합니다.\n\n ```json\n {\n \"name\": \"set_coredump_enabled\",\n \"arguments\": {\n \"enabled\": true\n }\n }\n ```\n\n `enabled` 를 `true` 로 설정하면 코어 덤프가 활성화되고, `false` 로 설정하면 코어 덤프가 비활성화됩니다. 참고: 이 설정은 현재 셸의 ulimit 설정을 변경합니다. 시스템 전체에 영구적인 변경을 적용하려면 루트 권한과 시스템 설정 파일 수정이 필요합니다.\n\n7. **get\\_stacktrace** : GDB를 사용하여 코어덤프에서 스택 추적을 가져옵니다.\n\n ```json\n {\n \"name\": \"get_stacktrace\",\n \"arguments\": {\n \"id\": \"2023-04-20 12:34:56-12345\"\n }\n }\n ```\n\n 이 도구는 GDB를 사용하여 코어 덤프에서 포맷된 스택 추적을 추출합니다. 참고: 시스템에 GDB 디버거가 설치되어 있어야 합니다.\n\n### 사용 가능한 리소스\n\n서버는 두 가지 유형의 리소스를 노출합니다.\n\n1. **코어덤프 정보**\n\n * URI 형식: `coredump:///`\n * 자세한 코어덤프 정보가 포함된 JSON을 반환합니다.\n\n2. **스택 추적**\n\n * URI 형식: `stacktrace:///`\n * 코어덤프에서 포맷된 스택 추적을 반환합니다.\n\n여기서 `` `-` 형식의 코어덤프에 대한 고유 식별자입니다.\n\n예를 들어:\n\n```\ncoredump:///2023-04-20 12:34:56-12345\nstacktrace:///2023-04-20 12:34:56-12345\n```\n\n## 권한에 대한 참고 사항\n\n일부 작업, 특히 코어 덤프를 추출하거나 제거하는 경우 높은 권한이 필요할 수 있습니다. MCP 서버를 실행하는 사용자에게 시스템 코어 덤프에 액세스할 수 있는 적절한 권한이 있는지 확인하십시오.\n\n## 특허\n\nMIT","Korean","ko-KR",{"_29":62,"_33":66,"_38":67},{"_31":63,"_33":64,"_35":65},"通过与 systemd-coredump 功能集成，使支持 MCP 的应用程序能够访问、管理和分析系统核心转储。","systemd-coredump MCP 服务器","# systemd-coredump MCP 服务器\n\n用于与 systemd-coredump 功能交互的模型上下文协议 (MCP) 服务器。这使得支持 MCP 的应用程序能够访问、管理和分析系统核心转储。\n\n[![npm 版本](https://img.shields.io/npm/v/@taskjp/server-systemd-coredump.svg?v=0.1.1)](https://www.npmjs.com/package/@taskjp/server-systemd-coredump) [![许可证：MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT)\n\n## 特征\n\n* 列出系统中所有可用的 coredump\n* 获取有关特定核心转储的详细信息\n* 将 coredump 文件提取到指定位置\n* 从系统中删除核心转储\n\n## 先决条件\n\n* Node.js 18+ 和 npm\n* 必须在系统上安装并配置 systemd-coredump\n* `coredumpctl`命令行实用程序必须可用\n\n## 安装\n\n### 来自 npm（推荐）\n\n#### 全局安装\n\n```bash\nnpm install -g @taskjp/server-systemd-coredump\n```\n\n#### 本地安装\n\n```bash\nnpm install @taskjp/server-systemd-coredump\n```\n\n### 来自源\n\n1. 克隆存储库或下载源代码\n2. 安装依赖项：\n\n```bash\ncd systemd-coredump-server\nnpm install\n```\n\n3. 构建服务器：\n\n```bash\nnpm run build\n```\n\n## 配置\n\n将服务器添加到您的 MCP 设置配置文件：\n\n### 如果从 npm 全局安装：\n\n```json\n\"systemd-coredump\": {\n \"command\": \"systemd-coredump-server\",\n \"args\": [],\n \"disabled\": false,\n \"autoApprove\": []\n}\n```\n\n### 如果从 npm 本地安装：\n\n```json\n\"systemd-coredump\": {\n \"command\": \"node\",\n \"args\": [\"node_modules/@taskjp/server-systemd-coredump/build/index.js\"],\n \"disabled\": false,\n \"autoApprove\": []\n}\n```\n\n### 如果从源安装：\n\n```json\n\"systemd-coredump\": {\n \"command\": \"node\",\n \"args\": [\"/path/to/systemd-coredump-server/build/index.js\"],\n \"disabled\": false,\n \"autoApprove\": []\n}\n```\n\n## 用法\n\n### 可用工具\n\n该服务器提供以下工具：\n\n1. **list\\_coredumps** ：列出系统中所有可用的 coredump\n\n ```json\n {\n \"name\": \"list_coredumps\"\n }\n ```\n\n2. **get\\_coredump\\_info** ：获取有关特定 coredump 的详细信息\n\n ```json\n {\n \"name\": \"get_coredump_info\",\n \"arguments\": {\n \"id\": \"2023-04-20 12:34:56-12345\"\n }\n }\n ```\n\n3. **extract\\_coredump** ：将核心转储提取到文件\n\n ```json\n {\n \"name\": \"extract_coredump\",\n \"arguments\": {\n \"id\": \"2023-04-20 12:34:56-12345\",\n \"outputPath\": \"/path/to/output/core.dump\"\n }\n }\n ```\n\n4. **remove\\_coredump** ：从系统中删除核心转储\n\n ```json\n {\n \"name\": \"remove_coredump\",\n \"arguments\": {\n \"id\": \"2023-04-20 12:34:56-12345\"\n }\n }\n ```\n\n5. **get\\_coredump\\_config** ：获取系统当前的核心转储配置\n\n ```json\n {\n \"name\": \"get_coredump_config\"\n }\n ```\n\n 此工具返回有关当前核心转储配置的信息，包括：\n\n * 是否启用核心转储\n * 当前的核心模式\n * 核心尺寸限制\n * systemd 是否正在处理核心转储\n\n6. **set\\_coredump\\_enabled** ：启用或禁用核心转储生成\n\n ```json\n {\n \"name\": \"set_coredump_enabled\",\n \"arguments\": {\n \"enabled\": true\n }\n }\n ```\n\n 将`enabled`设置为`true`将启用核心转储，设置为`false`将禁用核心转储。注意：这将更改当前 shell 的 ulimit 设置。要进行永久性的系统级更改，需要 root 权限并修改系统配置文件。\n\n7. **get\\_stacktrace** ：使用 GDB 从 coredump 获取堆栈跟踪\n\n ```json\n {\n \"name\": \"get_stacktrace\",\n \"arguments\": {\n \"id\": \"2023-04-20 12:34:56-12345\"\n }\n }\n ```\n\n 此工具使用 GDB 从核心转储中提取格式化的堆栈跟踪信息。注意：需要在系统上安装 GDB 调试器。\n\n### 可用资源\n\n服务器公开两种类型的资源：\n\n1. **核心转储信息**\n\n * URI 格式： `coredump:///`\n * 返回包含详细核心转储信息的 JSON\n\n2. **堆栈跟踪**\n\n * URI 格式： `stacktrace:///`\n * 从核心转储返回格式化的堆栈跟踪\n\n其中``是核心转储的唯一标识符，格式为： `-` 。\n\n例如：\n\n```\ncoredump:///2023-04-20 12:34:56-12345\nstacktrace:///2023-04-20 12:34:56-12345\n```\n\n## 关于权限的说明\n\n某些操作可能需要提升权限，尤其是在提取或删除核心转储时。请确保运行 MCP 服务器的用户拥有访问系统核心转储的相应权限。\n\n## 执照\n\n麻省理工学院","Chinese","zh-CN","githubUser","locale",{"_71":72,"_73":74,"_13":81,"_89":32,"_90":32,"_91":92,"_95":96,"_117":-5,"_16":118,"_119":120,"_121":122,"_33":34,"_133":109,"_134":135,"_139":-5,"_140":141,"_142":-5,"_143":144,"_148":-5,"_129":105,"_149":150,"_152":-5,"_110":153,"_154":155},"addedAt","2025-03-08T23:17:41.961961739Z","argumentsJsonSchema",{"_75":76,"_77":78,"_79":80},"properties",{},"required",[],"type","object",[82,83,84,85,86,87,88],"category:os-automation","category:monitoring","category:developer-tools","environment:local","hosting:local-only","language:javascript","license_grade:f","descriptionMarkdown","descriptionPlainText","githubProject",{"_35":36,"_93":94},"url","https://github.com/signal-slot/mcp-systemd-coredump","githubRepository",{"_97":98,"_99":100,"_101":102,"_103":104,"_33":105,"_106":107,"_112":113,"_114":-5,"_115":116},"defaultBranch","main","fullName","signal-slot/mcp-systemd-coredump","githubTreeId",73674,"language","JavaScript","mcp-systemd-coredump","owner",{"_108":109,"_110":111},"login","signal-slot","uid","TojtzakY9L","recentStargazers",0,"spdxLicense","stargazers",1,"glamaJson",1266,"inspectable",false,"integrations",[123],{"_124":125,"_31":131,"_110":132},"brand",{"_126":127,"_33":128,"_129":130},"logoSvgPath","M11.998,24c-0.321,0-0.641-0.084-0.922-0.247l-2.936-1.737c-0.438-0.245-0.224-0.332-0.08-0.383 c0.585-0.203,0.703-0.25,1.328-0.604c0.065-0.037,0.151-0.023,0.218,0.017l2.256,1.339c0.082,0.045,0.197,0.045,0.272,0l8.795-5.076 c0.082-0.047,0.134-0.141,0.134-0.238V6.921c0-0.099-0.053-0.192-0.137-0.242l-8.791-5.072c-0.081-0.047-0.189-0.047-0.271,0 L3.075,6.68C2.99,6.729,2.936,6.825,2.936,6.921v10.15c0,0.097,0.054,0.189,0.139,0.235l2.409,1.392 c1.307,0.654,2.108-0.116,2.108-0.89V7.787c0-0.142,0.114-0.253,0.256-0.253h1.115c0.139,0,0.255,0.112,0.255,0.253v10.021 c0,1.745-0.95,2.745-2.604,2.745c-0.508,0-0.909,0-2.026-0.551L2.28,18.675c-0.57-0.329-0.922-0.945-0.922-1.604V6.921 c0-0.659,0.353-1.275,0.922-1.603l8.795-5.082c0.557-0.315,1.296-0.315,1.848,0l8.794,5.082c0.57,0.329,0.924,0.944,0.924,1.603 v10.15c0,0.659-0.354,1.273-0.924,1.604l-8.794,5.078C12.643,23.916,12.324,24,11.998,24z M19.099,13.993 c0-1.9-1.284-2.406-3.987-2.763c-2.731-0.361-3.009-0.548-3.009-1.187c0-0.528,0.235-1.233,2.258-1.233 c1.807,0,2.473,0.389,2.747,1.607c0.024,0.115,0.129,0.199,0.247,0.199h1.141c0.071,0,0.138-0.031,0.186-0.081 c0.048-0.054,0.074-0.123,0.067-0.196c-0.177-2.098-1.571-3.076-4.388-3.076c-2.508,0-4.004,1.058-4.004,2.833 c0,1.925,1.488,2.457,3.895,2.695c2.88,0.282,3.103,0.703,3.103,1.269c0,0.983-0.789,1.402-2.642,1.402 c-2.327,0-2.839-0.584-3.011-1.742c-0.02-0.124-0.126-0.215-0.253-0.215h-1.137c-0.141,0-0.254,0.112-0.254,0.253 c0,1.482,0.806,3.248,4.655,3.248C17.501,17.007,19.099,15.91,19.099,13.993z","Node.js","slug","node-dot-js","Enables interaction with systemd-coredump functionality to access, manage, and analyze system core dumps. Provides tools for listing, extracting, and removing coredumps, as well as getting detailed information and stack traces from coredumps using GDB.","im1zudkqpn","namespace","npmPackage",{"_33":136,"_137":138},"@taskjp/server-systemd-coredump","weeklyDownloads",5,"prompts","redditPostForeignId","1j6tyxl","resources","scores",{"_145":113,"_146":-5,"_147":-5},"license","quality","security","simpleIcon","supportedPlatforms",[151],"LINUX","tools","m7kiwah6mm","updatedAt","2025-03-21T19:39:58.690690416Z","meta",[158,161,163,170,173,175,178,181,184,187,190,192,195,198,200,202,204,206,208],{"_159":160},"title","systemd-coredump MCP Server | Glama",{"_162":32,"_33":31},"content",{"_164":165,"_166":167,"_168":169},"href","https://glama.ai/mcp/servers/@signal-slot/mcp-systemd-coredump","rel","canonical","tagName","link",{"_162":34,"_171":172},"property","og:title",{"_162":32,"_171":174},"og:description",{"_162":176,"_171":177},"https://glama.ai/logo.png","og:logo",{"_162":179,"_171":180},"https://glama.ai/mcp/servers/@signal-slot/mcp-systemd-coredump/og-image","og:image",{"_162":182,"_171":183},"630","og:image:height",{"_162":185,"_171":186},"1200","og:image:width",{"_162":188,"_171":189},"website","og:type",{"_162":165,"_171":191},"og:url",{"_162":193,"_171":194},"Glama – MCP Hosting Platform","og:site_name",{"_162":196,"_33":197},"summary_large_image","twitter:card",{"_162":193,"_33":199},"twitter:title",{"_162":32,"_33":201},"twitter:description",{"_162":179,"_33":203},"twitter:image",{"_162":182,"_33":205},"twitter:image:height",{"_162":185,"_33":207},"twitter:image:width",{"_209":210},"script:ld+json",{"_211":212,"_213":214},"@context","http://schema.org","@graph",[215],{"_211":216,"_217":218,"_219":220},"https://schema.org","@type","BreadcrumbList","itemListElement",[221,227,231,235],{"_217":222,"_223":224,"_33":225,"_226":116},"ListItem","item","https://glama.ai/","Glama","position",{"_217":222,"_223":228,"_33":229,"_226":230},"https://glama.ai/mcp","MCP",2,{"_217":222,"_223":232,"_33":233,"_226":234},"https://glama.ai/mcp/servers","Servers",3,{"_217":222,"_223":165,"_33":34,"_226":236},4,"visitorIsMaintainer","routes/_public/mcp/servers/~namespace/~slug/_pages/_explorer/blob/~branch/~/_route",{"_240":241,"_245":98,"_29":246,"_156":260,"_284":285,"_286":287},"blob",{"_162":242,"_243":244},"# Build artifacts\n*.tgz\nbuild/\n\n# Editor temporary files\n.*.swp\n.*.swo\n*~\n\n# Runtime files\ncrash/\ntest-output.txt\n\n# Node.js\nnode_modules/\nnpm-debug.log\n","fileName",".gitignore","branch",{"_71":72,"_73":247,"_13":250,"_89":32,"_90":32,"_91":251,"_95":252,"_117":-5,"_16":118,"_119":120,"_121":254,"_33":34,"_133":109,"_134":257,"_139":-5,"_140":141,"_142":-5,"_143":258,"_148":-5,"_129":105,"_149":259,"_152":-5,"_110":153,"_154":155},{"_75":248,"_77":249,"_79":80},{},[],[82,83,84,85,86,87,88],{"_35":36,"_93":94},{"_97":98,"_99":100,"_101":102,"_103":104,"_33":105,"_106":253,"_112":113,"_114":-5,"_115":116},{"_108":109,"_110":111},[255],{"_124":256,"_31":131,"_110":132},{"_126":127,"_33":128,"_129":130},{"_33":136,"_137":138},{"_145":113,"_146":-5,"_147":-5},[151],[261,263,265,267,269,270,271,273,274,275,276,277,278,279,280,281,282,283],{"_159":262},"MCP Server | Glama",{"_162":264,"_33":31},"Enterprise-grade security, privacy, and features like agents, MCP, prompt templates, and more.",{"_164":266,"_166":167,"_168":169},"https://glama.ai/mcp/servers/@signal-slot/mcp-systemd-coredump/blob/main/",{"_162":268,"_171":172},"MCP Server",{"_162":264,"_171":174},{"_162":176,"_171":177},{"_162":272,"_171":180},"https://glama.ai/generated-images/og?title=MCP+Server",{"_162":182,"_171":183},{"_162":185,"_171":186},{"_162":188,"_171":189},{"_162":266,"_171":191},{"_162":193,"_171":194},{"_162":196,"_33":197},{"_162":193,"_33":199},{"_162":264,"_33":201},{"_162":272,"_33":203},{"_162":182,"_33":205},{"_162":185,"_33":207},"path","","treeMembers",[288,291,293,295,297,299,300,302,304,306,308,310,312,314,316,318,320,322,324,326,328,330,332,334,336],{"_284":289,"_79":290},"src","tree",{"_284":292,"_79":240},".clinerules",{"_284":294,"_79":240},"direct-test.js",{"_284":296,"_79":240},"example-usage.sh",{"_284":298,"_79":240},"generate-test-coredump.c",{"_284":244,"_79":240},{"_284":301,"_79":240},"JOIN_ORGANIZATION.md",{"_284":303,"_79":240},"mcp-settings.json",{"_284":305,"_79":240},".npmignore",{"_284":307,"_79":240},"package.json",{"_284":309,"_79":240},"package-lock.json",{"_284":311,"_79":240},"PUBLISHING.md",{"_284":313,"_79":240},"README.md",{"_284":315,"_79":240},"README.npm.md",{"_284":317,"_79":240},"stacktrace-direct-test.js",{"_284":319,"_79":240},"test-decode-fix.js",{"_284":321,"_79":240},"test-filter.js",{"_284":323,"_79":240},"test-simple.js",{"_284":325,"_79":240},"test-stacktrace.js",{"_284":327,"_79":240},"test-stacktrace-resource.js",{"_284":329,"_79":240},"test-stacktrace-simple.js",{"_284":331,"_79":240},"test-tools.js",{"_284":333,"_79":240},"tsconfig.json",{"_284":335,"_79":240},"verify-npm-package.js",{"_284":337,"_79":240},"verify-stacktrace-resource.sh","actionData","errors"]

MCP directory API