How do I install the MCP Arch skill?

Run npx skillmds@latest add different-ai/mcp-arch-2 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the MCP Arch skill do?

Explain how MCP is wired between OpenWork, OpenCode, and the OpenWork server, and guide config or auth troubleshooting. Triggers when user mentions: - "mcp wiring" - "mcp architecture" - "mcp config" It is listed under AI & ML on SkillMD.

Is MCP Arch safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with MCP Arch?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is MCP Arch free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published MCP Arch?

different-ai (@different-ai) published this skill. Their other Agent Skills are listed on their SkillMD profile.

MCP Arch by different-ai — Agent Skill

Name: MCP Arch
Author: different-ai

File contents

Quick Usage (Already Configured)

Provide wiring overview

OpenWork UI uses the OpenCode SDK for runtime MCP calls and events.
MCP config lives in opencode.json under mcp; 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-directory or directory query) so OpenCode loads the correct config.

Troubleshoot auth errors

Confirm the MCP entry type and required fields (local needs command[], remote needs url).
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.json path.
In remote mode, OpenWork approval gates apply for mcp.add and engine.reload unless 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)

Add the MCP entry to opencode.json.
Restart or reload the OpenCode engine.
Authenticate the MCP provider via OpenCode.

Frequently asked questions

MCP Arch