Before you begin
Tarvos initially supports self-hosted n8n. You need an environment where community nodes can be installed and, for agent-assisted building, an n8n MCP connection available to your coding agent.
Builder journey
- Describe the workflow.State the trigger, desired action, Solana service, and expected result.
- Read the registry.Find an installable node matching the required capability.
- Verify the record.Check readiness, lifecycle, provider, credentials, capabilities, and installation source.
- Install the node.Use only the exact command provided by an installable registry record.
- Configure credentials in n8n.Tarvos never receives or stores credential values.
- Build and test.Assemble manually or through n8n MCP, then validate with controlled inputs.
What Tarvos does not install automatically
The registry is a source of installation knowledge. A builder or their coding agent decides which node marked installable to add inside the builder's own environment.