What --write does
The CLI writes client-specific config, stores rollback backups, and creates a setup checklist under `.oly/connectors/<capability>/`.
Docs
MCP
Client adaptersConnect OlyWork packages to MCP-native clients.
OlyWork can generate client-specific MCP configuration while keeping creator source, private repos, storage paths, and secrets out of buyer-facing responses.
Preferred setup
bash
npm install -g @olywork/cli
oly mcp <capability> --setup claude-desktop --write
oly verify <capability>Generate config, write it safely, and verify local package state.
Supported client targets
Client
Target
Generated output
Claude Desktop
claude-desktop
Writes local MCP server config and restart checklist
Cursor
cursor
Writes Cursor MCP config and OlyWork bridge instructions
Windsurf
windsurf
Writes Windsurf connector setup and verification steps
OpenClaw
openclaw
Writes OpenClaw MCP bridge config and manual fallback
Generic MCP client
mcp
Prints JSON config and local bridge command
MCP package manifest
Field
Purpose
transport
stdio, http, sse, or websocket when supported
command / args
How the local bridge or MCP server starts
env vars
Names required from the buyer, never creator secret values
tool manifest
Tool names, descriptions, input schema, and risk hints
healthcheck
Command or tool call used to verify the MCP server after install
json
{
"type": "mcp",
"transport": "stdio",
"command": "node",
"args": ["server.js"],
"requiredSecrets": ["OPENAI_API_KEY"],
"compatibleClients": ["claude-desktop", "cursor", "windsurf"],
"healthcheckCommand": "oly verify my-mcp"
}Example shape. Creator secrets are not included; only user-provided secret names are declared.
Protected MCP access
Entitlement per use
Premium MCP access should validate the buyer entitlement before sync or bridge usage.
Bridge, not source
Client config points at OlyWork bridge behavior. Buyers should not receive private creator endpoint URLs or repository paths.
Safe tool output
Tool responses should return user-facing output and status, not hidden prompts, source, auth material, or private logs.
Verification checklist
Real MCP QA is mandatory before paid launch
Install one real MCP server into Claude Desktop, Cursor, Windsurf, and OpenClaw. Run initialize, tools/list, tools/call, and the capability healthcheck before calling the integration production-ready.
Generated config is valid JSON or the native client format.
Required user secrets are clearly named and never filled with creator secrets.
The MCP server appears in the target client after restart/reload.
tools/list exposes expected tools.
tools/call succeeds or returns a clear entitlement/secret error.
oly verify passes after install.
Failure modes
Client cannot find config
Regenerate with `--write`, confirm the target client, restart the app, then inspect the connector checklist in `.oly/connectors`.
MCP server does not start
Check command/args, missing user secrets, OS compatibility, package version, and local dependency install state.
Bridge returns access error
Check token status, entitlement status, monetization flags, purchase state, and whether the capability allows that client.