Edition API vs Linux MCP Server

A side-by-side look at the Edition API and Linux MCP Server MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Edition API logoEdition APIOS Automation · Local subprocess (stdio)Japan Operations OS for AI agents. 10 knowledge domains, 23 MCP tools for the Japanese market.60GoodAuth: not declaredLinux MCP Server logoLinux MCP ServerOS Automation · Local subprocess (stdio)MCP server for read-only Linux system administration, diagnostics, and troubleshooting64GoodAuth: not declared

Verdict: choose Edition API for os automation work as a local process; choose Linux MCP Server for os automation as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Edition API logoChoose Edition API when

  • You need dedicated capabilities in the OS Automation domain.
  • You prefer a local stdio subprocess transport.
  • You have the keys it needs: EDITION_API_URL, EDITION_API_KEY.
  • You want tools like memory_store, memory_recall, memory_facts.
Explore Edition API

Linux MCP Server logoChoose Linux MCP Server when

  • You need dedicated capabilities in the OS Automation domain.
  • You prefer a local stdio subprocess transport.
  • You want tools like get_journal_logs, read_log_file, get_network_interfaces.
Explore Linux MCP Server

Feature & specification comparison

Rows where the two servers differ are marked.

SpecEdition API logoEdition APILinux MCP Server logoLinux MCP Server
CategoryOS AutomationOS Automation
Quality signal60/100 · Good64/100 · Good
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNot declaredNot declared
PricingNot declaredNot declared
Required env varsEDITION_API_URLEDITION_API_KEYNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars0314
Directory activity 1 views 0 installs 0 upvotes 3 views 0 installs 0 upvotes
Tools4523

Tools & capabilities

Edition API tools 45

  • memory_store会話やイベントのエピソードを永続記憶に保存します。日本語の文脈(敬語レベル、主語省略、暗黙の了解)も構造化して保持します。auto_extract=trueにすると、テキストからファクト(主語→述語→目的語の三つ組)を自動抽出します。
  • memory_recall過去の記憶をセマンティック検索で呼び出します。「前回の会議で○○部長が仰った件」のような曖昧な日本語クエリにも対応します。
  • memory_facts現在有効なファクト(構造化された事実)の一覧を取得します。ファクトは「主語→述語→目的語」の三つ組で、確度と有効期限を持ちます。
  • memory_context現在のセッション状態(有効な事実・合意事項のサマリー)を取得します。エージェントのプロンプトに注入して文脈を維持するために使います。新しい会話セッション開始時や、長い会話の途中で文脈を再確認したい場合に呼び出してください。個別のファクトを一覧で見たい場合はmemory_factsを使ってください。
  • memory_extractテキストからファクト(主語→述語→目的語の三つ組)を自動抽出します。日本語の敬語・主語省略・社会的階層を分析して構造化します。store=trueにすると抽出結果をメモリに永続保存します(書き込み発生)。store=false(デフォルト)なら読み取り専用で、保存せずに抽出結果のみ返します。memory_storeとの違い: memory_storeはエピソード全体を保存、memory_extractはテキストからファクトのみを抽出。
  • regulation_check特定のビジネスアクションに必要な日本の規制・許認可情報を回答します。10業種の詳細データベース + 訪日旅行者向け規制に対応。
  • regulation_industries日本の規制データベースに登録されている業種の一覧を取得します。対応業種を確認したい場合や、regulation_checkに渡すindustryパラメータの値を調べたい場合に使ってください。特定の規制内容を知りたい場合はregulation_checkを使ってください。
  • regulation_tourist訪日旅行者向けの規制・マナー情報のカテゴリ一覧を取得します。ビザ、免税、交通、宿泊、医療、マナーの6カテゴリ。どのカテゴリがあるか一覧で確認したい場合に使ってください。特定のカテゴリの詳細を知りたい場合はregulation_check(entity_type='tourist')を使ってください。
  • protocol_check日本のビジネスプロトコル(根回し、稟議、報連相、名刺交換、席順、贈答)を検索します。
  • protocol_list日本のビジネスプロトコルの一覧を取得します。カテゴリを一覧で確認したい場合はこのツールを使い、特定のプロトコル(例: 名刺交換)の詳細を知りたい場合はprotocol_checkを使ってください。
  • calendar_check日本のビジネスカレンダー情報を検索します。祝日、決算期、贈答シーズン、行政締切、季節性ビジネスの5カテゴリ。
  • calendar_list日本のビジネスカレンダーの全カテゴリ一覧を取得します。カテゴリを一覧で確認したい場合はこのツールを使い、特定の日付やイベント(例: GW、確定申告)を検索する場合はcalendar_checkを使ってください。
  • +33 more on the listing page

Linux MCP Server tools 23

  • get_journal_logsGet systemd journal logs.
  • read_log_fileRead a specific log file.
  • get_network_interfacesGet detailed information about network interfaces including address and traffic statistics.
  • get_network_connectionsGet detailed information about active network connections.
  • get_listening_portsGet details on listening port, protocols, and services.
  • pcp_guideReturns the PCP metrics guide: a catalog of the metric names recorded on a typical Linux system, and how to read the values the other PCP tools return. Read it before investigating performance with PCP, and take metric names from it rather than from memory.
  • pcp_list_metricsBrowses the PCP metric namespace. Lists the metrics under 'prefix' with their descriptions, collapsing any large sub-namespace to one line giving its name and how many metrics it holds; call again with that name as the prefix to see inside it. Only metrics this system's pmlogger records are listed, so everything listed can be passed to pcp_query_metrics. The pcp_guide tool already names the commonly needed metrics, so reach for this when you need a subsystem the guide does not cover. Use only if get_system_information() indicates PCP is available.
  • pcp_query_metricsRetrieves historical metric data from PCP archives as JSON samples. When start_time, end_time, or interval is omitted, reasonable defaults are chosen, targeting one hour or about 20 samples. Call pcp_guide first for the metric catalog and how to read the values; do not guess metric names. Use only if get_system_information() indicates PCP is available.
  • pcp_performance_summaryProduces a condensed snapshot of CPU, memory, disk, network, and process information using pcp xsos. Can summarize the live system or a particular time in the past. Use only if get_system_information() indicates PCP is available.
  • list_processesList running processes
  • get_process_infoGet information about a specific process.
  • list_servicesList all systemd services.
  • +11 more on the listing page

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

Edition API

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "edition-api": {
      "command": "npx",
      "args": [
        "-y",
        "edition-mcp-server"
      ],
      "env": {
        "EDITION_API_URL": "YOUR_EDITION_API_URL_HERE",
        "EDITION_API_KEY": "YOUR_EDITION_API_KEY_HERE"
      }
    }
  }
}

Linux MCP Server

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "linux-mcp-server-2": {
      "command": "uvx",
      "args": [
        "linux-mcp-server"
      ]
    }
  }
}

Frequently asked questions

Edition API is categorized under OS Automation and uses a local stdio subprocess. Linux MCP Server belongs to OS Automation and uses a local stdio subprocess. Pick Edition API for os automation work and Linux MCP Server for os automation.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.

Edition API has no declared pricing — check the project's own site. Linux MCP Server has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add edition-api and linux-mcp-server-2 as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Edition API has a quality signal of 60/100 (Good) with 1 views, 0 installs and 0 GitHub stars. Linux MCP Server has 64/100 (Good) with 3 views, 0 installs and 314 GitHub stars.