원클릭으로 Manus에서 모든 스킬 실행

mcp-arch

스타59

포크7

업데이트2026년 2월 4일 06:21

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"

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

different-ai

different-ai/the-factory

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

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.

이 저장소의 다른 Skills

같은 저장소

using-openwork-with-chrome-mcp

different-ai/the-factory

Drive the OpenWork dev renderer with Chrome MCP and verify workspace UI flows. Triggers when user mentions: - "use Chrome MCP with OpenWork" - "hook up to pnpm dev renderer" - "add an OpenWork workspace through the UI"

2026-05-0659

make-pr

different-ai/the-factory

Create a PR with structured evidence: build verification, UI screenshots uploaded to an ephemeral host, API test results, and a verification comment. No screenshots committed to the repo. Triggers when user mentions: - "create a pr" - "make a pr" - "open a pr" - "push and pr"

2026-05-0559

den-test-instructions

different-ai/the-factory

Boot up the Den dev stack and the OpenWork desktop app locally, then test common flows like sign-in, dashboard, and telemetry. Triggers when user mentions: - "test den" - "test the app locally" - "boot up den" - "den dev flow" - "test sign in"

2026-05-0559

changelog-release-tracker

different-ai/the-factory

Generate or update the internal OpenWork release changelog tracker as plain markdown release sections. Triggers when user mentions: - "generate changelog markdown" - "track this release" - "add a changelog entry"

2026-04-0559

cupid-app-architecture

different-ai/the-factory

CUPID app architecture guidance for apps/app/src/app/**

2026-03-2959

vercel-env-vars

different-ai/the-factory

Manage Vercel environment variables for OpenWork projects from the CLI, including linking the local app directory first. Triggers when user mentions: - "add a vercel env var" - "set a vercel env var" - "vercel environment variable"

2026-03-2359

name	mcp-arch
description	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"

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.