Server providing Argo CD integration for MCP clients.
Kilnshell is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Fast, telemetry-free local MCP: shell, files, search, processes, PDF, Excel and Word for agents.
Quickstart
Install it the way its author documents:
The full guide: https://github.com/Soflutionltd/kilnshell/releases/download/v1.0.5/kilnshell.mcpb
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts Kilnshell as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
Install it the way its author documents:
The full guide: https://github.com/Soflutionltd/kilnshell/releases/download/v1.0.5/kilnshell.mcpb
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Read from its source code. A server that builds its tool list when it starts can list more tools than this.
Get the complete server configuration as JSON. Config includes fields for: - blockedCommands (array of blocked shell commands) - defaultShell (shell to use for commands) - allowedDirectories (paths the server can access)…
No parameter schema on file.
Set a specific configuration value by key. Security note: configuration changes affect later file and command behavior. Isolating them from untrusted file or command content reduces the chance that external content influences…
No parameter schema on file.
Read contents from files and URLs. Read PDF files and extract content as markdown and images. Suitable for reading authorized local files directly without starting a shell command.…
No parameter schema on file.
Read the contents of multiple files simultaneously. Each file's content is returned with its path as a reference. Handles text files normally and renders images as viewable content. Recognized image…
No parameter schema on file.
Write or append to file contents. PDF creation is handled by the dedicated write_pdf tool. Existing DOCX content can be edited with edit_block. New DOCX files can be created here; markdown headings (#, ##, ###) are converted to styled DOCX…
No parameter schema on file.
Create a new PDF file or modify an existing one. Dedicated PDF creation and modification tool. OUTPUT FILES: - Creating a PDF requires 'outputPath' with a new filename (e.g., "result_01.pdf", "analysis_2025_01.pdf", etc.).…
No parameter schema on file.
Create a new directory or ensure a directory exists. Can create multiple nested directories in one operation. Only works within allowed directories. … Relative paths depend on…
No parameter schema on file.
Get a detailed listing of all files and directories in a specified path. Returns a structured directory listing without starting a shell command. Results distinguish between files and directories with [FILE] and [DIR]…
No parameter schema on file.
Move or rename files and directories. Can move files between directories and rename them in a single operation. Both source and destination must be within allowed directories.…
No parameter schema on file.
Start a streaming search that can return results progressively. SEARCH STRATEGY GUIDE: Choose the right search type based on what the user is looking for: USE…
No parameter schema on file.
Get more results from an active search with offset-based pagination. Supports partial result reading with: - 'offset' (start result index, default: 0) * Positive: Start from result N (0-based…
No parameter schema on file.
Stop an active search. Stops the background search process gracefully. Use this when you've found what you need or if a search is taking too long. Similar to force_terminate for terminal processes.…
No parameter schema on file.
List all active searches. Shows search IDs, search types, patterns, status, and runtime. Similar to list_sessions for terminal processes. Useful for managing multiple concurrent searches.…
No parameter schema on file.
Retrieve detailed metadata about a file or directory including: - size - creation time - last modified time - permissions - type - lineCount (for text…
No parameter schema on file.
Apply surgical edits to files. Small, focused edits are easier to verify than large multi-purpose replacements. old_string can include enough surrounding context to uniquely identify the intended text. FORMAT HANDLING (by…
No parameter schema on file.
Start a terminal process on the authorized device with intelligent state detection. Suitable for shell commands, interactive REPL sessions, data-processing scripts, programmatic file analysis, and other long-running terminal…
No parameter schema on file.
Read output from a running process with file-like pagination support. Supports partial output reading with offset and length parameters (like read_file): - 'offset' (start line, default: 0) *…
No parameter schema on file.
Send input to an existing terminal or REPL process and return newly available output. Useful for interactive shells, Python/Node/R/Julia REPLs, database consoles, and long-running commands started with start_process().…
No parameter schema on file.
Force terminate a running terminal session. This command can be referenced as "KS: ..." or "use Kilnshell to ..." in your instructions.
No parameter schema on file.
List all active terminal sessions. Shows session status including: - PID: Process identifier - Blocked: Whether session is waiting for input - Runtime: How long the session…
No parameter schema on file.
List all running processes. Returns process information including PID, command name, CPU usage, and memory usage. This command can be referenced as "KS: ..." or "use Kilnshell to ..." in your…
No parameter schema on file.
Run several Kilnshell tools in ONE call, in order, and get every result back together. Each call is {tool, arguments}, exactly as if it were called on its own. Use it to chain reads, edits, commands and searches: one round trip instead of one per…
No parameter schema on file.
Wait until a condition holds instead of polling: a TCP port accepts connections (port, host), a file exists (path), a URL answers (url), or a process started with start_process exits (pid). gone=true waits for the port or file to disappear.…
No parameter schema on file.
Terminate a running process by PID. Use with caution as this will forcefully terminate the specified process. This command can be referenced as "KS: ..." or "use Kilnshell to ..." in your instructions.
No parameter schema on file.
Get usage statistics for debugging and analysis. Returns summary of tool usage, success/failure rates, and performance metrics. This command can be referenced as "KS: ..." or "use Kilnshell to ..." in…
No parameter schema on file.
Get recent local tool call history with arguments and outputs. Returns a chronological list of recent calls loaded from the local history file. Useful for: - Onboarding new chats about work already…
No parameter schema on file.
Open feedback form in browser to provide feedback about Desktop Commander. The form itself collects survey answers; this tool does not accept survey responses or pre-fill them. It automatically includes basic usage metadata:…
No parameter schema on file.
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Kilnshell or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | critical | capability blast radius (critical) — client exposure if the model is manipulated | −10 |
| verification-discount | repo | publisher verification (public source) — no provenance, but the source is public and inspectable | −1 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tools were statically extracted from the published source (27 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
uninstall-claude-server.js (27 KB) was not read: over the file-count budget.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. critical is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| get_config | no tags | |
| set_config_value | state-write | state-write: declares readOnlyHint: false, destructiveHint: true |
| read_multiple_files | no tags | |
| write_file | file-writestate-write | file-write: keyword "write_file" in tool name; state-write: declares readOnlyHint: false, destructiveHint: true |
| write_pdf | state-write | state-write: declares readOnlyHint: false, destructiveHint: true |
| create_directory | state-write | state-write: declares readOnlyHint: false |
| list_directory | no tags | |
| move_file | file-writestate-write | file-write: keyword "move_file" in tool name; state-write: declares readOnlyHint: false, destructiveHint: true |
| get_more_search_results | no tags | |
| stop_search | state-write | state-write: declares readOnlyHint: false |
| list_searches | no tags | |
| get_file_info | no tags | |
| start_process | external-sink | external-sink: declares readOnlyHint: false, destructiveHint: true, openWorldHint: true |
| read_process_output | no tags | |
| interact_with_process | external-sink | external-sink: declares readOnlyHint: false, destructiveHint: true, openWorldHint: true |
| force_terminate | state-write | state-write: declares readOnlyHint: false, destructiveHint: true |
| list_sessions | no tags | |
| list_processes | no tags | |
| batch | external-sink | external-sink: declares readOnlyHint: false, destructiveHint: true, openWorldHint: true |
| wait_for | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| kill_process | state-write | state-write: declares readOnlyHint: false, destructiveHint: true |
| get_usage_stats | no tags | |
| get_recent_tool_calls | no tags | |
| give_feedback_to_desktop_commander | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
| read_file | untrusted-inputsensitive-source | untrusted-input: keyword "fetch", declares openWorldHint: true (interacts with entities outside the server); sensitive-source: keyword "read_file" |
| start_search | no tags | |
| edit_block | state-write | state-write: declares readOnlyHint: false, destructiveHint: true |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
Supply chain and provenance
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
It installs from its repository rather than from a versioned package, so the command cannot be pinned to a release. The history below is for reading; the current release on file is 1.0.5.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish Kilnshell can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.