Prompt
Describe the outcome and point the coding agent to the Tarvos registry.
From intent to infrastructure.
How does Tarvos work?
A builder describes a workflow, a coding agent reads the Tarvos registry, installs the required open-source nodes, and builds through the builder's own n8n MCP connection. The resulting workflow runs in the builder's self-hosted n8n environment.
One request. Four clear movements.
Discover
The registry identifies the correct node, provider, capabilities, credentials, and installation source.
Install
Only the required community-node packages enter the self-hosted n8n environment.
Build
The user's own n8n MCP connection creates the workflow directly in their instance.
A registry built for two readers.
The same public source explains every documented integration to builders and exposes predictable data for coding agents.
For humans
Installation guidance, provider choices, credential definitions, capabilities, examples, and compatibility notes.
For agents
Stable URLs, JSON and Markdown records, package sources, exact installation commands, schemas, and workflow examples.
Agent contract
Browse first. Build inside the user's instance.
Tarvos keeps installation constrained to explicitly installable, inspectable sources.
- 01Read the registry
Start with the canonical /registry.json source.
- 02Match the capability
Select a node marked installable that fits the requested outcome.
- 03Verify the source
Confirm its status, provider, credentials, and repository.
- 04Install the package
Run the exact installation command from the node record.
- 05Build and validate
Create the workflow through the user's own n8n MCP.
Your coding agent. Your n8n MCP. Your infrastructure.
Tarvos generates the connection, not the execution.
Workflows run inside the self-hosted n8n environment the builder controls. Tarvos never becomes a required runtime.