Use case
Answer questions about a codebase with an MCP server
Updated September 21, 2026
"How does auth work in this repo?" is a question someone asks every week. An MCP server that already knows how to read a repository's documentation answers it, and the agent decides which of its tools to use.
Connect the server
On the MCP page, search the marketplace for a documentation server and add it. Novalink lists its tools, here one that lists a repository's pages and one that answers questions about it.
Nothing else is needed: the server publishes what each tool takes, so its inputs appear on the node. See MCP servers.
How the workflow runs
- The trigger carries the question and the repository, for example
{ question, repo }. - The MCP node is attached to the agent as a tool, with Offer every tool on this server switched on, so the agent can list the pages first and then ask its question.
- The agent answers in a few sentences, citing the pages it read.
- Slack · Post message sends the answer to the channel that asked, and the Output node records it.
Fill the nodes with templates
Answer this question about {{ trigger.repo }} using the documentation tools:
{{ trigger.question }}Channel: #engineering
Text: {{ nodes.answer.output.text }}What to keep in mind
Keep reading
- MCP servers: a marketplace of tools for your workflowsConnect a Model Context Protocol server from the marketplace or by URL, and call its tools from a workflow node or hand them to an agent.
- MCP node: call a tool on an MCP serverThe MCP node calls a tool on a Model Context Protocol server you connected, with its saved auth. It also works as an agent tool, one tool or the whole server.
- Agent node: Claude with tools and structured outputThe Agent node calls Claude with your prompt, can call attached HTTP tools in a loop, and returns text plus schema-validated structured output for branching.
Build it on the canvas
Create a free account, describe the workflow or wire it yourself, and run it in the browser.