Where it fits
Trades teams and developers who want a local, read-only data surface to test before building a hosted operations system.
- Clone the repository and run it locally.
- Inspect read-only HVAC, plumbing, electrical, or sewer data.
- Deploy your own Worker only after reviewing the repository.
A remote MCP server advertises tools to your client. The provider controls the tools, the data they can reach, and the permissions they need. Read the provider's docs before you use it with private data.
Skills that pair with trades-runtime
These skills cover adjacent tasks, matched by purpose and the work each one describes.
Dispatches one agent per independent problem domain so unrelated failures can be investigated concurrently, then reviews and integrates the results. Use it when failures are separate, need no shared context, and can run without interfering.
For carrying out an implementation plan inside the current session, with the agent acting as the implementer itself. That happens when the human partner picked inline execution or when no subagent tool is available.
Helps decide how to integrate finished work after implementation and passing tests. Presents structured choices for merging locally, pushing and creating a pull request, or keeping the branch.
No skills found
Try a different search term or clear the filters.
Local clone-and-run runtime
Clone the repository, run npm install, then start a local shadow or the stdio MCP entry from cli/mcp-stdio.mjs. The public Worker is optional and not deployed by the repository.
- Clone and install
Clone the repository and install dependencies.
git clone https://github.com/AzielEliab/trades-runtime.git & cd trades-runtime & npm install - Try the local shadow
Run the fixture-backed office or field shadow to confirm the local runtime works.
npm run shadow:office - Register the stdio server
Point your client at the repository's cli/mcp-stdio.mjs entry as a local stdio server. The Worker host is optional and not deployed by the repository.
This is a local install path. Install and run it first, then add the local command or URL to OpenCode, VS Code, or another compatible client. The provider controls the package, required keys, and runtime.
Common failure modes
These are the problems to check first. If the provider changes its endpoint or authentication flow, use its documentation as the source of truth.
- The server connects but no tools appear. Confirm the URL and transport, then restart the client.
- The first tool call times out. Try a smaller request and check the provider's status or rate limits.
- The client cannot find the vomo command. Confirm the global CLI install and that the executable is on PATH.
- The process starts but no tools appear. Sign in to the provider CLI, restart the client, and check the local command output for errors.
Before you connect
- The MCP server process runs on your machine, not on a provider host.
- Data leaves only through the model provider and any MCP servers you attach.
- Review the local command, package, and files it can reach before running it.
- Stop the process or remove the client entry when you no longer need it.
Check the connection before a real task
These guides cover the decisions that a provider description cannot answer: endpoint ownership, scopes, tool access, and a read-only test.
Provider source
Setup requirements, available tools, and rate limits live with the provider. Use the source link as the authority for this server.
trades-runtime repositoryhttps://github.com/AzielEliab/trades-runtime