opencode-spicrawl

Spicrawl plugin for OpenCode. It adds the Spicrawl MCP server to your OpenCode config, so agents can scrape pages to Markdown or JSON, run batch jobs, use persistent login sessions, look up request history and usage, and search the Spicrawl docs.

Install

1. Create an API key at app.spicrawl.com.

2. Export it where OpenCode runs:

   export SPICRAWL_API_KEY=spicrawl_live_...

3. Add the plugin to opencode.json (project) or ~/.config/opencode/opencode.json (global):

   {
     "$schema": "https://opencode.ai/config.json",
     "plugin": ["opencode-spicrawl"]
   }

OpenCode installs the package from npm on start. Check the connection with:

opencode mcp list

spicrawl should show as connected. Its tools are named spicrawl_*; ask the agent to scrape a URL and it will pick the right one.

What it does

On startup the plugin adds this entry to OpenCode's config, in memory. It does not write to your config files:

{
  "mcp": {
    "spicrawl": {
      "type": "remote",
      "url": "https://mcp.spicrawl.com/mcp",
      "oauth": false,
      "enabled": true,
      "headers": { "Authorization": "Bearer <SPICRAWL_API_KEY>" }
    }
  }
}

• If SPICRAWL_API_KEY is unset or blank, no server is added, so there is no failing connection. OpenCode logs one warning (opencode run --print-logs shows it).
• If your config already has an mcp.spicrawl entry, the plugin leaves it alone.
• Other MCP servers are untouched.

Without the plugin

The same result with no plugin, in opencode.json:

{
  "mcp": {
    "spicrawl": {
      "type": "remote",
      "url": "https://mcp.spicrawl.com/mcp",
      "oauth": false,
      "enabled": true,
      "headers": { "Authorization": "Bearer {env:SPICRAWL_API_KEY}" }
    }
  }
}

Links

• Docs: https://docs.spicrawl.com/agents/opencode
• API keys: https://app.spicrawl.com

License

Apache-2.0