MCP servers: a marketplace of tools for your workflows

Marketplace searches a public registry of MCP servers. Pick one and it is added straight away. If the server needs something from you, such as signing in to Gmail or a Brave API key, its page shows what is missing and a Finish setup button that opens the marketplace's own page for it. Come back and choose check again, and its tools appear.

Now and then a marketplace listing is broken for everyone, and the page says so. Most of those servers also have their own URL you can add directly instead.

By URL connects any server that speaks MCP over HTTP. Give it the URL and how it authenticates: nothing, a bearer token, custom headers, or an OAuth sign-in. Servers that run as a local command are not supported, because Novalink runs on our servers, not on your machine.

After connecting, Novalink asks the server what tools it has and remembers the answer. A server can change its tools at any time, so press Refresh on its page to ask again. If a workflow names a tool the server no longer lists, validation warns you, and the run reports whatever the server says.

In the editor palette, MCP tools lists your servers. Adding one creates an MCP node: pick a tool and fill its inputs with values or templates. The node outputs what the tool returned, so later nodes can read it.

Connect the node to an Agent's tools port and the agent calls it, filling whatever you left empty. Switch on Offer every tool on this server and the agent can choose any of the server's tools rather than the one you picked.

• Tokens are encrypted at rest, never returned to the browser, and scrubbed from run records.
• Private and loopback addresses are refused, the same as the HTTP Request node.
• A server you connect sees the arguments you send it, and what it returns reaches your agent. Connect servers you trust, the same as any other integration.
• Every call is recorded on the run, so you can replay what a tool was asked and what it answered.