Opscotch Root Guidance

Root guidance served by the Public Opscotch MCP server for an LLM that has just connected without prior Opscotch context.

Start Here

This root guidance is being returned by the Public Opscotch MCP server at https://mcp.opscotch.ai/mcp. The user likely added this server because they want to evaluate Opscotch, plan an Opscotch automation problem, build an Opscotch app or workflow, package it, test it, or run it.

Opscotch is a constrained workflow runtime for productized automation. It is used to develop, deploy, and run workflows that collect, transform, correlate, and report data from systems that do not directly answer the user's operational question. Opscotch is not a generic web framework or unconstrained scripting host. Its workflows run inside customer-controlled environments, including cloud, on-prem, edge, and disconnected environments when configured and deployed that way.

This MCP endpoint is the canonical LLM-facing help surface for Opscotch design-time work. Use it for guidance, schema lookup, API/context discovery, workflow patterns, and validation before asserting Opscotch-specific behavior.

The first mental model is bootstrap versus workflow.

Bootstrap is the installed boundary. It is local to the runtime and describes trust, permissions, deployments, keys, package expectations, host/file/server access, licensing, and environment-specific configuration. Bootstrap answers: what may this deployment do?

Workflow is the updateable automation logic that runs inside those bootstrap boundaries. It contains workflows, steps, triggers, processors, resources, data flow, and reusable behavior. Workflow answers: how should this deployment use what it may do?

Load deeper guidance based on the user's intent:

• Start with get_guidance(role=system) to establish tool order and anti-hallucination rules.
• Use get_guidance(role=architect) before planning or designing bootstrap/workflow boundaries.
• Use get_guidance(role=engineer) before implementation-sensitive authoring or final JSON.
• Use operations guidance for run, start, package, Docker, or test-harness questions.

System Guidance Preamble

This first-contact guidance is being served from the Public Opscotch MCP server because the user likely wants to evaluate or build with Opscotch. Opscotch is a workflow runtime for productized automation; workflows run in customer-controlled environments, including edge or disconnected environments when configured that way. Bootstrap describes installed trust, permissions, deployments, keys, packages, and environment-specific configuration. Workflow describes updateable automation logic: triggers, steps, processors, resources, and data flow. The Public Opscotch MCP endpoint at https://mcp.opscotch.ai/mcp is the LLM-facing guidance, schema, lookup, and validation surface. Load system guidance first, architect guidance before design, engineer guidance before implementation, and operations guidance for run/start/test questions.

Primary Provenance

• docs/src/llm/processed/intro.md -> https://docs.opscotch.co/docs/current/intro
• docs/src/llm/processed/introduction/basic-concepts.md
• docs/src/llm/processed/core-capabilities/runtime.md -> https://www.opscotch.co
• docs/src/llm/processed/what-opscotch-does/what-commercial-workflow-runtime.md -> https://www.opscotch.co
• docs/src/llm/processed/what-opscotch-does/what-edge-and-disconnected-execution.md -> https://www.opscotch.co
• docs/src/llm/processed/docs/workflow.md -> https://docs.opscotch.co/docs/current/workflow
• docs/docs/llm/opscotch-architect-skill.md -> https://docs.opscotch.co/docs/current/llm/opscotch-architect-skill
• docs/docs/llm/opscotch-operations-skill.md -> https://docs.opscotch.co/docs/current/llm/opscotch-operations-skill
• docs/src/llm/operations/context/prompt-imperatives.md