Set up LinkBunny in OpenCode

Install the shared LinkBunny Skill

Review the canonical Skill, then use the setup prompt or the manual command below. The Skill holds the API workflow and approval rules. Local MCP is optional; both interfaces follow the same instructions.

In bash or zsh, this downloads the Skill to ~/.agents/skills/linkbunny/SKILL.md and refuses to overwrite a copy. It needs curl with --remove-on-error support. For one repository, save the reviewed file at .agents/skills/linkbunny/SKILL.md instead. Keep credentials out of the Skill.

skill_dir="$HOME/.agents/skills/linkbunny"
skill_file="$skill_dir/SKILL.md"
mkdir -p "$skill_dir" &&
if [ -e "$skill_file" ]; then
  printf 'Refusing to overwrite %s\n' "$skill_file" >&2; exit 1
else
  curl -fsSL --remove-on-error "https://getlinkbunny.com/skill.md" -o "$skill_file"
fi

OpenCode discovers .agents/skills and ~/.agents/skills, as well as its own .opencode/skills and Claude-compatible directories. Keep one reviewed copy. In a fresh session, ask OpenCode to load linkbunny through its skill tool and read the entire file before preparing a profile.

Subscribe before creating a marketplace token

$20/month covers up to 10 active sites. Sign in to Account, subscribe, then create a token. Approve account, subscription and credential actions as they arise. Your agent's account and model usage are separate from LinkBunny's plan.

Store LINKBUNNY_API_TOKEN in an approved secret store or a private, Git-ignored file. The local MCP examples use --token-file: only the absolute file path goes in configuration. The loader reads that variable without executing the file as a shell script. Keep the value out of prompts, command arguments, source, URLs, logs and screenshots.

Have the agent propose a profile from your site's content before registration. Each new profile needs manual marketplace review before matching. Approve one check-in at a time; check_in can reserve an assignment. Review each contextual nofollow edit, approve publication, then approve reporting separately. Approve rejection when no suitable context exists. Stop when review is pending or no request is available; do not poll automatically.

The agent workflow owns these steps. The directory backlink tutorial uses the free hosted checker for an existing link and needs no LinkBunny signup or token.

Merge the local server into opencode.json

Use OpenCode in your site's repository with your chosen model configured. For local MCP, the host also needs Node.js 22 or later and npm/npx. Review the proposed config, package, private file path and permissions before approving the change. Preserve unrelated entries.

Prepare project-scoped registration for the local stdio server @linkbunny/mcp@0.1.1 in this coding agent. Follow https://getlinkbunny.com/docs/agents#mcp for the correct client configuration, secret loading, trust, restart, and safe verification. Never reveal or copy the LinkBunny API token into chat, command arguments, logs, screenshots, or tracked configuration. Before changing persistent MCP configuration, show me the exact client, scope, config diff, pinned command, secret-loading path, and restart/trust steps, then ask for approval. After setup, read linkbunny://guidance/skill before using any LinkBunny tool. Do not call a LinkBunny tool merely to test setup.

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "linkbunny": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@linkbunny/mcp@0.1.1",
        "--token-file",
        "/absolute/project/.env.linkbunny"
      ],
      "enabled": true
    }
  },
  "permission": {
    "linkbunny_*": "ask",
    "edit": "ask",
    "bash": "ask"
  }
}

Replace /absolute/project/.env.linkbunny with the private token file's path on the OpenCode host. Project configuration lives in opencode.json or opencode.jsonc; personal configuration can live in ~/.config/opencode/opencode.json.

OpenCode's local server uses type: "local" and a single command array containing the executable and arguments. Its environment key is environment. A copied mcpServers/args block from another client is a different schema. The token-file example needs no environment block.

opencode mcp list

Run this after approving setup to inspect connection status. It connects to configured servers and retrieves their tool declarations; it does not run a marketplace operation or need a model response. OpenCode also offers opencode mcp add for interactive registration. Inspect the resulting configuration and keep the permission rules above.

OpenCode configuration and discovery · checked 15 Oct 2026: MCP servers · Config · CLI · Skills

Ask before tools, edits and shell commands

"linkbunny_*": "ask" applies to the tools OpenCode names with this server prefix. The edit and bash rules also ask before file changes and shell commands. Check the selected agent's overrides and later matching rules; don't replace these with allow to get past a prompt. A native tool approval and the Skill's approval for the actual marketplace action both matter.

Keep --auto and the TUI's auto-approve mode off. Auto mode approves requests that would otherwise ask, including these rules. In the command palette, choose Disable auto-approve permissions if the prompt shows the auto indicator.

Read the installed Skill, then inspect the connected server's available tools: register_profile, update_profile, check_in, report_assignment and reject_assignment. Discovery is enough for setup; never call one of these tools as a connection test. Use the shared MCP instructions for the bundled linkbunny://guidance/skill resource when your client exposes resource reads.

OpenCode approval controls · checked 15 Oct 2026: Tool permissions · Permission rules

Fix OpenCode configuration and Skill loading

The server is absent or disconnected

Check the active project directory, the mcp key, enabled: true and the command array. Check Node.js and the absolute token-file path on the same host. A first npx download can take longer than OpenCode's default five-second MCP timeout; its per-server timeout setting can accommodate that startup.

The Skill does not appear

Check the exact linkbunny/SKILL.md path, frontmatter name and Skill permission. Look for a second copy in .claude/skills or .opencode/skills, then restart in the intended repository. A model session uses your configured provider; an MCP connection alone does not load the Skill.

A workflow action is rejected

Check the approved token and subscription privately, then the returned API error. A connected server does not establish entitlement. If profile review is pending or there is no assignment, tell the site owner and stop.

Compare setup requirements for other coding agents.