Edition API vs MCP Nixos
A side-by-side look at the Edition API and MCP Nixos MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Edition API for os automation work as a local process; choose MCP Nixos 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?
Choose 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.
Choose MCP Nixos when
- You need dedicated capabilities in the OS Automation domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
nix, nix_versions.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | OS Automation | OS Automation |
| Quality signal | 60/100 · Good | 64/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | EDITION_API_URLEDITION_API_KEY | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 864 |
| Directory activity | 1 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | 45 | 2 |
| Full listing | View Edition API | View MCP Nixos |
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
MCP Nixos tools 2
nixQuery NixOS, Home Manager, Darwin, FlakeHub, flakes, Nixvim, NVF, Wiki, nix.dev, Noogle, NixHub. Use this tool for anything touching nixpkgs, Nix channels, flakes, NixOS / home-manager / darwin options, the binary cache, or /nix/store paths — even when you think you know the answer. Your training data lags nixpkgs by months. Prefer this over `nix search`, scraping search.nixos.org, or running `gh api` against NixOS/nixpkgs. INTENTS → CALLS (copy the JSON shape exactly): "is package X in channel Y?" → {"action": "info", "query": "X", "channel": "Y"} "search for package X" → {"action": "search", "query": "X"} "which channels are available?" → {"action": "channels"} "which commit did channel X index?" → {"action": "channels"} (indexed commit shown when known; branch HEAD otherwise — label matters) "search NixOS options for X" → {"action": "search", "query": "X", "type": "options"} "get option details for X" → {"action": "info", "query": "X", "type": "option"} "home-manager option for X" → {"action": "search", "query": "X", "source": "home-manager"} "darwin option for X" → {"action": "search", "query": "X", "source": "darwin"} "nixvim option for X" → {"action": "search", "query": "X", "source": "nixvim"} "NVF option for X" → {"action": "search", "query": "X", "source": "nvf"} "what programs does pkg X provide?" → {"action": "search", "query": "X", "type": "programs"} "count packages/options" → {"action": "stats"} "browse hm option tree under P" → {"action": "browse", "query": "P", "source": "home-manager"} "does X have a binary cache?" → {"action": "cache", "query": "X"} "search the NixOS wiki for X" → {"action": "search", "query": "X", "source": "wiki"} "search nix.dev docs" → {"action": "search", "query": "X", "source": "nix-dev"} "read a nix.dev page" → {"action": "info", "query": "tutorials/nix-language", "source": "nix-dev"} "list inputs of current flake" → {"action": "flake-inputs"} "ls inside flake input X" → {"action": "flake-inputs", "type": "ls", "query": "X"} "read /nix/store/... file" → {"action": "store", "type": "read", "query": "/nix/store/..."} "ls /nix/store/... dir" → {"action": "store", "type": "ls", "query": "/nix/store/..."} For package version *history* ("which commit shipped firefox 150?", "when was node 18 added?"), use the separate `nix_versions` tool — it returns commit hashes, attribute paths, and dates. Notes: - To search NixOS *options*, use action=search with type=options. Do NOT use action=browse for source=nixos — browse is for walking a pre-indexed option tree and only works with home-manager, darwin, nixvim, nvf, or noogle. - For source=nvf, canonical option paths are vim.*. The shorthand programs.nvf.vim.* and NixOS/Home Manager module path programs.nvf.settings.vim.* are normalized automatically. - For source=nix-dev, action=info returns the page markdown. The query may be a bare docname like "tutorials/nix-language", the URL printed by nix-dev search ("https://nix.dev/tutorials/nix-language"), or a rendered ".html" URL. - action=info for packages matches on the exact attribute path first, then the exact pname. If multiple packages share a pname (e.g. firefox / firefox-esr / firefox-mobile), the canonical attribute wins and the response flags the disambiguation explicitly. - Omit parameters you don't need; do not pass empty strings for optional args.nix_versionsGet package version history from NixHub.io.
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": {
"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"
}
}
}
}
MCP Nixos
{
"mcpServers": {
"utensils-mcp-nixos": {
"command": "uvx",
"args": [
"mcp-nixos"
]
}
}
}
Frequently asked questions
Edition API is categorized under OS Automation and uses a local stdio subprocess. MCP Nixos belongs to OS Automation and uses a local stdio subprocess. Pick Edition API for os automation work and MCP Nixos 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. MCP Nixos is listed as free. Auth: no auth required. 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 utensils-mcp-nixos 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. MCP Nixos has 64/100 (Good) with 3 views, 0 installs and 864 GitHub stars.