Workflows Overview

Oplink workflows are YAML-defined tools that your IDE/agent can call via MCP. They let you combine prompts and external MCP servers into reusable flows that your team can version, review, and share.

Why workflows

• Combine prompts with MCP tools into one invokable command
• Share a consistent toolbox across teammates/repos
• Curate arguments, defaults, and sequences for reliability

Project setup

• npx oplink@latest init
• Add .mcp-workflows/workflows.yaml (and servers.json if using external servers)
• Point your IDE at --config ./.mcp-workflows when starting the server

Workflow modes

• Prompt workflows: a single prompt tool (great for heuristics, helper text)
• Auto-discovery workflows: route calls to external servers; Oplink registers describe_tools so agents can discover available commands using cached schemas
• Scripted workflows: multi-step orchestration that validates args and calls specific external tools in sequence

Folder layout

• .mcp-workflows/workflows.yaml – your workflow definitions
• .mcp-workflows/servers.json – registry of external MCP servers (aliases, commands, env)
• .mcp-workflows/.tokens/* – OAuth tokens/cache (ignored by git)

Next steps

• Auto‑Discovery Workflows
• Scripted Workflows
• External Servers & Registry
• Parameters & Schemas
• Debugging & Caching
• See the Examples section for practical workflow examples