MCP servers in Novalink, with a marketplace to find them

Adding a server used to mean finding its URL first. The MCP page now opens on a marketplace: search a public registry, read what a server does, and add it in one step. Novalink fills in its endpoint and asks for whatever it needs, such as the account key it should use.

Servers outside the registry are still welcome. The By URL tab takes any server that speaks MCP over HTTP, with no auth, a bearer token, custom headers or an OAuth sign-in.

After connecting, Novalink asks the server what it can do and remembers the answer, so a tool's inputs appear on the node without you describing them. One tool is one node, wired like any other step.

Server: DeepWiki
Tool: read_wiki_structure
repoName: {{ trigger.repo }}

Attach that node to an agent and it becomes a tool the agent can call. Switch on Offer every tool on this server and the agent gets the whole server to choose from, which is what MCP is really for.

We could have handed the server to the model provider and let it make the calls. We did not, because a call we make is a call we can guard and record: private addresses are refused, secrets are scrubbed, and every tool call lands in the run so you can replay what was asked and what came back. It also means a tool works as a plain step, with no agent involved.

A server you connect sees the arguments you send it, and what it returns reaches your agent's context. Connect servers you trust, the same as any integration. Tools can change under you, so Novalink warns when a workflow names one the server no longer lists, and Refresh asks again. See MCP servers to get started.