mcp-arch

Document MCP wiring between OpenWork, OpenCode, and the OpenWork server.

63|8|Updated Jan 24, 2026
One-click install
npx skills add https://github.com/different-ai/openwork-enterprise --skill mcp-arch
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mcp-arch
Source: https://github.com/different-ai/openwork-enterprise/tree/main/.opencode/skills/mcp-arch
Command: npx skills add https://github.com/different-ai/openwork-enterprise --skill mcp-arch

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

MCP wiring and authentication can be complex to configure across OpenWork and OpenCode. This guide clarifies the data flow, config structure, and troubleshooting steps to streamline setup and reduce setup errors.

Core Features & Use Cases

  • Clear overview of how MCP connects OpenWork UI, OpenCode runtime, and the OpenWork server.
  • Explanation of where the MCP config lives (opencode.json under mcp) and how tokens are managed.
  • Use Case: Remote UI interactions require proper routing, config persistence, and token handling between components.

Quick Start

Configure the MCP wiring in opencode.json and reload the OpenCode engine.

Frequently Asked Questions about mcp-arch

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How does MCP wiring work between OpenWork and OpenCode?

MCP wiring connects the OpenWork UI, OpenCode runtime, and OpenWork server by managing remote UI traffic, config persistence, and token handling across components.

Where does the MCP config live in the OpenCode ecosystem?

The MCP config lives in the opencode.json file under the mcp key, defining endpoint routing, configuration scope, and token handling for the OpenCode ecosystem.

How do I configure MCP authentication tokens for OpenWork remote UI interactions?

Configure MCP authentication by defining token handling and endpoint routing requirements in opencode.json, then reload the OpenCode engine to apply the updated config scope.

Why is my MCP config not applying after updating opencode.json?

MCP config changes in opencode.json require an OpenCode engine reload to take effect, ensuring configuration scope, token handling, and endpoint routing are properly enforced.

Can I use this MCP config guide for troubleshooting remote UI traffic routing?

Yes, the MCP wiring guide clarifies data flow, config structure, and troubleshooting steps for remote UI traffic, config management, and authentication workflows across OpenWork and OpenCode.