OPLINK – MCP Server for Workflows

OPLINK is an MCP server that sits between your IDE and multiple MCP servers. It reads simple YAML workflow definitions and exposes them as a single, coherent tool surface in your editor.

Get started

GitHub

Terminal

npx -y oplink@latest server --config ./.mcp-workflows

# .mcp-workflows/workflows.yaml
frontend_debugger:
  description: "Debug frontend issues with Chrome DevTools"
  prompt: |
    Use Chrome DevTools MCP tools to inspect the page,
    capture screenshots, and list console or network logs.
  externalServers:
    - chrome-devtools

Workflows on Top of Your MCP Servers

Connect MCP Servers

Point OPLINK at .mcp-workflows/servers.json and combine multiple MCP servers behind one workflow hub.

Named Workflow Commands

Call custom workflow names like debug_frontend or research_repo instead of juggling dozens of raw tools.

Versioned Config

Keep workflows in git so your team shares the same debugging, triage, and research flows.

Encoded Strategies

Encode multi‑step plans, defaults, and guardrails so agents don’t have to improvise every time.

Team Friendly

Give teammates one MCP endpoint with curated workflows instead of a pile of servers.

Ready-Made Workflows

Start from examples (DeepWiki, Chrome DevTools, Context7, Atlassian, etc.) and adapt them to your stack.

Examples

Linear + Discord Integration

Combine Linear issue management and Discord messaging into a single linear_discord_helper workflow. Use describe_tools to discover available tools, then route calls to either server.

.mcp-workflows/workflows.yaml

linear_discord_helper:
  description: "Access both Linear and Discord MCP tools"
  prompt: |
    Use Linear and Discord MCP tools together.
    Call describe_tools({ "workflow": "linear_discord_helper" }) first to see available tools.
    Then call this workflow with {"tool": "tool_name", "server": "linear" or "discord", "args": {...}}.
  externalServers:
    - linear
    - discord

Frontend Debugger

Turn Chrome DevTools MCP into a single take_screenshot workflow that agents can call to navigate, wait for content, and capture screenshots.

.mcp-workflows/workflows.yaml

take_screenshot:
  description: "Navigate and capture a screenshot"
  runtime: scripted
  parameters:
    url:
      type: string
      required: true
    wait_for:
      type: string
    format:
      type: string
      enum: [png, jpeg, webp]
      default: png
  steps:
    - call: chrome-devtools:navigate_page
      args:
        type: url
        url: "{{ url }}"
        ignoreCache: false
    - call: chrome-devtools:wait_for
      requires: wait_for
      args:
        text: "{{ wait_for }}"
        timeout: 10000
    - call: chrome-devtools:take_screenshot
      args:
        fullPage: true
        format: "{{ format }}"

Repository Q&A with DeepWiki

Ask structured questions about any GitHub repo via DeepWiki, but expose it as a single deepwiki_lookup workflow in your IDE.

.mcp-workflows/workflows.yaml

deepwiki_lookup:
  description: "Ask DeepWiki a question about a GitHub repository"
  runtime: scripted
  parameters:
    repo:
      type: string
      description: "owner/repo, e.g. shadcn-ui/ui"
      required: true
    question:
      type: string
      description: "Question to ask about the repository"
      required: true
  steps:
    - call: deepwiki:ask_question
      args:
        repoName: "{{ repo }}"
        question: "{{ question }}"

Try OPLINK as your workflow MCP server

OPLINK turns your MCP ecosystem into a coherent, versioned set of workflows that your IDE (and agents) can call with one server.

Get Started Now GitHub