Mcp Arch
- 2 installs
- 29 repo stars
- Updated March 27, 2026
- different-ai/openwork-hub
Explains how MCP is wired across OpenWork, OpenCode, and the OpenWork server, and guides config and OAuth token troubleshooting.
About
Documents the MCP wiring between the OpenWork UI, OpenCode SDK, and OpenWork server, and provides steps to fix config, directory, and OAuth token errors. A developer uses it when debugging MCP architecture, config, or auth issues in OpenWork.
- Wiring overview: UI, OpenCode SDK, server proxy at /opencode/*
- Auth troubleshooting for OAuth tokens and workspace directory
Mcp Arch by the numbers
- 2 all-time installs (skills.sh)
- Ranked #13,958 of 16,546 AI & Agent Building skills by installs in the Skillselion catalog
- Data as of Aug 3, 2026 (Skillselion catalog sync)
npx skills add https://github.com/different-ai/openwork-hub --skill mcp-archAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 2 |
|---|---|
| repo stars | ★ 29 |
| Last updated | March 27, 2026 |
| Repository | different-ai/openwork-hub ↗ |
What it does
Explains how MCP is wired across OpenWork, OpenCode, and the OpenWork server, and guides config and OAuth token troubleshooting.
Files
Quick Usage (Already Configured)
Provide wiring overview
- OpenWork UI uses the OpenCode SDK for runtime MCP calls and events.
- MCP config lives in
opencode.jsonundermcp; OpenWork server only reads/writes config for remote clients. - MCP auth tokens are managed by OpenCode and stored outside the repo.
- Remote UI traffic hits the OpenWork server at
/opencode/*, which proxies to OpenCode. - The OpenWork server must include the workspace directory (via
x-opencode-directoryordirectoryquery) so OpenCode loads the correct config.
Troubleshoot auth errors
- Confirm the MCP entry type and required fields (
localneedscommand[],remoteneedsurl). - If refresh tokens are invalid, re-auth via OpenCode and reload the engine after config edits.
- Avoid editing token files directly; use OpenCode commands or endpoints.
- If the UI says "does not support OAuth", verify the directory matches the on-disk
opencode.jsonpath. - In remote mode, OpenWork approval gates apply for
mcp.addandengine.reloadunless auto-approve is explicitly enabled.
Common Gotchas
- Engine reload only re-reads config; it does not refresh OAuth tokens.
- Remote clients need OpenWork server for config writes, but MCP runtime still routes through OpenCode.
- macOS can resolve temp paths as
/private/tmp/...while config is under/tmp/...; normalize before calling MCP endpoints.
First-Time Setup (If Not Configured)
1. Add the MCP entry to opencode.json. 2. Restart or reload the OpenCode engine. 3. Authenticate the MCP provider via OpenCode.
.env
Related skills
Setup Matt Pocock SkillsScaffold the per-repo configuration that Matt Pocock’s engineering agent skills rely on so they understand the issue tracker, triage labels, and domain documentation la495k196k
Lark AppsConnect Claude, Cursor or custom agents directly to Lark (Feishu) for messaging, document automation, approval workflows and enterprise data access.402k
CavemanSlash token usage by roughly 75% while keeping every technical detail intact when working with Claude Code, Cursor or similar agents.391k94.7k
Lark Skill MakerQuickly turn any Lark/Feishu OpenAPI call or multi-step workflow into a reusable agent skill with its own SKILL.md.386k16k
Running Claude Code Via Litellm CopilotRun Claude Code at a fraction of the cost by routing requests through LiteLLM to the GitHub Copilot Chat API.270k72
Codex PetGenerate a complete Codex Pet spritesheet and metadata from one reference image without needing an OpenAI key or Codex Pro.246k10AI & Agent Buildingagents