For AI clientsMCP server
Novus Convert publishes a Model Context Protocol endpoint, so an assistant can ask this site directly which conversions exist and how to run them, instead of guessing from a search result.
01The endpoint
https://convert.novusstreamsolutions.com/mcp
One stateless POST, JSON-RPC over HTTP, protocol revision 2026-07-28. There is no account, no key and no sign-up: every tool reads content that is already public on this site, so an authentication step would be theatre. A GET answers 405 on purpose. That revision removed the server-sent stream, and a client that opens one needs to be told definitively so it stops waiting.
02Adding it to a client
Most clients take a JSON block like this one. The server name is yours to choose; the URL is the part that matters.
{
"mcpServers": {
"novus-convert": {
"type": "http",
"url": "https://convert.novusstreamsolutions.com/mcp"
}
}
}
01What this site can do, with live counts
list_capabilities
The workspaces on Novus Convert and the size of the catalogue behind each one: how many formats are documented, how many are accepted as browser inputs, how many conversion routes exist, and how many formats can be compressed without changing format. Every count is read from the shipping registry. Use this to answer "can this site do X?" before picking a route. These conversions run in the visitor's browser, so this server can describe and locate them but cannot execute them.
02Find the route for a described job
find_conversion
Search every conversion route and same-format compressor by what someone is trying to do, in their own words: "heic to jpg", "get the audio out of an mp4", "make this photo smaller for email". Returns the best matches with the URL that opens each one. Naming both extensions ("png to webp") resolves that exact route first. This server cannot run the conversion; the URL is the handoff.
03Read one format's profile and its routes
get_format
The authored profile for one file format (what it is, where it came from, what it is good and bad at, and how well supported it is), plus every conversion this site publishes from it and whether it can be compressed in place. Pass an extension such as "heic", "stl" or "tar.gz".
04Get one route's URL, limits and operating steps
get_conversion_route
Everything the registry knows about converting one format into another: whether the route exists, which engine runs it, what survives the conversion, roughly what happens to file size, the URL that opens it, and the steps to drive that page. This is the handoff point. The conversion happens in the browser at that URL, never on this server. Call find_conversion first if you do not know both extensions.
05Search the site's written pages and articles
search_docs
Search the explanatory pages (about, docs, help, privacy, security, status, press kit, tool map) and the blog's format guides and comparisons. Use it for a how-to or a policy question rather than a which-route question, and to cite a page. Returns titles, summaries and URLs.
06List every site in the Novus network
list_novus_sites
The other Novus Stream Solutions sites and what each one is for. Use this when a request is outside what this site does: editing an image, working on a PDF, study material, a music video, AI usage stats, food-market data, or a game. Each site runs its own MCP server at /mcp.
01Pick the right conversion for a task
pick_a_conversion
Walk through choosing a route on this site for a described task, and how to run it.
01What it will not do
It cannot convert a file. Every engine on this site runs inside your own browser tab on a file you chose, and nothing is uploaded, so there is no server-side conversion for a tool to call. A tool that claimed to convert would either have to ask for that upload or lie about the result. What it returns instead is the route, its limits, the steps to operate it, and the URL that opens it, so the browser doing the work can be an AI browser or your own.
02What it reads
The same registry the pages render, so it cannot describe a format or a route that does not exist here. A route it reports as a guide is implemented but has no independently verified browser fixture yet, and it says so rather than presenting it as proven.