MCP server for terminal commands, file operations, and process management
Filemorph 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
Convert files between 44 formats: documents, spreadsheets, images, ebooks, subtitles.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user filemorph-mcp '--' npx -y @reneturcios/filemorph mcp
# 2 — ask your agent for something these tools do
# list_formats, check_conversion, list_conversions and 2 more
Filemorph costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
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 Filemorph 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.
This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user filemorph-mcp '--' npx -y @reneturcios/filemorph mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
5 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
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.
List every file format this converter reads or writes (id, name, extensions, family). Use the id values as from/to in other tools.
No parameter schema on file.
Check whether one format can be converted to another before sending a file. Returns the engine, whether AI Deep Read is needed, the options it accepts, and alternatives when the pair is not supported. Formats accept ids (docx), extensions (jpeg) or common names (word, excel).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| from | string | yes | Source format, e.g. pdf |
| to | string | yes | Target format, e.g. docx |
List supported target formats for a source format (or every source that can produce a target). Returns compact {from,to,slug,engine,mode} rows.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| from | string | no | A source format (e.g. "pdf"), to list the target formats it can be converted to. |
| to | string | no | A target format, to list every source format that can be converted into it. |
Convert a file. Provide the content as base64 OR a public https URL. from is optional when the filename/URL has an extension. Text outputs (Markdown, CSV, JSON, HTML…) up to 200 KB are returned inline as text; other outputs are returned as base64 plus a downloadUrl that accepts the same…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| filename | string | no | Original filename with extension, e.g. report.pdf |
| base64 | string | no | File bytes, base64-encoded |
| url | string | no | Public https URL of the file (alternative to base64) |
| from | string | no | Source format id; detected from the filename when omitted |
| to | string | yes | Target format id, e.g. md, docx, xlsx, png |
| options | object | no | Engine options from check_conversion (delimiter, sheet, quality, …) |
| deepRead | boolean | no | Use AI Deep Read (OCR + layout understanding) for PDFs and images |
Fetch a previous conversion by id: status, warnings, and the output (inline text or base64) if it is still retained.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | The id of the conversion to fetch, as returned when the conversion was created. |
- 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 Filemorph 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 | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| 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.
No tools were enumerated, so prompt-injection, capability and toxic-flow analysis had no tool surface to inspect. To grade a package’s real runtime tools, scan the running server: --command "npx -y <package>".
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. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| No per-tool rows for this release — see the note below. | ||
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.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
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
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 0.1.0. Pin a release below and the command asks for exactly that one.
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 Filemorph 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.