Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Convert files between 44 formats: documents, spreadsheets, images, ebooks, subtitles.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"filemorph": {
"command": "npx",
"args": [
"-y",
"@reneturcios/filemorph",
"mcp"
]
}
}
}Run this in your terminal
claude mcp add filemorph -- npx -y @reneturcios/filemorph mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"filemorph": {
"command": "npx",
"args": [
"-y",
"@reneturcios/filemorph",
"mcp"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"filemorph": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@reneturcios/filemorph",
"mcp"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026
The registry name was verified with the GitHub account CloudCorpRecords, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (0.1.0) reached the registry yesterday.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js, Docker on your computer.
In the same category: Spec Driven Development, Remote Desktop Commander, DepTime
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
What changed in a Python library, in which release, and what replaces it. Answered locally.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
filemorph is a small local bridge to the hosted FileTypeConverters MCP server, which converts files between 44 formats spanning documents, spreadsheets, images, ebooks and subtitles. You hand it a file either as base64 content or as a public https URL, pick a target format, and get the converted output back — small text outputs inline, larger or binary outputs as base64 plus a download URL.
The bridge converts nothing itself and keeps no files. It serves the upstream server's tool list locally, exactly as captured from the live endpoint, and forwards each tool call upstream, returning the result untouched. Two tools read reference data, one checks whether a conversion pair is supported, one submits a conversion, and one fetches a conversion submitted earlier.
list_formats — every format the converter can read or write, with its id, name, extensions and family. The ids are what the other tools take as from and to. No arguments.check_conversion — whether one format can be converted to another, checked before any file is sent. Reports the engine, whether AI Deep Read is needed, the options the pair accepts, and alternatives when the pair is not supported. Formats may be given as ids (docx), extensions (jpeg) or common names (word, excel). Required: from, to.list_conversions — the supported target formats for a source format, or every source that can produce a given target, as compact {from,to,slug,engine,mode} rows. Optional: from, to.convert_file — submit a file for conversion. The content goes in as base64 or as a public https url; from is optional when the filename or URL carries an extension. Text outputs (Markdown, CSV, JSON, HTML…) up to 200 KB come back inline as text; other outputs come back as base64 plus a downloadUrl that accepts the same bearer token. Files are capped at 10 MB. Setting deepRead: true reads scans, photos and handwriting with AI Deep Read (1 credit per page). Required: to. Optional: filename, base64, url, from, options, deepRead.get_conversion — a conversion submitted earlier, fetched by id: its status, any warnings, and the output (inline text or base64) while it is still retained. Required: id.FILETYPECONVERTERS_MCP_URL (optional) — override the upstream endpoint. Defaults to https://filetypeconverters.com/api/mcp. (The override hook is this rebuild's own labelled reconstruction.)FILETYPECONVERTERS_API_KEY (optional) — when set, every upstream request carries an Authorization: Bearer header. When it is not set, no auth header is sent. (This forwarding is also a labelled reconstruction; the original surface was captured keyless, though the registry record declares an Authorization header required.)On the first tool call the client opens a streamable HTTP session with the upstream: a JSON-RPC initialize request (protocolVersion 2025-03-26, clientInfo name filemorph), then a notifications/initialized notification, then the tools/call request carrying the caller's arguments unchanged. When the upstream answers initialize with an Mcp-Session-Id header, that value rides on every later request of the session, which is reused for the life of the process. Replies may arrive as plain JSON or as server-sent events; both are read.
Successful upstream results pass through verbatim, including any isError flag the upstream sets. Failures — a JSON-RPC error, a non-2xx status, an unreadable response, or a request that cannot be completed — come back as an isError result whose text starts with filemorph error: (this rendering is this rebuild's own labelled reconstruction).
Each tool is also a subcommand taking one JSON argument string (omit it for tools that take none):
npx @reneturcios/filemorph list_formats
npx @reneturcios/filemorph check_conversion '{"from":"pdf","to":"docx"}' npx @reneturcios/filemorph convert_file '{"to":"md","filename":"report.pdf","base64":"..."}' npx @reneturcios/filemorph get_conversion '{"id":"conv-42"}' npx @reneturcios/filemorph --version
Exit codes: 0 on success, 1 on an isError result, 2 on a usage error.
npx -y @reneturcios/filemorph mcp
MCP client config:
{
"mcpServers": { "filemorph": { "command": "npx", "args": ["-y", "@reneturcios/filemorph", "mcp"] } } }
docker run -i ghcr.io/cloudcorprecords/filemorph
docker run --rm ghcr.io/cloudcorprecords/filemorph --version
The container's default command is mcp, so the first form is a stdio MCP server; any other arguments reach the CLI normally.
npm install
npm run build npm test npm run dev
The test suite runs entirely against a stubbed JSON-RPC upstream — no live network calls.
MIT — see LICENSE.