MCP server

The endpoint

https://novusstreamsolutions.com/mcp

One stateless POST, JSON-RPC over HTTP, protocol revision 2026-07-28. No account, no key, no sign-up: every tool reads content this site already publishes, so an authentication step would be theatre. A GET answers 405 on purpose, because that revision removed the server-sent stream and a client opening one needs a definitive answer rather than a request that hangs.

Adding it to a client

Most clients take a block like this. The server name is yours to choose; the URL is the part that matters.

{
  "mcpServers": {
    "novus": {
      "type": "http",
      "url": "https://novusstreamsolutions.com/mcp"
    }
  }
}

What it exposes

List every app in the Novus networklist_novus_apps

The whole Novus Stream Solutions network: every app, what it is for, its URL, and whether it runs its own MCP server. Start here when you do not yet know which app a request belongs to. Every app is free to use and needs no account unless stated.

Find the right Novus tool for a task, across every appfind_tool

Describe a task in plain language and get the Novus tools that do it, ranked, from anywhere in the network. This searches all nine apps at once, so use it before guessing which subdomain a capability lives on. Returns the app, the tool and the URL that opens it. These tools run in the visitor's browser, so this server can locate them but cannot run them.

Everything one Novus app doesget_app

The full tool map for one app: every tool and editor it ships, grouped by section, with a description and URL for each, plus its docs, tutorials and MCP endpoint. Use it to answer "what can this app do?" without opening the site. Call list_novus_apps for the slugs.

List the cross-app recipeslist_workflows

Recipes that span more than one Novus app: the sequences where the output of one app is the input to the next. Use this when a request needs several steps ("product photo ready for three storefronts") rather than one tool. Call get_workflow for the steps.

The steps in one cross-app recipeget_workflow

One recipe in full: each step, which app performs it, why that step matters, and the URL that answers how. Call list_workflows for the ids.

Search the tutorials, documentation and product blogsearch_docs

Search the hub's written material: tutorials, per-app documentation, the product blog and the site's own pages. Use this for a how-to or a why question, or to cite a page. Use find_tool instead when the question is which tool does a job.

Resources and prompts

Alongside the tools the server publishes 2 readable resources and 1 prompt:

Novus Stream Solutions site index for language modelshttps://novusstreamsolutions.com/llms.txt

The site index written for language models: what the network is and its key pages.

Machine-readable directory of the Novus networkhttps://novusstreamsolutions.com/apps.json

Every app with its URL, category, capabilities, documentation and MCP endpoint.

Find the Novus app and tool for a taskroute_a_task

Work out which Novus app handles a described task, and how to run it.

What it will not do

It cannot run a Novus tool for you. The tools it describes execute inside a browser tab (the models, the WebAssembly cores, the canvas) on a file the visitor chose, and nothing is uploaded, so this server holds nothing to work on. A tool here that offered to remove a background or sign a PDF would either have to ask for that upload or lie about the result.

What it returns instead is a route: which app, which tool, and the URL that opens it, so the browser doing the work can be an AI browser or the person’s own. Everything it reads is already published on this site (the app catalogue, the tool maps, the documentation, the tutorials and the product blog), so a caller reaches exactly what an anonymous visitor reaches and nothing else. Nothing here writes, bills, or touches anyone’s account, which is why there is nothing to authenticate.

Novus Restaurant is the one data-backed exception in the network, and its own MCP server requires a token for that reason. The same routing the tools do by hand is written up for people on the tool maps and cross-product workflows.